Website and CMS migration.

A planned transition between content systems, with page mapping, validation and editor handover.

Two editors arrange illustrated content cards in a cabinet and on a website layout.

List everything before moving anything.

We identify what needs to move, what can be retired and how the new system will represent it. The migration plan includes URLs, assets and relationships as well as the visible page copy.

What we can build together.

The final deliverables, review rounds and schedule are agreed around your brief.

Content inventory: List page types, assets, metadata and dependencies in the current system.
Mapping and transformation: Define how existing fields and relationships fit the new content model.
Migration and validation: Import a sample, resolve issues and check the agreed full migration.
Launch planning: Prepare URL handling, editor access and the transition between systems.

Keep a map of what moves.

Reconcile the content inventory

Record each source page, its destination and the treatment of its assets and metadata. Test representative content before the full move. Keep a list of exclusions so a missing page can be distinguished from an intentional retirement.

Treat URL changes as a separate launch task

If addresses change, plan the mapping and permanent redirects alongside the content move. Google’s migration guidance also calls for updating internal links. A successful import alone does not prove that visitors and search engines can still reach the right pages. Read Google’s site-move guidance.

From brief to handover.

Audit the source
Review export options, content quality and the full set of pages to preserve.
Test a sample migration
Move representative content and validate it in the new editor and website.
Complete and reconcile
Check the migrated inventory, links and agreed URL behaviour before release.