service
Website and software migrations
A business moving a site or application to a new platform, or off a system that is being retired, where losing data or search visibility would be costly.
What you get
- A migration plan with a rollback position and a cutover window agreed in advance.
- Content and data mapping, including the fields that do not map cleanly.
- Redirect handling for every URL that carries traffic or links.
- A post-cutover verification pass against the pre-migration baseline.
How this differs from website redesign
A redesign keeps the platform and changes the experience. A migration changes the platform itself, so the risk is data, URLs and functionality rather than design. They are sometimes done together, which is precisely why the distinction must be explicit.
How we approach it
- We take a complete copy of the existing data and content before anything is moved, and we verify the copy restores.
- We migrate in stages with the old system still running, so a problem is a delay rather than a data loss.
- We reconcile record counts and spot-check content after the move, because a migration is not finished until the two agree.
What is out of scope
- Guaranteeing zero disruption. A migration carries risk; the honest deliverable is a plan that contains it and a stated rollback.
- Preserving functionality that depended on a platform feature the new platform does not have. That is found in planning, not on cutover night.
How it is priced
Cost is driven by data volume, by how much of the old system is undocumented, and by how long both systems must run in parallel.
See the pricing page for how that works in practice.
How to start
The first conversation is free and usually takes half an hour. Bring the problem as you experience it — what is not working and what you have already tried.
Tell us what you need
The more specific you are about the problem, the more useful the first reply will be. We read every enquiry ourselves.