Moving your website and email without losing track of either

You can move a website while keeping its domain registration and email where they are. Before ordering new hosting, decide which services you want to change. That makes the quote clearer and gives everyone a smaller job to check.

Tell the new provider what is moving

Service	What to identify before the move
Domain registration	Current provider, renewal date and who manages the account
DNS	Current nameservers and a copy of the records
Website	Software, files, database and storage used
Email	Mailbox provider, active addresses, aliases and messages to keep

Send the host your application name and version, storage use, and a realistic account of busy periods. Mention scheduled jobs, uploads and outgoing email. Ask who handles migration, server updates and backups, with any charges included in the quote.

Use the VPS specifications to check standard resources, or send a Specialized Hosting enquiry for work that needs a custom scope. If 1984 Hosting is on your shortlist, the 1984 and xUID comparison separates the services before you choose.

Copy the website before changing its address

Keep a usable backup outside the server you’re leaving. For WordPress, that includes the site files and database. Its official migration guide distinguishes moving to another server with the same URLs from changing the domain too.

Use the backup and restore checklist to check what the copy includes. Assign an owner to the database export, uploaded files, DNS change and final checks. When testing a restored copy, isolate outgoing mail and other live integrations before starting the application.

Agree how you’ll test the copy before sending visitors to it. Check an article, an upload, login and a form submission. For sites receiving orders or new member posts, agree when changes on the old server stop and how the final data is copied. Otherwise, the tested copy may already be out of date.

Keep email and DNS in the plan

Changing nameservers moves responsibility for the whole DNS configuration. Copy mail and verification records as well as the website records. Cloudflare advises reviewing imported records because its scan may miss entries; its nameserver setup instructions also cover the DNSSEC steps when moving to its service.

If DNS stays with the current provider, ask which website records need changing and leave working mail records alone. If email moves too, prepare the new addresses before routing incoming mail there. The .RU and .SU Proton Mail guide covers that sequence for Proton.

For Cloudflare, the .RU/.SU DNS guide connects that provider’s setup steps with xUID’s nameserver controls. If you are still choosing mail service, compare email hosting and forwarding before moving addresses.

Check the live result before closing the old account

• Open the site using the normal domain and check HTTPS.
• Test login, forms and any purchase or membership flow.
• Send and receive mail through the addresses you actually use.
• Confirm the latest content and uploaded files reached the new server.
• Check that a current backup exists and someone knows how to restore it.

Record the new renewal dates and keep a copy of the old configuration. Close the previous service only after the agreed checks pass and you’ve saved any data still needed from that account.