Skip to content
TECH Consult

How to Move Your Website to a New Host Without Losing Email

The steps for moving a business website and email to a new hosting provider, in the right order, with the checks to run before you change DNS.

Published 10 min read

Moving a website to a new host looks simple: copy the files, change the DNS, done. In practice, most of the trouble isn’t with the website at all. It’s with email. Messages land on the old server after the move, mailboxes on the new server sit empty, and the contact form quietly stops sending anything. This guide walks through the order to do a website migration in, what to prepare beforehand and what to check afterwards, so your company loses neither visitors nor messages.

Before anything else: what you have and where it lives

Day one of any migration is an inventory. Skip it and you’ll find out at the end that you forgot something that “just worked”.

Write down:

  • Where the domain is registered and who can log in to the account that manages it. For .ro domains held by a company, the registrant shows up in the ROTLD WHOIS database. ROTLD is the Romanian registry that runs the .ro zone. More on that in our guide to registering a .ro domain.
  • Where the domain’s DNS servers are. They might be at the registrar, at the old host or with a third service.
  • Every current DNS record. Make a copy of the DNS zone: A, CNAME, MX and TXT records (SPF, DKIM, DMARC, domain verifications for various services). Each one is there for a reason, even if nobody remembers what it is.
  • What else runs on the old hosting apart from the site: subdomains, a forgotten second website, FTP accounts used by some outside program, scheduled tasks (cron jobs), redirects.
  • The email accounts, with the size of each mailbox and the passwords (or who knows them).
  • When the old contract expires. Don’t leave the move for the last week.

If you’d like a refresher on the terms before you start, DNS explained in plain English shows what each record type does.

Pick your moment and lower the TTL

Every DNS record has a TTL, short for “time to live”. It’s how long servers around the world keep an answer in memory before asking again. If the TTL is one day, some visitors will keep reaching the old server for a day after you make the change.

A few days before the move, lower the TTL on the records you’re going to change (usually the A record for the website and the MX record for email) to something small, such as 300 seconds. Wait for the old TTL to run out. On the day itself, the change will spread much faster.

Also check who can edit the DNS zone. If the DNS servers belong to the old host and that account is in the name of a web agency, you’ll need the agency’s help for every change. Sort out access beforehand, not on the evening of the move.

Choose a day and time when things are quiet. For most businesses that means an evening or a weekend. Avoid invoicing days and the middle of a marketing campaign.

Copy the website to the new server

A dynamic site such as WordPress has two parts: the files and the database. Both need to be copied at the same moment, or orders and messages that arrive between the two copies get lost.

Steps for a WordPress site:

  1. Take a full backup on the old hosting and download it to your own computer. If something goes wrong, you have a way back.
  2. Copy the files (over FTP, SFTP or as an archive downloaded from the old control panel) into the site’s folder on the new server.
  3. Export the database from the old panel (usually in phpMyAdmin, under Export) and import it into a new database.
  4. Update wp-config.php with the new database name, user and password.
  5. Check the PHP version. To start with, set the same version on the new server as on the old one. Change versions separately, after the move, so you know what caused any error that shows up.

In Plesk, WordPress Toolkit and the migration tools can copy a site straight from another server if you have the login details. For large sites or online shops, that’s worth using.

If the site isn’t WordPress, the principle is the same: the files, the database (if there is one) and any application settings that contain connection details.

Test before you change DNS

This is where a calm migration is won or lost. You need to check the site on the new server before visitors get sent there.

How to see the new site without changing DNS for everyone:

  1. Find the new server’s IP address in the hosting control panel.
  2. On your own computer, open the hosts file. In Windows it’s C:\Windows\System32\drivers\etc\hosts, and you need to open it in Notepad started with Run as administrator.
  3. Add a line with the new IP followed by your domain, for example 203.0.113.10 yourcompany.ro www.yourcompany.ro.
  4. Save the file and open the site. Your computer now sees the new server while everyone else still sees the old one.

What to check: the home page, a few inner pages, the contact form (does the message arrive?), logging in to the WordPress dashboard, the site search, and the shop and checkout if you have them. When you’re done, delete the line from hosts.

Plesk also offers a site preview through a temporary address. It’s handy for a quick look, but the hosts test is more faithful because the site loads under its real address.

Email: the part that breaks most often

You can move a website in a few hours. Email needs more care because messages keep arriving while you work.

The order that avoids losing mail:

  1. Create every mailbox on the new server, with the same names, before you touch DNS.
  2. Change the MX record to point at the new server. From then on, new messages start arriving there, gradually, as the old TTL expires around the world.
  3. Copy the old messages from the old server to the new one. Use an IMAP migration tool or, for a handful of mailboxes, your email program: add both accounts and drag the folders from one to the other.
  4. Keep the old server running for a few days after the switch. Some messages can still land there while other servers remember the old MX. Do one final copy before you close the old account.
  5. Reconfigure the email apps on computers and phones with the new incoming and outgoing servers.

Don’t forget email authentication. SPF has to include the new sending server, and DKIM has to be switched on at the new server and published in DNS. Otherwise mail sent after the move is far more likely to end up in spam. We cover this in detail in why business email goes to spam.

If your email runs on a different service from your hosting (Microsoft 365, for example), leave the MX records alone. Move only the website and keep the rest of the DNS zone exactly as it was.

Changing DNS: two ways to do it

There are two ways to point the domain at the new host:

  • Change only the records (A for the website, MX for email) in the existing DNS zone. This is the most controlled option, because you only touch what’s moving.
  • Change the domain’s DNS servers to the new provider’s. Before you do, recreate the whole zone there, with every record from your inventory. For .ro domains, the change is made in ROTLD’s domain management interface or through your registrar, and ROTLD notes that propagation can take up to 24 hours.

The second option is tidier in the long run, but any record you forget to recreate means a service that stops working. Checking the old zone line by line is worth the time.

Online shops and sites with integrations

A brochure site can be copied at any time because it rarely changes. A shop takes orders, and an order placed on the old server after you copied the database never reaches the new one.

A few precautions for shops:

  1. Turn on maintenance mode on the old server just before the final database copy. Customers see a short notice instead of a basket that empties itself.
  2. Make the final copy of the database and import it on the new server.
  3. Change DNS straight afterwards, with the TTL already lowered.
  4. Watch both servers for a few hours. If an order still turns up on the old one, enter it by hand.

External integrations have their own settings tied to the server:

  • The payment processor sends confirmations to an address on your site. If it also checks the server’s IP address, update it in your merchant account.
  • Invoicing or stock software may connect to the shop using access keys or from a list of allowed IP addresses.
  • Couriers send delivery status updates through the same kind of mechanism.
  • Connections to external databases or APIs that only accept certain IP addresses need the new server’s address.

List these integrations during the inventory, not after a customer calls to say their invoice never came.

After the move: checks for the first week

  • The SSL certificate is only issued on the new server once the domain points to it. Check the padlock on both yourcompany.ro and www.yourcompany.ro. See our guide to SSL certificates and HTTPS for details.
  • Do the forms send? Some sites send mail through the local mail server, which is now a different one.
  • Do scheduled tasks (automatic backups, syncs, newsletters) run on the new server?
  • Is backup active on the new hosting? Do a first test restore.
  • Does email flow both ways, to customers on Gmail and Outlook addresses? Check the message headers, where SPF, DKIM and DMARC should all show PASS.
  • The error logs in the new panel. The first days tend to expose incompatible plugins and file paths written wrongly.

For a few days, also keep an eye on the reports in the search engines’ webmaster tools. A sudden jump in crawl errors after a move points to pages that no longer respond on the new server, usually because a redirect rule wasn’t copied across.

Only after a week with no surprises should you cancel the old hosting, with one last backup downloaded to your own computer.

Frequently asked questions

How long is the website down during a migration?

If you test on the new server before changing DNS and lower the TTL in advance, downtime can be practically zero. Visitors see either the old site or the new one, and both work. The risk sits with online shops, where orders placed during the move window have to be watched on both servers.

Will I lose my search rankings if I change hosts?

Not if your page addresses stay the same and the site doesn’t go offline. Search engines follow the domain and the pages, not the server. Problems start when a move also changes the URL structure without redirects.

Do I have to transfer my domain to the new provider as well?

No. The domain can stay with its current registrar, and you simply point it at the new hosting through DNS. Our page on whether you need web hosting for your domain explains why the domain and the hosting are separate services.

What if my old provider won’t give me access to my files?

Your website’s files and your email belong to your company. Ask in writing for a full archive and an export of the database. If an agency built the site, check what your contract says about handing it over.

Can I move my website myself?

A simple brochure site, yes, with the steps above and some patience. For online shops, sites with many integrations or companies with lots of mailboxes, having someone who has done it dozens of times run the move saves time and stress.

When to hand the move over to us

If you have several domains, email in daily use across the team or an online shop, a migration has enough moving parts that it deserves a written plan and someone to carry it out. For clients of TECH Consult web hosting, we move the website from the old provider ourselves and help you move the mailboxes. We’ll ask you for the access details, and we’ll tell you what we’re changing before we change it.

Tell us what is not working

Describe the problem in a few lines. We reply with what we think needs doing and what it would cost.

Request a quote