How to move your website without losing enquiries

During the move, some visitors may end up on the old server, and some on the new one. If both save requests in different databases, the manager will see only part of the requests. Therefore, start by deciding where the data will be recorded at the time of switching.

This plan is suitable for a site with forms, orders, or a client dashboard. Go through it with the developer and the person who accepts enquiries. The latter will best notice that the request has been saved, but has not appeared in the work queue.

1. Identify every enquiry channel

List forms, chat, registration, file uploads and ordering. For each channel, write down where the record is stored, who receives the notification, and how the manager knows to respond to the client.

Check for hidden dependencies. For example, a form can save a request in WordPress, send an email, and separately create a deal in CRM. Check all three results. The diagram can be checked with the article about the path of the enquiry to the manager.

2. Back up the site and test the move

Save the database, files, application settings and everything you need to restore queues and tasks. Keep a copy separate from both servers. Make sure the archive can be read and the database can be restored in a test environment.

Deploy a copy on a new server before changing DNS. Restrict access to it and disable sending real emails and messages while you are checking forms. Details are described in the article about checking backups.

3. Follow the customer journey

Send a test request from your phone and computer. Check the confirmation on the screen, the entry in the database, the appearance in the CRM and the delivery of the notification. If the form accepts attachments, open the file from the enquiry card under the employee’s account.

Do the check with the external service disabled or unavailable. If the CRM did not accept the data, it should be clear where the enquiry remains and how to resend it. Record the expected outcome for each step so that it can be repeated after the move.

4. Choose one place to record new enquiries

Determine in advance where enquiries from visitors who are still opening the old site will be sent. One option is to configure the old server so that the forms pass data to the new handler. Check this before switching, including protecting the form and resubmitting.

If you cannot securely link the servers, agree on a work window and temporarily close the record to the old database before the final transfer. During the pause, indicate a proven backup communication channel. Before opening forms on the new server, make sure that the final copy includes enquiries received after the trial transfer.

5. Switch the domain

Prepare the certificate and verify that the new server correctly serves the main domain and the required subdomains. Check which DNS records apply to the site. If only the site server is changing, check that the mail settings continue to point to the correct provider.

After switching, check the site from a different network and look at the logs of both servers. Some visitors may continue to access the same address due to DNS caching. Leave the old server available to handle such requests consistently and monitor its traffic.

6. Reconcile records after the move

Fix the time of the final copy and mark the last enquiry that was included in it. Verify records for the period around the switchover by identifiers, time and channel of receipt. The same number of lines does not mean that the records themselves match.

Separately check attachments and resubmissions. If one request hits both servers, save the processing history and eliminate the duplicate according to an agreed rule. Ask the manager to confirm that test and new work requests are visible where he usually processes them.

Before switching, write down unfinished background tasks. If the old and new copies launch the same queue at the same time, the client may receive a repeat letter, and two cards will appear in the CRM. Agree on which server tasks run on before the switchover and when they are allowed to run on the new one. For your first work request after moving, record the submission time, ID, and result of each step. If it does not reach the manager, this data will help find the point of failure: the form processor, record saving, notification queue, or external service. Do not resend the entire queue until you know which tasks have already completed.

7. Prepare a safe rollback

Assign someone responsible for the rollback decision and write down the conditions for it. For example, new requests are visible in the browser, but not in the work queue. Check who will stop the recording and where the data received by the new server will be stored.

If you return only the old DNS, some of the fresh requests may remain in the new database. Before rolling back, download the changes and determine how they will get to the production system. After returning, repeat the test from submitting the form to confirmation from the manager.

8. Complete the migration checklist

Remove the old server from service after checking the traffic, reconciling enquiries and confirming the operation of integrations. Leave a backup copy and write down where the database, files and logs are now so that support can find them the next time there is a failure.

Describe the site and ticket channels in the briefto agree on the migration scenario and verification criteria before changing hosting.