Before changing DNS for a hosting move, you need evidence that the website works on the new hosting. Seeing the homepage load is a useful first check, but it does not demonstrate that enquiries arrive, account access works or the copied information is current. A practical test should follow the tasks that customers and staff depend on.
The test also needs to identify which environment you are actually using. A preview can look correct while some links, images or connected services still refer to the existing website. This guide explains how to plan a hosting verification exercise before the public change, record the results and decide what still needs checking afterwards.
Agree the scope of the move first
Write down what is moving and what is staying with its current provider. The website, database, email service, DNS management and domain registration are separate items in the plan. Your supplier should explain the particular change being proposed, rather than treating “moving hosting” as permission to alter all of them.
Identify the person responsible for the migration and the business owner who can confirm the customer journey. Include other suppliers where a connected tool belongs to them. A booking integration or customer management system may require a separate check that the website hosting team cannot complete alone.
Agree how the test environment will be distinguished from the live service. Use controlled test records and approved test contact routes. Ask the technical owner to explain how customer messages, payments and other consequential actions will be handled during testing, so a rehearsal does not create unintended live activity.
Choose a preview method supported by the new host
Ask the hosting provider for its supported way to view the copied site before the public DNS change. A temporary URL may be available, but it can behave differently from the intended live hostname. Follow the destination host's supported preview method and record which checks still need the real domain. Our hosting migration checklist provides the related checks.
Some tests also need the intended hostname. A developer can use a controlled request method where appropriate. For example, curl's --resolve option supplies a chosen address for a hostname and port within that request. This allows a technical check against a specified destination without changing public DNS. It does not replace testing the complete live arrangement. Our pre-migration testing checklist provides the related checks.
Ask the developer to explain what their method proves and what it leaves untested. A command-line response check and a browser journey serve different purposes. The business reviewer needs a usable route for checking content and interactions, while the technical reviewer needs to confirm the destination and relevant configuration.
Confirm that the preview really reaches the new environment
Have the technical owner provide evidence of the environment being tested. This could be an agreed environment identifier or a server-side record of the controlled test request. The exact method depends on the hosting setup. A familiar page design alone is insufficient evidence because both environments may contain the same copied site.
Check what happens when you follow navigation and submit forms. Does the journey remain in the intended test environment, or does it send the visitor back to the current live site? Record those observations so the team can distinguish a preview limitation from an implementation problem.
Discuss secure connections and hostname-specific behaviour with the provider. Do not treat bypassing a certificate warning as a successful HTTPS test. If a preview method cannot demonstrate the required configuration, record that limitation and agree another supported check. Keep the test findings accurate about what has actually been verified.
Check the copied content and important records
Agree when the copy was taken and which information may have changed since then. A business website can receive new enquiries, content edits or transactions while migration preparation is under way. The team needs a plan for handling those changes before the final move.
Inspect representative pages across the main templates. Include service pages, contact information, blog articles, downloadable material and any account or product pages relevant to the site. Check text, photographs, menus and supporting links. Use important real addresses from the current website rather than only browsing newly created preview pages.
Ask the staff responsible for business records to verify suitable samples. A copied booking list or product catalogue needs more than a visual design check. Confirm that the information required for the customer task is present and meaningful. Record the sample, expected result and actual result without putting unnecessary private data in the shared test notes.
Test complete customer journeys
Select a small set of tasks that matter to the business. A service visitor might find the relevant page, complete an enquiry and receive a clear acknowledgement. A returning customer might sign in and find an existing record. A shopper might choose an item and complete an agreed test checkout through the supported testing arrangement.
Follow each task from start to finish. Check required fields, helpful error messages, confirmation screens and the record received by staff. Inspect the resulting message or system entry with the person responsible for handling it. A form that displays “thank you” has not yet demonstrated that the business received the enquiry.
Test on a phone as well as a larger screen. Include a realistic mistake, such as an incomplete field, to check whether the visitor can recover. Record exactly where an issue occurs. “Booking does not work” is less useful than a description of the page, action and missing result.
Review connected services with their owners
List the services the website uses or contacts. These might include email sending, booking tools, payments, maps, customer records and scheduled background tasks. Ask the developer which connections need different configuration in the new environment and which use a separate test mode.
Agree evidence for each important connection. For an enquiry route, staff should be able to find the controlled record. Ask the technical owner to show the expected run and result of a scheduled task. The relevant system owner should confirm that an external integration test was received and handled appropriately.
Keep website verification separate from email migration verification. The preview does not by itself demonstrate that public mail routing has changed correctly. If email is also moving, give it a separate test plan and owner. If it is staying put, ensure the DNS change plan preserves the approved email arrangements.
Record issues in a way that supports a decision
For each test, record the task, environment, time, expected behaviour and observed behaviour. Include an issue owner and the evidence needed to close it. A screenshot can help show a layout problem, while a delivery record may be more useful for an enquiry handover.
Distinguish launch-blocking problems from improvements that can follow later. The business should agree that distinction based on the affected task. An unavailable enquiry route is different from a minor spacing issue on a rarely used page. Avoid silently accepting a serious problem because the homepage looks finished.
Repeat the relevant checks after a fix. Keep the result with the original issue so the decision record shows why it was closed. If the site changes substantially during preparation, review whether earlier test evidence still applies to the final version.
Agree the final change and follow-up checks
Before changing public DNS, confirm the remaining work, the current copy, the responsible people and the recovery plan with the technical owner. Include any short period when editing or transactions need to be controlled. The decision should be based on the agreed test results and preparation, not simply a calendar date.
Plan checks after the change too. Customers will use the public route, so the team must verify important journeys through that route and confirm that staff can operate them. Keep the previous environment available according to the agreed migration plan until the technical owner confirms it is no longer required.
Giraffe Digital's digital strategy services connect website journeys with the supporting tools and processes. Hosting tests support that connection when they prove a working task, identify the environment and give the business clear evidence for the move.
Frequently asked questions
How should we agree the scope of the move first?
Write down what is moving and what is staying with its current provider. The website, database, email service, DNS management and domain registration are separate items in the plan. Your supplier should explain the particular change being proposed, rather than treating "moving hosting" as permission to alter all of them. Identify the person responsible for the migration and the business owner who can confirm the customer journey. Include other suppliers where a connected tool belongs to them. A booking integration or customer management system may require a separate check that the website hosting team cannot complete alone. Agree how the test environment will be distinguished from the live service. Use controlled test records and approved test contact routes.
How should we confirm that the preview really reaches the new environment?
Have the technical owner provide evidence of the environment being tested. This could be an agreed environment identifier or a server-side record of the controlled test request. The exact method depends on the hosting setup. A familiar page design alone is insufficient evidence because both environments may contain the same copied site. Check what happens when you follow navigation and submit forms. Does the journey remain in the intended test environment, or does it send the visitor back to the current live site? Record those observations so the team can distinguish a preview limitation from an implementation problem. Discuss secure connections and hostname-specific behaviour with the provider. Do not treat bypassing a certificate warning as a successful HTTPS test.
How should we test complete customer journeys?
Select a small set of tasks that matter to the business. A service visitor might find the relevant page, complete an enquiry and receive a clear acknowledgement. A returning customer might sign in and find an existing record. A shopper might choose an item and complete an agreed test checkout through the supported testing arrangement. Follow each task from start to finish. Check required fields, helpful error messages, confirmation screens and the record received by staff. Inspect the resulting message or system entry with the person responsible for handling it. A form that displays "thank you" has not yet demonstrated that the business received the enquiry. Test on a phone as well as a larger screen.
How should we review connected services with their owners?
List the services the website uses or contacts. These might include email sending, booking tools, payments, maps, customer records and scheduled background tasks. Ask the developer which connections need different configuration in the new environment and which use a separate test mode. Agree evidence for each important connection. For an enquiry route, staff should be able to find the controlled record. Ask the technical owner to show the expected run and result of a scheduled task. The relevant system owner should confirm that an external integration test was received and handled appropriately. Keep website verification separate from email migration verification. The preview does not by itself demonstrate that public mail routing has changed correctly. If email is also moving, give it a separate test plan and owner.
How should we agree the final change and follow-up checks?
Before changing public DNS, confirm the remaining work, the current copy, the responsible people and the recovery plan with the technical owner. Include any short period when editing or transactions need to be controlled. The decision should be based on the agreed test results and preparation, not simply a calendar date. Plan checks after the change too. Customers will use the public route, so the team must verify important journeys through that route and confirm that staff can operate them. Keep the previous environment available according to the agreed migration plan until the technical owner confirms it is no longer required. Giraffe Digital's digital strategy services connect website journeys with the supporting tools and processes.


