Service detail

Move the site with a plan for what must survive.

A migration is a controlled change of platform or hosting, with content, data, URLs and operational dependencies accounted for.

01 / Service detail

Check the starting condition

Choose by the actual obstacle and readiness. A different or smaller intervention can be the appropriate result.

Fit, reason to wait and a useful alternative
Decision	Condition
Explore this scope when	A defined source/target move is needed and the important data and tasks can be inventoried.
Pause or choose another scope when	The source/target pair is unsupported, essential data is unknown or no safe recovery path exists.
Before commissioning work	Agree the named output, supported platform, responsible role and a testable finish line. No purchase, account access or live action is authorized by reading this page.

Work through the earlier decision

02 / Service detail

Inventory before choosing a moving day

List pages, media, structured content, forms, accounts, redirects, integrations and any important operational records. Establish which source and target platforms can actually be supported before quoting the move.

03 / Service detail

Map content and URLs deliberately

Define the target structure and map each old URL or data type to its destination. Decide how retired content is handled. A URL map is an implementation input and a test record, not a last-minute spreadsheet.

04 / Service detail

Map what moves before changing the platform

Hypothetical planning specimen. It explains the decisions and checks to agree; it is not a completed customer deliverable or a fixed offer.

Synthetic migration mapping
Old item	New destination / action	Verification	Rollback checkpoint
/services/example/	Retain or approved equivalent URL	Status, content, canonical and internal links	Preserved original route/content inventory.
Retired duplicate	Approved merge target and redirect	Redirect chain and final useful destination	Original mapping and changed-file record.
Media / data	Named export/import fields and assets	Record/asset counts plus representative content checks	Usable export and restore test.
Forms / connected tools	Scoped destination and supported configuration	Authorized end-to-end tests; no copied private secrets	Previous working configuration and manual fallback.
Mail / DNS	Explicit change or preserve decision	Relevant records and ordinary mail operation verified by authorized owner	Known prior records and responsible administrator.

Who should own your website and accounts?

05 / Service detail

Rehearse cutover and rollback

Hypothetical planning specimen. It explains the decisions and checks to agree; it is not a completed customer deliverable or a fixed offer.

Migration go/no-go register
Stage	Evidence	Hold / recovery
Inventory / mapping	Sources, targets, priority tasks and data owners agree	Unknown essential records or unsupported source/target pair.
Rehearsal	Staged import, counts, URLs and representative functions reconcile	Failed restoration or missing critical content.
Cutover	Freeze, final sync, owner and approved release window	Unexpected write activity or irreversible unsupported step.
Live verification	Priority URLs, forms, content and mail/DNS behavior checked	Named rollback trigger, owner and time-sensitive constraints.

How it works

06 / Service detail

Rehearse the change

Use a staging copy or test import where practical. Compare counts, relationships, assets, customer journeys and search controls. Confirm licensed components and any data that cannot be carried over.

07 / Service detail

Plan cutover and rollback together

Define backup ownership, DNS or hosting changes, a freeze window if needed, the person authorized to release and the criteria for rolling back. A backup should be usable by the person responsible for recovery.

08 / Service detail

Verify after the move

Expected content and media present at the intended destinations
Critical forms and operational connections tested with permission
Old URLs return the intended redirects or appropriate status
Production canonicals, sitemap and indexing rules reviewed
Known limitations, access and follow-up monitoring handed over

09 / Service detail

Specialist fit comes before commitment

No. Confirm support for the source and target platforms, agree a rehearsal and specify recovery tests before committing. Sensitive records, complex commerce and incident recovery require a separate assessment.

Websites that make the next step easier

10 / Service detail

Agree the inputs, effort and boundary

Use these work variables to compare a written scope. They are not a price list, payment policy or authorization to purchase tools, media or services.

Scope preparation and cost drivers
Buyer question	Scope answer to agree
What will I receive?	An inventory/mapping plan, rehearsed cutover and verification/handover
What do I need to supply?	Source/target, accounts, important URLs/data, integrations, write activity and what cannot stop
What changes the effort and cost?	System differences, data quality, transactions, redirects, mail/DNS dependencies and rollback constraints
What needs separate scope or is excluded?	Universal source/target compatibility, zero-loss/rank guarantees and unspecified systems
How will completion and support be defined?	Identify the reviewer, actual test evidence, known limits and handover. Any recurring allowance, fees, cancellation and response arrangement need their own written terms.

To keep the deliverable and finish line reviewable: Review the acceptance and handover checkpoints

Scope and pricing

11 / Service detail

Start with the reason for moving

Name the source platform, intended destination, operational reason and what must stay available. A first conversation should not require putting a database export or passwords into a public form.

Tell us what you need