Service

Content migration

Getting years of content out of an old system and into a new one with its structure, its media and its URLs intact.

What you get

  • Content inventory and field mapping
  • Custom Migrate source and process plugins
  • Media and inline-link rewriting
  • URL alias and redirect preservation
  • Repeatable, re-runnable migration
  • Row-level reconciliation report

The Migrate API handles the straightforward eighty per cent. The work is in the rest: a field that meant three different things over a decade, inline links pointing at files that moved, a taxonomy that grew organically, users whose accounts came from an SSO provider that has since changed.

We write custom source and process plugins for those cases — entity and field mappers, media-link extraction and rewriting, redirect validation and path conversion, webform submission migration, user and authmap de-duplication — so the migration is repeatable. It has to be: you will run it many times before you run it for real.

Questions we get asked

They should, and that is a deliverable rather than a hope. Old aliases are migrated and, where the structure genuinely changed, redirects are generated and validated. Breaking a decade of inbound links is the most common and most avoidable migration failure.

The inventory surfaces it early — the thousands of pages last edited in 2014. Migration is the one good moment to decide what not to bring, and that decision belongs to you, not to us.