%20(1).png?width=200&height=63&name=Promet%20Logo%202019-01%20(1)%20(1).png)
Drupal 10 end of life · December 2026
A fixed price and a fixed date.
In writing.
Every other vendor quotes your Drupal 11 upgrade with a range, because nobody can tell you in advance what's hiding in 180 modules and eight years of custom code.
We can. We built the tooling that finds it: every deprecation, every dependency conflict, every abandoned module, before anyone signs anything. When the unknowns are gone, a fixed price stops being a gamble.
Non-destructive. Runs in isolation. Never changes your production site.
2
Human review gates before go-live
1-click
Rollback to pre-upgrade state
What a fixed price actually requires
A fixed price requires solving the unknowns first
You already know you need to be off Drupal 10 before security coverage ends.
You're stalled because you can't get a figure you can defend to procurement, and the reason is the same everywhere.
Deprecation debt hides until it's analyzed
Nobody sees it until someone reads the code line by line. Manual audits are expensive, so most vendors skip them and pad the estimate instead.
Contrib is a dependency puzzle
A large install has modules with no D11 release, absent maintainers, and patches that half-apply. Resolving that by hand takes days before anyone can price it.
So the risk gets priced in
You get a range, a discovery phase that becomes its own project, and a change order when reality arrives. The uncertainty ends up on your budget.
Gate 1 · The plan
Every unknown found and resolved on paper first
Before a single line changes, we run a full non-destructive analysis and hand you a proposal you can read, question, and take to your budget holder.
- Discovery and upgrade status: complete inventory of modules, themes, and custom code
- Deprecation analysis: every incompatible API call identified across the full codebase
- Dependency resolution: the full contrib puzzle solved, including what gets replaced or retired
- Proposal diff: exactly what will change, before it changes
Human governance: we review the Gate 1 proposal with you and price it. You approve the plan before anything runs. This is the point at which the fixed price is set.
Gate 2 · The evidence
Evidence the site still looks right
The upgrade runs against a rehearsal branch, then automated visual regression captures before-and-after screenshots across your key routes on desktop and mobile, with pixel-diff overlays.
- Before/after capture: key routes, both breakpoints
- Pixel diff overlays: every visual change surfaced immediately for review
- Automated DB snapshot and Git checkpoint: taken before the upgrade, every time
- One-click rollback: instant return to the pre-upgrade state
Human governance: our engineers spot-check the regression results and walk them through with your team before anything reaches production.
HUMAN GOVERNANCE
Where a person takes over
Our engine tells you exactly where it stops and a person takes over.
Better to stop and ask than report success on a broken site.
Architectural redesigns
If custom code depends on an abandoned module with no Drupal 11 replacement, the engine halts and flags it for a developer. It does not invent a substitute.
Ambiguous API changes
When a breaking change has more than one defensible resolution, it stops at Gate 1 and flags a blocker for a developer to decide.
Live third-party integrations
Payment gateways and production SSO are sanitized for testing. We rehearse against them safely; we never point a rehearsal at your live systems.
Your production environment
Rehearsals run strictly on zero-copy local branches. Analysis runs in an isolated container. Your code and database are untouched throughout.
SEE IT RUN
A real upgrade, start to finish
Walk through Gate 1 analysis, dependency resolution, and Gate 2 visual regression on a live production site.
CASE EVIDENCE
Proven on a live city government website
The City of Cleveland's production Drupal site, taken cleanly to 11.4.x: schema updates applied, caches rebuilt, visual regression passing.
MUNICIPAL GOVERNMENT
City of Cleveland
Civic configurations: Complex
Contrib dependencies: Extensive
Upgraded to: Drupal 11.4.x
Visual regression: Passed
part of the same engagement
The same engine can carry you to Drupal Canvas
Canvas is where Drupal page building is going. For sites built on Paragraphs or Layout Builder, getting there has looked like rebuilding every landing page you own, which is why most teams have quietly deferred it.
Our AI-assisted migration tooling converts existing Paragraphs and Layout Builder pages to Canvas automatically, preserving content and structure, the same engine doing the heavier work of your Drupal 11 upgrade.
If the site is already open for a Drupal 11 upgrade, this is the cheapest moment you will ever have to do it.
Questions and answers
What teams ask us first
How can you commit to a fixed price when nobody else will?
Because we resolve the unknowns before we ever quote a price. The Gate 1 analysis is exhaustive: every module, every deprecation, every dependency conflict. Once that's known, pricing it is simple arithmetic. If we get the estimate wrong, we absorb it.
What access do you need for the scan?
A short call and secure access to your site's code and database. A developer sets up a working copy of your site on their local machine and runs the analysis there, so your production site stays exactly as it is. Once access is in place, you get the readiness report within 24 hours.
What happens to our site and data after the scan?
We only use the copy of your site to run the scan. If you don't move forward with the upgrade, we delete it once your readiness report is delivered. If you choose to proceed, we keep working from that same copy, so there's no need to hand over access twice.
We have a module with no D11 release and no maintainer.
That's the normal case. The scan identifies it, categorizes it as port, replace, or retire, and the proposal prices the resolution. You see it at Gate 1, before you commit.
Can you work with our existing hosting platform?
Yes. We deliver on all major Drupal hosting platforms and work within your existing environment and deployment pipeline. No migration required.
When would the actual cutover happen?
Whatever your genuine low-traffic window is. The rehearsal branch and visual regression run well ahead, so the cutover itself is the least eventful part.
We don't have budget in this fiscal year.
The scan is free and its output is the document you need to request funding: a defensible scope with a real number attached. One caution: everyone is discovering the same deadline at once, and delivery capacity across the Drupal ecosystem gets scarce in the final quarter before an end of life.
Who owns the work?
You do. All code and documentation in your repository, no proprietary components in the delivered report, no lock-in.
REQUEST YOUR FREE SCAN
Get the number you can actually take to procurement
Fill out the form and our team will reach out to set up secure access to your site.
We run the full Gate 1 analysis and return a complete readiness report within 24 hours: module inventory, deprecation findings, dependency resolution, and what each one takes to fix.
Free, with no obligation to proceed
Non-destructive: production is never touched
The report is yours to keep and use internally
Fixed-price proposal only if you want one