Define what is moving
A visual redesign, a hosting transfer and a CMS replacement create different work. State whether domains or URL paths change, which data must be retained and whether users need continued account access. Include files, media and third-party connections in the inventory.
For each item, record its source, destination, transformation and acceptance check. An export button does not establish that every field, relationship or password can be imported into the new system.
Use a migration worksheet
| Area | Evidence needed before estimating |
|---|---|
| URLs | Current inventory and intended destination for changed addresses |
| Content | Page types, fields, images and reusable templates |
| Business data | Record counts, dependencies and required history |
| Integrations | Credentials owner, field mapping and reconnect procedure |
| Search signals | Redirects, internal links, canonicals and sitemap plan |
| Launch | Freeze window, validation owner and rollback procedure |
Keep access credentials out of the worksheet. Record who manages them, and use the normal secure access process when implementation begins.
Pilot a representative sample
Move a small sample containing an ordinary page, a complicated page and a known edge case. Measure the work and identify which steps can be automated safely. A clean ten-page sample does not prove that every record in a large catalog is clean, so inspect exceptions before extrapolating.
A fictional budget might include 8 hours for inventory, 12 for mapping and tooling, 10 for exception cleanup, 8 for validation and 4 for launch support: 42 hours. At an assumed $75 per hour, that is $3,150 before tax, hosting overlap or custom data-recovery work. The example is a calculation method, not an observed migration price.
If the pilot exposes inconsistent data, update the estimate. Do not hide the extra cleanup inside a guessed percentage attached to the redesign price.
Treat the launch as a controlled transition
For changed URLs, follow Google's migration guidance and map important old pages to relevant new destinations. Validate redirects, internal links and the new sitemap. Avoid sending every removed page to the homepage simply to make a redirect report look complete.
Test the business journeys as well: forms, checkout, login and record updates. Keep a recovery route and assign responsibility for monitoring after launch. Search performance can fluctuate; passing technical checks does not guarantee preservation of traffic.
Use the redesign planner for the rebuild scope and add the migration estimate separately. Existing content is reusable only after its condition and destination requirements have been checked.