Website migration moves hosting, a platform, content or addresses while preserving the functions people still need. Zoha can plan the inventory, destination mapping, transfer and launch checks. A move that changes URLs also needs an SEO migration plan, including suitable redirects and post-launch monitoring. A hosting change is not automatically a redesign.
Updated
On this page
Define exactly what is moving
List the domain, hosting, CMS, content, documents, forms and connected services involved. A move to another host with the same addresses has different risks from rebuilding a large site on another platform. Make the scope visible before selecting the transfer method.
Confirm who controls the existing and destination accounts. Record the people who can approve content and the launch. A migration should not begin with a surprise that the organization cannot access its domain or export important information.
Build a content and address map
| Existing item | Destination decision | Check |
|---|---|---|
| Useful page | Keep its address or assign a suitable new one | Content and purpose remain available |
| Merged pages | Choose the best combined destination | Old visitors reach a relevant answer |
| Document or image | Transfer or replace with an approved version | Links and downloads work |
| Retired material | Record the removal decision | No misleading redirect to unrelated content |
Include addresses used in navigation, printed material and important external links. Avoid sending every old page to the homepage. A useful map explains the intended destination and who approved the content decision.
Include the SEO migration work
Preserve useful page titles and descriptions where appropriate, check the preferred public addresses and update internal links. If URLs change, arrange suitable server-side redirects and test representative old addresses. Review the new sitemap and make sure a staging restriction is not accidentally left on the live site.
Keep access to relevant Search Console and analytics accounts so the organization can monitor the change. Record a baseline of important pages and visitor tasks before the move. Temporary search changes can occur; no migration plan can guarantee every ranking or traffic level.
Rehearse the cutover and rollback
- Transfer a test copy and reconcile the content and required records.
- Test forms, downloads, logins where included and connected services.
- Choose a controlled change window and identify final approval.
- Account for records or submissions created during the transfer.
- Keep a recovery route until the agreed live checks are complete.
A hypothetical association might pause editing while the final content export is taken, then verify recent notices and form destinations before switching. That example illustrates a controlled process, not a promised timetable. Sites with active orders or user records need a specific plan for changes occurring during the move.
Hand over the new operating setup
After launch, test the agreed old and new addresses, important user journeys and notifications. Review errors and search information over an agreed follow-up period. Separate an urgent broken function from later design or content improvements.
The handover should identify account owners, renewal responsibilities, backup arrangements and any remaining work. Google's site-move guidance is a useful reference for URL changes; it distinguishes those from infrastructure-only moves. Your migration plan should reflect which kind of change is actually happening.
How this list was put together
Primary reference for search-related migration planning, reviewed on 4 November 2026.
Google Search Central
Official guidance for site moves that change existing URLs.