Before changing website providers, agree what will be handed over, who controls each account, and which services must continue working. A copy of the visible pages is only part of the picture. Domain settings, business email, form notifications, publishing access, and third-party subscriptions can sit in different accounts.
Start the conversation before canceling the current service. What can be transferred depends on your agreement and the systems involved. Ask both providers to name the work they will handle, anything they cannot transfer, and the costs or notice periods that apply.
Make an account and responsibility inventory
| Item | Handover question |
|---|---|
| Domain and DNS | Who controls registration, renewals, and the records directing website and email traffic? |
| Hosting and publishing | What files or source code are available, and how will the new provider publish and restore the site? |
| Content and media | Which text, images, licenses, and editable originals can you use after the move? |
| Forms and connected tools | Where are inquiries received, and who controls notifications, booking tools, and subscriptions? |
| Search and analytics | Who has access to the relevant properties and the information needed to review the move? |
Use account invitations or an agreed secure handover process rather than placing passwords and secret keys into a shared project brief. Keep a named owner for renewals and billing after the move.
Separate the website move from business email
Ask the new provider to identify the DNS records and services that must remain. Changing where the website is hosted does not by itself define a plan for mailboxes. Confirm whether email is part of the work, who administers it, and how it will be checked after any DNS change.
The same applies to forms. A working page can depend on a database, email service, or booking account outside the hosting plan. Agree how those connections will be transferred or replaced and how successful receipt will be verified.
Preserve useful content and page addresses
List the public pages before work begins. Mark which addresses will stay, which will change, and which content is genuinely being retired. If addresses change, include a plan for relevant redirects and checks after release in the scope.
For example, our Lighthouse project has separate location menus, events, and private party information. A handover inventory for that kind of site should account for each customer destination rather than treating the homepage as the entire website.
Google's Search Console introduction describes tools for reviewing search performance and how Google finds pages. Retaining appropriate property access helps the responsible provider investigate after a change. It does not guarantee that search visibility will stay constant.
Define the release and support period
Ask who approves the new site, who makes the switch, what happens if a check fails, and how long the old setup remains available. Verify main pages, phone and email links, form receipt, location information, and connected tools. Assign a contact for problems discovered after launch.
Get a scoped handover estimate
A provider change can be a small transfer or a rebuild if the current setup cannot be moved as expected. We review the website and available access before confirming what we can take on. Zay Web Solutions bills website work at $100 per hour; annual hosting is $500, billed separately. Domain fees, third-party subscriptions, and any separate work need their own confirmation.
Explore our redesign approach and website care responsibilities, or send your website and explain the provider change you are planning.