How to Plan Moving a Small-Business Website to a New Platform, Developer or Host
How should a small business plan for moving its website away from a platform, developer or hosting provider?
Plan the move in stages: define its scope, take control of accounts and website assets, inventory the current site, choose the replacement arrangement, document required design or URL changes, build and test the destination, and only then switch traffic. A website migration can affect crawling and indexing as well as customer experience, so preserve working URLs where practical, map unavoidable changes and keep the old arrangement recoverable until the new website has been checked.
- Ecomzier defines website migration as transferring a website from one hosting environment or platform to another.
- A Guide to Website Migration · As of 2026-11-16
- Moz says a domain-name change commonly occurs when a rebranding business moves from one domain to another.
- The Website Migration Guide: SEO Strategy, Process, & Checklist - Moz · As of 2026-11-16
- Ecomzier notes that replatforming can require design and URL changes because of technical limitations when platforms change.
- A Guide to Website Migration · As of 2026-11-16
- Makers’ Den says major changes to hosting, platform, URL structure, design or content can affect how search engines crawl and index pages.
- The Definitive Guide on Website Migrations - Makers’ Den · As of 2026-11-16
Define exactly what the move changes
Ecomzier defines website migration as transferring a website from one hosting environment or platform to another. Define the move in business terms before work begins by recording the current arrangement, intended destination, reason for moving and elements that should remain unchanged. Give one person authority to settle scope questions so a hosting transfer does not quietly become an unapproved redesign or content project.
Sources: A Guide to Website Migration.
- Name the current provider arrangement and intended destination.
- Mark each area as changing, staying or undecided.
- State the business reason and decision owner.
Separate the possible migration types
Moz says a domain-name change commonly occurs when a rebranding business moves from one domain to another. Treat a domain change as a separate decision from changing a host, and do not add it merely because another part of the website is moving. List platform, hosting, domain, URL structure, design and content in a scope record, then mark each item as unchanged, changing or deferred.
Sources: The Website Migration Guide: SEO Strategy, Process, & Checklist - Moz.
Moz also identifies migrations triggered by changes to a site’s content, structure, design or platform. Use that range as a prompt to find hidden work, not as a reason to bundle every possible change into the project.
Sources: The Website Migration Guide: SEO Strategy, Process, & Checklist - Moz.
- Separate hosting, platform, domain, URL, design and content decisions.
- Include only changes with a clear purpose.
- Record dependencies created by each proposed change.
Choose the destination and operating owner
Hypersite describes platform and CMS migrations as changes that can include switching content management systems, changing hosts or upgrading to a headless CMS architecture. Choose a destination only after deciding who will own billing, administration, routine updates, support requests and approval of future changes. Record those responsibilities before selecting an arrangement so the business knows who will operate it after the move.
Sources: Website Migration: Complete Guide to Migrating Your Site Without Losing SEO Rankings | hypersite.
Use the guidance on how to manage recurring website tasks to decide which duties remain with the business and which are assigned to a provider.
- Choose an arrangement the business can operate.
- Name owners for routine work and support.
- Document who approves future changes.
Inventory what must move and what may need rebuilding
Ecomzier notes that replatforming can require design and URL changes because of technical limitations when platforms change. Create an inventory of pages, media, forms, integrations, domains, accounts and customer-facing functions, then mark whether each item can transfer, needs rebuilding or can be retired. Do not assume a theme, custom component, licence or integration can be copied unchanged.
Sources: A Guide to Website Migration.
When replacement work includes generated or lightly supervised code, use the process to validate a vibe-coded website to set a review standard before release.
- List pages, media, forms and downloadable content.
- List integrations and business-controlled accounts.
- Mark each item for transfer, replacement or retirement.
Protect URLs, crawling and indexing
Makers’ Den says major changes to hosting, platform, URL structure, design or content can affect how search engines crawl and index pages. Keep working URLs where practical and make an old-to-new map for every priority address that must change. Include service pages, contact pages, campaign destinations and any address customers are likely to use directly.
Sources: The Definitive Guide on Website Migrations - Makers’ Den.
- Keep stable addresses where practical.
- Map every changed priority address.
- Check the live destination after switching.
Build a test and cutover plan around the full scope
Makers’ Den says CMS switches, domain moves, HTTPS changes and redesigns can carry search and user-experience risks. Test the destination through the customer tasks that matter most, including finding a service, contacting the business, submitting a form and receiving any expected confirmation. Assign separate people where practical to approve the switch, make the technical change, check customer tasks and decide whether to recover.
Sources: The Definitive Guide on Website Migrations - Makers’ Den.
Use website accessibility testing for important customer tasks, and apply privacy and consent checks when reconnecting analytics, advertising or chat tools.
- Test the customer tasks that matter most.
- Test forms, confirmations and connected services.
- Name the approver and recovery owner before cutover.
Switch, verify and keep a recovery path
Hypersite characterises a website migration as a significant change to site structure, platform, domain or hosting that affects crawling, indexing and ranking. Switch only when the planned checks, decision owner and usable recovery option are available, then verify priority pages, customer journeys and changed addresses on the live site. Keep the previous arrangement and current backups until the business has checked the replacement and accepted any remaining issues.
Sources: Website Migration: Complete Guide to Migrating Your Site Without Losing SEO Rankings | hypersite.
Before an irreversible or service-affecting change, confirm the current provider’s transfer, recovery and cancellation prerequisites in its own documentation.
- Switch only with named decision ownership.
- Check priority live pages and journeys immediately.
- Retain backups and the prior arrangement until verification is complete.
Website move decision map and owner checklist
Use this decision map to keep the move controlled. Complete each row before treating the next stage as ready, and record the person accountable for the decision.
| Stage | Business decision | Owner | Output before next stage |
|---|---|---|---|
| Scope | What changes and what stays? | Business decision owner | Written scope record |
| Control | Can the business access or transfer every essential account and asset? | Account owner | Control gaps list |
| Destination | Who operates, supports and approves the replacement arrangement? | Operating owner | Named operating model |
| Inventory | What transfers, rebuilds or retires? | Website lead | Asset and dependency inventory |
| URLs | Which priority addresses change and where do they go? | Content or technical owner | Old-to-new URL map |
| Testing | Do essential customer tasks and connected services work? | Test owner | Recorded test results |
| Cutover | Who approves, checks and recovers the switch? | Final approver | Cutover and recovery record |
This map is a planning aid, not a guarantee that every technical or search outcome can be predicted. Confirm the current provider’s prerequisites in its own documentation before any irreversible or service-affecting change.
When this is not the right approach: This approach is not a substitute for specialist technical help when the business cannot identify its accounts, has a complex custom system or faces an urgent service failure. Use the plan to clarify the work and obtain appropriate help rather than attempting an irreversible change without control or recovery options.
Related guidance
Another perspective
A website move is not merely a technical file transfer. Changes to hosting, platforms, URLs, design or content can alter what customers and search engines encounter, so business control and testing matter as much as moving the site.
What follow-up questions matter most?
- Is changing web hosts always a full website migration?
- No. Start by recording whether the change affects hosting, the website platform, the domain, URLs, design, content or several of these. Keep unrelated changes out of scope unless there is a clear business reason to include them.
- Do all website moves require URL changes?
- Not necessarily. Keep working addresses where practical and create an old-to-new map for addresses that must change. Check priority addresses after the switch rather than assuming they behave as intended.
- What should delay a website cutover?
- Pause when an essential customer task fails, critical business access is unresolved, routing is not understood, a usable recovery option is unavailable or nobody can approve and manage the decision. A visually finished site is not enough for a safe switch.
What steps does this workflow follow?
Plan a controlled small-business website move
- Define the move: Record what is changing and what should remain unchanged, including hosting, platform, domain, URLs, design, content and connected services.
- Secure business control: Confirm business-owned access or a documented transfer route for the accounts and assets needed to operate and recover the website.
- Prepare and map: Inventory the current site, choose the replacement arrangement and map any URLs or components that cannot remain unchanged.
- Test before switching: Check priority customer journeys, connected services and changed addresses on the destination before directing customers to it.
- Switch with recovery available: Make the change under named ownership, verify the live result and retain a usable recovery path until the replacement has been checked.