Plan a migration that can be reconciled
A new website needs a content and URL migration plan, not just a new layout.
Newton & Carter. Published November 7, 2026; updated November 9, 2026. Version 1.1.
Inventory before building
Record source URLs, content types, owners, attachments and integration dependencies. Identify the user tasks that must keep working.
Agree destinations and redirects
Give each retained item a destination and owner. Distinguish intentional removal from missing content. Test permanent redirects, internal links and search results.
Reconcile and rehearse
Compare the source and destination inventory, record exceptions and rehearse rollback. Test the priority journeys with real roles in the agreed environment.
References for the work
Use these published resources when defining the requirements for your project.
- Google Search Central: site moves with URL changes ↗
Review URL mapping, permanent redirects, launch checks and search monitoring.
Synthetic planning sample / Version 1.0
CMS migration and redirect plan
/departments/public-works/trash/services/waste/forms/permit.pdf/services/permitsReconcile all agreed records and resolve failed priority journeys before launch.
Put the plan to work
Inspect the versioned source and discuss the structure of your engagement.
Inspect the related versioned sample ↗These are planning practices, not a universal scope, legal interpretation or delivery guarantee. Agree the criteria that apply to your project.
Bring your project brief ↗