Hands typing on a laptop

CMS and legacy platform migration

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 you're starting from

  • Drupal 7
  • Drupal 10
  • Sitecore
  • SharePoint
  • Optimizely
  • Bespoke systems

Where you go next is decided in the Blueprint. Sometimes the answer is to upgrade.

Where are you migrating from, or to?

Off an ageing platform, with your data, URLs and rankings intact.

Drupal migration and upgrades →

Upgrade, or move off Drupal. Whichever fits, we've done both.

Legacy platform migration →

Off Sitecore, SharePoint, Optimizely or a bespoke CMS, without losing what it quietly does.

Contentful migration →

Into Contentful from almost anything, scripted and rehearsed until cutover is routine.

What every migration includes

Whatever the platform, the same things decide whether a migration goes well.

1

A data map

Every content type and field mapped from old to new, signed off by its owner.

2

A redirect plan

Every old URL mapped to its new page, tested before launch.

3

Rehearsals

Repeated test migrations of real data, so the final run holds no surprises.

4

An integration decision

Every connection kept, rebuilt or retired, decided in discovery.

5

A short freeze

Content frozen for days rather than weeks, because the run is rehearsed.

6

A rollback plan

Parallel running and a way back, until you are confident in the new platform.

Five stages. Six to nine months.

  1. DiscoveryWorkshops, a data and systems audit, decision log.
  2. ArchitectureContent model, data mapping, redirect plan, integrations.
  3. Build and migrateStaged releases and repeated test migrations of real data.
  4. CutoverFreeze, final migration, redirects, parallel running, rollback.
  5. HandoverTraining, documentation, support through WebsiteSupport.io.

Questions

If yours isn't here, it's usually quicker to ask on the phone.

How long does a migration take?

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.

Will we lose our search rankings?

Not if the redirects are planned. Every old URL is mapped during architecture, tested before cutover and monitored afterwards.

How long will our content be frozen?

Usually days rather than weeks, because the final run has been rehearsed with your real data.

Start with a Blueprint!

Three weeks, from £5,500 + VAT. Credited against the build, and yours to take to any supplier.