Drupal Migration & Upgrade
Move off Drupal 7 or an ageing CMS without losing content, URLs or search rankings. Fixed price once the architecture is agreed, and you own the source code that comes out of it.
Migration projects fail in predictable ways: content that does not map cleanly, custom modules with no modern equivalent, and URLs that change and take search rankings with them. We plan for all three before writing migration code. You get a trial migration — a full copy of your data running on the new platform — so the comparison against your current site happens before cutover, not after. You own the source code that comes out of it, so nothing here creates a dependency on us that you did not choose.
Who this is for: Anyone still on Drupal 7 (now end of life), on Drupal 10 ahead of its December 2026 end of life, or on a legacy CMS that has become the constraint rather than the tool.
What We Deliver
How It Works
Audit What You Have
We inventory content types, contributed and custom modules, integrations and traffic. You get the findings whether or not you hire us.
Migration Architecture
Entity mapping, what carries over, what gets rebuilt, and what is deliberately retired. Priced at a fixed cost from here.
Trial Migration
A full copy of your data on the new platform, running, so you can check it against the old site before anything is committed.
Rebuild & Verify
Weekly demos. Automated tests on the code we ship. Redirects mapped so existing rankings survive the move.
Cutover & Warranty
Go-live planned to keep the current site available until the new one is proven. Warranty included, up to 3 years, same team.
What you get
How the work runs
A migration is a content problem before it is a code problem. We audit what you actually have — including the parts nobody has looked at in years — and run a trial migration early, so the surprises arrive while they are still cheap.
- Content audit: what exists, what is still used, what should not come across
- Field-level mapping from the old model to the new one, agreed before code
- A trial migration you can browse, run repeatedly as the mapping is corrected
- Redirects planned for every URL that changes, so rankings survive the move
- Rehearsed cutover, then warranty on the result
We have written this up in full — the process when you come to us directly, the sprint cycle when you are an agency partner, and the framework underneath both.
Questions we get asked
Will we lose our search rankings?
Not if the redirects are done properly, which is why the redirect map is a deliverable rather than an afterthought. Every old URL either resolves to its equivalent or is deliberately retired, and we verify that before go-live rather than discovering it in Search Console afterwards.
How long does a migration take?
It depends on content volume, how much custom code exists, and how many integrations have to be re-pointed. The audit gives you that answer before you commit, which is the point of doing it first.
Can we migrate in stages?
Often yes. Where a single cutover is too risky, we run the old and new systems in parallel and move sections across, with the redirect layer keeping both addressable.
What about our custom modules?
The audit lists them with a recommendation for each: port, replace with a contributed module, or drop because the need has gone. That decision is yours, made against real information.
Delivered work using this service
Technologies Used
Let's Get Started
Ready to transform your business with drupal migration & upgrade?
Start Your Project