Website migration checklist
Copy, test and switch your website before cancelling the old hosting
A safe migration keeps the existing site online while a complete copy is prepared on the new server. Move files, databases, email and configuration, test with temporary access, then change DNS. Keep the source account and backups until the new website and mail have been proven.
What should you collect before moving a website?
Website files and database
Identify the document root, application files, uploads, database names and current database credentials.
Software requirements
Record the PHP version, extensions, scheduled tasks, rewrite rules, storage use and any application-specific server settings.
DNS and domain access
Export the current DNS zone and confirm who controls nameservers. Note any third-party email or verification records.
Email accounts and messages
List every mailbox, alias and forwarder. Decide whether old messages must be copied and obtain the necessary passwords.
How do you move the site safely?
- 1Create independent backups
Back up files and databases outside the old hosting account. Check that the archives can be opened.
- 2Prepare the destination
Create the domain, database, users, PHP settings and required applications in Plesk.
- 3Copy files and data
Transfer site files and import the database. Update configuration with the new database credentials.
- 4Test before changing DNS
Use a preview method or local hosts-file entry. Check pages, login, forms, images, checkout and scheduled tasks.
- 5Prepare SSL and email
Create mailboxes and issue certificates when DNS and validation permit. Keep both mail systems available during the change.
- 6Switch DNS and monitor
Change only the required records, then watch web and email traffic while cached answers expire.
How do you prevent lost email?
Recreate addresses first
Create destination mailboxes, aliases and forwarders before changing MX or nameserver records.
Copy old messages separately
Website files do not contain mailbox contents. Use an IMAP migration or another supported mail-copy method.
Keep the old service active
Some senders will use cached DNS. Check both old and new mailboxes until the transition is complete.
Update mail applications
For UKC shared hosting, use the assigned server hostname such as ukc10.uk to avoid certificate mismatch warnings.
How should you make the DNS switch?
Preserve every required record, including MX, SPF, DKIM, DMARC and third-party verification entries. Change the website’s A or AAAA record, or its nameservers, only after the destination copy is ready. DNS propagation is cache expiry, not a fixed 48-hour event: some users may reach either server during the transition.
What should you check after migration?
Customer journeys
Test contact forms, orders, account login, password reset and any payment callbacks using real end-to-end steps.
Search continuity
Keep the same URLs where possible. Use specific permanent redirects for genuinely moved pages and retain analytics and Search Console verification.
Security and backups
Confirm HTTPS, application updates, Imunify protection and a suitable backup schedule on the destination.
Logs and monitoring
Review error logs, storage, resource use and failed mail. Fix hidden errors before closing the old service.
Website migration questions
Will a migration cause downtime?
Careful preparation can reduce or avoid visible downtime, but dynamic sites and email require a plan for changes that happen during the final switch.
Can UKC move my website?
Ask UKC Support with the current host, platform, site size and number of mailboxes. The team can confirm feasibility, access required and any charge before work begins.
Should I transfer the domain at the same time?
Usually it is simpler to move hosting first and transfer the registration later. A domain transfer and a hosting migration are separate processes.
When can I cancel the old hosting?
Only after you have checked the new site, SSL, email, forms, databases, jobs and backups and allowed for cached DNS.
Planning a move?
Let UKC assess the source before you change anything
Send the platform, site size, access available and email requirements so the migration can be scoped safely.