Migration continuity
Usually the existing website remains public while UKC prepares and tests a copy. The final switch can often be made without a visible outage, although busy database-driven sites may need a short maintenance window to prevent data being written to both servers.
Old site stays liveThe initial copy and most testing happen before public DNS changes.
Caches split trafficSome visitors may reach the old server briefly while others reach the new one.
Dynamic sites may pauseA controlled write freeze protects orders, accounts and content during final sync.
Normal process
UKC normally copies the website to the new hosting service while the old server continues serving visitors. The new copy is configured and tested using a preview method or local hosts-file override. DNS changes only after the site is ready.
This approach makes a small static or brochure site capable of switching with little or no visible interruption.
Changing data
Shops and paymentsOrders must not be accepted independently on old and new databases.
Membership sitesNew registrations, password changes and account updates need one authoritative database.
Forums and publishingPosts, comments and uploads made after the copy need a final sync.
Bookings and formsSubmissions must be captured once and delivered to the correct system.
For these sites, UKC may recommend maintenance mode during the final database sync and DNS switch. The expected window is agreed after assessing the application and data-change rate.
DNS transition
DNS resolvers cache answers for their TTL. After the switch, some visitors may continue reaching the functioning old server while others reach the functioning new server. This is split traffic rather than complete downtime.
Cancelling it immediately can turn cached old DNS answers into an outage. Wait until traffic and essential services are confirmed on UKC.
Email continuity
Changing a website A record does not require changing MX records. If email is also migrating, retain the old mail service during propagation, recreate mailboxes first and perform a final message sync where possible. Devices must be updated only when the mail route or server credentials change.
Reduce risk
After cutover
Open the website over HTTPS from more than one network. Test login, forms, orders, payments and mail. Review application and web-server logs for errors, and compare new records with activity on the old server before declaring the move complete.
Plan your migration
Include the domain, application/CMS, busy times, changing data, mailboxes, payment or booking flows, acceptable maintenance window and preferred switch date. We can then advise whether a write freeze is needed.
Need a continuity plan?Open a migration ticket before changing DNS or cancelling the old service.
