What needs to move when you change hosting?
Look beyond the pages. Email, scheduled jobs, uploads, and new inquiries may need their own place in the plan.
Separate the services
Identify domain registration, DNS, hosting, email, media storage, scheduled tasks and important integrations. Record the authorized owner and support contact for each. Sharing an invoice doesn’t make them one system.
Also distinguish a hosting move with stable addresses from a move that changes domains or page URLs. Google's site-move guidance addresses search-facing transitions, while application and provider checks remain separate responsibilities.
Example: a scheduled report stays on the old host
The transferred pages may work while a background task still runs only on the previous environment. Staff notice later when a report or synchronization stops. Include scheduled work and its expected result in the inventory.
Rehearse representative tasks on the destination and note anything intentionally isolated. Prevent test copies from sending duplicate communications or modifying live records. The map should explain those differences.
Agree the final change window
For an active site, decide how new submissions and edits are handled between the rehearsal and final move. Keep the old environment available until the agreed verification point where feasible, subject to provider terms.
After the switch, verify the actual HTTPS site, login, forms, media and connected tasks. If addresses changed, follow important old links to their intended replacement. No move can promise unchanged search rankings or zero disruption in every circumstance.
The next step is a dependency review with the people who use the site. A small service map can uncover a much more consequential omission than a missing image, and it gives the team a clearer basis for deciding when the old hosting account can be closed.
Include provider cancellation as a separate decision after verification. A transfer being complete doesn’t establish that the old account contains no remaining mail, storage or required records.
Further reading: Authoritative guidance related to this topic.
The booking link still works after the move
Try the step after the obvious one. Send a marked test enquiry to the agreed internal destination, have the receiving colleague find it, and check what the visitor sees in return. A homepage that loads from the new host doesn't tell you whether the form and its delivery settings came with it.
You need to verify that the backend logic actually received the data before assuming the migration succeeded. For instance, if a customer submits a quote request on the live site, ensure the sales team's inbox lights up immediately rather than waiting for a manual email check later. This simple verification prevents the common scenario where the front end looks perfect but the back end remains silent.
Rehearse representative tasks on the day before launch to catch hidden dependencies. Do not assume that moving the website files automatically moves the application code or the database triggers. For example, a payment gateway integration might rely on specific server libraries that are not included in the new package, causing transactions to fail silently. Another team member should test the full workflow from the moment a user clicks a button to the moment they receive a confirmation. If the new host does not support the same PHP version or database engine, custom scripts could break unexpectedly. Write down exactly which tools must be installed on the new server so no one is surprised by an error message during the first real customer interaction.
Check the backup and restore procedures specifically for the new environment. A backup made on the old host might not be compatible with the new platform, leading to corrupted data if a rollback is needed. Verify that the new host accepts the file types and database formats your business currently uses. For instance, a large video file that fits on the old storage tier might be rejected by the new provider's quota limits, causing uploads to fail mid-process. Ensure the team knows how to trigger a test restore from a snapshot taken on the old server to confirm the integrity of the data. Without this check, a critical database corruption could go unnoticed until a real customer tries to access their account and finds it empty.
Document the specific permissions required for the new server to avoid lockouts during the cutover. The new administrator might not have the same access rights as the previous one, blocking access to configuration files or admin panels. For example, a marketing team member who previously had read-only access to the uploads folder might find it completely locked down on the new system, preventing them from updating product images. Clarify who needs write access, who needs database access, and who only needs to view logs. Keep a list of these roles separate from the technical staff. This ensures that when the new environment is live, the right people can make changes without waiting for IT intervention, keeping the business operational without delays.
