CMS migration
Off an ageing platform, with your data, URLs and rankings intact.
Moving off an ageing or unsupported platform without losing data, rankings or the integrations your organisation runs on. We map every field and every URL before build, rehearse the migration with your real data, and plan the cutover down to the rollback.
Where are you migrating from?
What every migration includes
Whatever the platform, the same things decide whether a migration goes well.
A data map
Every content type and field mapped from old to new, signed off by its owner.
A redirect plan
Every old URL mapped to its new page, tested before launch.
Rehearsals
Repeated test migrations of real data, so the final run holds no surprises.
An integration decision
Every connection kept, rebuilt or retired, decided in discovery.
A short freeze
Content frozen for days rather than weeks, because the run is rehearsed.
A rollback plan
Parallel running and a way back, until you are confident in the new platform.
Five stages. Six to nine months.
Workshops, a data and systems audit, decision log.
Content model, data mapping, redirect plan, integrations.
Staged releases and repeated test migrations of real data.
Freeze, final migration, redirects, parallel running, rollback.
Training, documentation, support through WebsiteSupport.io.
Questions we get asked
If yours isn't here, it's usually quicker to ask on the phone.
Most run six to nine months including discovery. Smaller, simpler sites are quicker, and we will tell you which yours is on the first call.
Not if the redirects are planned. Every old URL is mapped during architecture, tested before cutover and monitored afterwards.
Usually days rather than weeks, because the final run has been rehearsed with your real data.
Start with a readiness review
A free 30-minute call with a technical lead, then a short written summary of your options. No commitment beyond that.
020 3608 2525