Plan the handover before removing access or cancelling services
A website provider handover needs an inventory, named owners and checks that the business can continue operating. Giving the new team a password does not complete that work.
Describe which relationship is changing. You might change maintenance only, commission a redesign or move hosting and email too. Different companies may administer each service even when you receive a single invoice.
Share the plan with the outgoing and incoming providers. Their knowledge helps identify dependencies and prepare next steps. Avoid cancelling services or removing necessary access before establishing how work will continue.
Use a handover worksheet with specific items
For each row, record who manages the item now, who will take it over, what needs handing over and how you will confirm the transfer. Use the worksheet to coordinate the work and share passwords, keys and recovery codes separately through a secure channel.
| Item | Identify | Check continuity |
|---|---|---|
| Domain | Managing account, contacts and renewal. | The authorised person can administer it and knows the next renewal. |
| Hosting and configuration | Account, hosted websites, requirements and connections. | The receiving team can perform its future tasks. |
| Website and data | Files, database, media and relevant documentation. | The delivery supports preparation and continuity testing. |
| Provider, mailboxes, configuration and owners. | Sending and receiving work in the test mailboxes. | |
| Licences and integrations | Terms, accounts, renewals and connected services. | Confirm what continues and what needs a new purchase or change. |
| Analytics and search tools | Properties, accounts and permissions. | Authorised teams retain necessary data and access. |
| Open work | Incidents, changes in progress and unresolved decisions. | Each item has context, an owner and a next step. |
The inventory does not determine ownership or whether a licence can transfer. Check those conditions in the agreements and with the relevant providers. Include any new account requirements in timing and cost.
Test access using the account that will be used afterwards
A screenshot does not establish that the receiving team can administer an account. Have an authorised person check access and the tasks they will perform: renewing a service, reviewing a backup or editing content, as applicable.
Where a platform supports individual permissions, prepare each person’s access at the level needed. Check who receives renewal notices and can recover the account when someone leaves. Our user and permission guide covers that review.
Search Console users, delegated owners and verified owners have different access arrangements. When administration changes, review verification methods too, as explained in Google’s permission documentation. Removing a user from one list does not replace checking all remaining access.
Separate the website change from the email change
Establish explicitly whether email stays with its current provider. Moving website hosting does not require moving business mailboxes, but the domain configuration can connect these services.
A domain’s MX records identify receiving mail servers, as described in Cloudflare’s technical explanation. If management of that configuration changes, include checks of email and other connected services.
If mailboxes are moving too, define what information must be retained, who prepares the migration and how sending and receiving will be tested. A working homepage does not demonstrate a completed handover.
Plan for changes arriving while the handover is being prepared
A copy prepared days earlier may not contain later enquiries, orders or content. During a move, agree how recent changes will be included and who authorises activation.
Moving WordPress can involve files and a database, with configuration changes depending on addresses and servers. Its official migration guide explains those differences. A copy used to review design is different from the final data of an active website.
Fictional example: a shop is copied to prepare a hosting move and subsequently receives orders. Before activating the new server, both teams identify missing data and how order details and statuses will be checked. Returning to an old copy without considering those changes could lose later information.
Checking backups and recovery helps prepare this work. If page addresses change, include the search transition plan too.
Review delivery through tasks your business recognises
Prepare a short list of important actions: opening services and products, searching, submitting an enquiry and following a booking or purchase journey where applicable. Coordinate tests that create data or notifications so they can be distinguished from real activity.
Record who performed each test, when, the result and anything unresolved. Also check required external links, received accounts and services that will keep renewing.
An open item needs a decision: correct it before the change, accept a known limitation or schedule specific work. Documentation lets the new team continue without reconstructing every discussion.
Finish the handover once continuity has been checked
Confirm which old services can be cancelled and when. Then review permissions no longer needed, recovery contacts and billing notices. Retain documentation and the terms of follow-up support.
If a new website is included, use the redesign delivery checklist too. It helps distinguish handover work from an additional project.
Nodo91 can help review the website’s condition and define transition checks. Tell us which service is changing and we can discuss the required work and coordination with the teams involved.