SERVICES / Website Migrations
WEBSITE MIGRATIONS
Move your site, without breaking it.
Migrating to a new host, a new platform, or a new domain is the moment most websites lose data, lose SEO, or break in subtle ways nobody notices for weeks. We handle migrations end to end so the new site works the day you cut over, the way the old one did the day before.
WHAT WE MIGRATE
The migration scenarios we deliver
Host-to-host migration
Moving the same site to a different hosting provider. Common reasons: cost, performance, support quality, security.
Platform replatform
Moving between CMS or e-commerce platforms. Content, structure, redirects, integrations reproduced or mapped.
Domain or brand migration
Moving a site from one domain to another, often after a rebrand. The hard problem is the redirect map and SEO continuity.
Consolidation of multiple sites
Merging two or more sites into one, after acquisitions or brand consolidation. We map every URL, form and integration.
Major version upgrade
Upgrading a site from an end-of-life CMS version or old technology stack onto a current, supported stack.
Staging-to-production cutover
For developers and agencies who built a new site on staging and need a clean, safe cutover to production.
THE STUFF THAT BREAKS
Migrations don't fail at the database. They fail at the details.
A bad migration usually looks fine on day one. Then over the next few weeks the symptoms appear: search rankings dropped, a form stopped sending, the favicon disappeared, half the images are 404s, email started bouncing because somebody forgot the SPF record.
Our migration checklist is over two hundred items long for a reason. Every item is a lesson learnt from someone else's painful migration. We don't expect you to read the checklist. We expect to deliver against it.
METHODOLOGY
Five stages, with sign-off between each
Migrations are run as a structured project, not an overnight stunt. You see the plan before we start and you have a rollback path at every stage.
01
Audit
Site inventory: pages, redirects, forms, integrations, mail config, DNS, SSL. Output is a written migration plan.
02
Staging
Migrate to a staging environment first. Test every page, form and integration. SEO sanity-check before cutover.
03
Dry run
Rehearsed full migration in a controlled window. Surfaces the issues that only appear when you actually move the site.
04
Cutover
Run out of hours. Engineers on call, rollback path ready. DNS, mail, SSL, analytics reconfigured and verified.
05
Hyper-care
Two weeks of dedicated post-migration monitoring. Anything that surfaces is fixed inside project scope.
FREQUENTLY ASKED
Common questions
Do you handle the SEO side of a migration?
Yes. Redirect mapping, canonical URLs, sitemap generation, Search Console reverification, structured data integrity, and a SEO sanity check on staging before cutover.
What about email if we are moving the domain too?
Mail is the most common collateral damage. SPF, DKIM, DMARC, MX records, mailbox migration, all handled in the right order so mail doesn't bounce.
Can you migrate a site you didn't build?
Yes, this is most of what we do. We assess the codebase first, document what's there, and propose a migration plan.
How much downtime should we expect?
For a standard host-to-host migration: minutes, not hours. For a major replatform: a planned outage window during a low-traffic period.
What if something breaks after cutover?
Anything that emerges during the two-week hyper-care window is fixed inside the project scope, no variation invoice.
How is it priced?
Fixed-scope projects after the audit phase. The audit is a small fixed-fee engagement that gives you the migration plan and a fixed quote.
Got a site that needs to move? Start with the audit.
30-minute scoping call to understand what you have and where it needs to go, followed by a paid audit phase that delivers a written migration plan and a fixed quote.
RELATED READING