Moving Email From Your Web Host to Google Workspace Without Losing Mail
Short answer: Move business email in this order: create the new users, copy the old mailboxes across with an IMAP migration, lower the DNS time-to-live on your mail records a day ahead, switch the MX records, then confirm that SPF and DKIM pass for the new service. Keep the old mailboxes running until the switch has settled, because mail sent during DNS propagation can still arrive at either server. Update phones and computers last, and retire the old mailboxes only after two to four weeks with no mail arriving there.
Before the switch: inventory
Log in to your hosting control panel and list every mailbox, alias, forwarder and autoresponder. Note the size of each mailbox, because a 40 GB archive takes much longer to copy than a 2 GB one. Also list the apps that send mail from your domain, such as the website contact form, the accounting package, a printer that scans to email and the booking system. Each of those needs an SPF entry or a DKIM setting on the new service, or its messages will start failing.
Take a full copy of every mailbox to a local drive as well. A migration is reversible on paper, but a copy you can open is the only sure rollback.
Step 1: Create the users in Google Workspace
Create one user for each mailbox that people read, and an alias or group for each shared address such as info@ or accounts@. Set the temporary passwords and ask each person to change theirs at first sign-in. Do not connect any device yet.
Step 2: Run the IMAP migration
The Google Workspace admin console includes a data migration tool for IMAP sources. Enter the hosting mail server's address and the mailbox credentials for each user, then start a migration for one mailbox as a test. Check that folders, read status and sent items arrived. Once the test looks right, run the rest. Large mailboxes can take days, so start them early and leave the old server connected until the migration reports complete.
Step 3: Lower the TTL
The TTL, or time-to-live, on a DNS record tells resolvers how long to cache it. A TTL of 86400 seconds means a day. Lower the MX record TTL to 300 seconds, which is five minutes, at least 24 hours before the switch. This makes the change spread quickly. Once the switch is complete and stable, you can raise the TTL again.
Step 4: Switch the MX records
On the day you have chosen, replace the old MX records with the values supplied by Google Workspace. Remove any old mail servers from the list rather than adding the new ones alongside them, because mixed records can send some mail to the old server for days. Record the time of the change.
Expect some mail to keep arriving at the old server during propagation. Resolvers pick up the change at different times, so for a few hours both servers may accept mail for your domain.
Step 5: Handle mail during propagation
Leave the old mailboxes active for at least two weeks. Set up a forwarder on the old server that sends every incoming message to the matching Google address, so nothing is stranded. Some hosts allow forwarding for the whole domain, which is simpler. Check the old mailbox daily during the first week and move anything you find.
Step 6: Verify SPF and DKIM
Your SPF record must include the new service and no longer rely on the old host's sending servers. Generate a DKIM key in the Workspace admin console, publish the value as a TXT record, and turn signing on. Send a test message to an outside address and open the full headers to confirm that SPF and DKIM show pass. If your domain has a DMARC policy, check that it still passes too.
Step 7: Move the devices
Update phones and computers last. Give staff the new IMAP and SMTP details or, better, set up the Google account directly on each device, which uses the secure settings automatically. Phones that keep old settings will keep fetching from the old server, which means people may stop seeing new mail while the old mailbox still looks fine. Ask each person to send a test message from their phone and confirm it appears in the sent folder on the new account.
Step 8: Retire the old service
After two to four weeks, when the old mailboxes have received no new mail for several days, cancel the mailbox plan. Keep the backup copies for a year, because the first time someone needs an old message is usually months later.
Common problems
Duplicate messages often come from a forwarder that copies mail back to a mailbox that is also being migrated. Remove the forwarder once the migration is complete. Missing sent items usually mean the migration tool skipped a folder, so check the folder list on the old server. A bounce from a supplier that says your domain is not accepting mail means the MX change has not reached their resolver yet, and a few hours of waiting normally fixes it.
FAQ
Will I lose emails during the switch?
Not if you keep the old mailboxes running and forward them. Gaps happen when the old server is shut down before the change has spread.
Can I migrate just one mailbox first?
Yes, and it is a good test. Run the pilot while the MX records still point to the old host, and send the test messages to the pilot user's Google address directly. Once the pilot passes, move the rest of the mailboxes in the same cutover window, so that one domain is never split between two servers for long.
How long does the whole move take?
For a small business with a few mailboxes, the technical work can be done in a day, but the safe period for keeping the old service is usually two to four weeks.
Do I need to tell customers?
Usually not. A switch done carefully is invisible to them. Tell staff in advance so they know which device settings to change.
If you would like help planning the cutover date or checking the DNS records before you change them, tell us about your hosting setup and our studio will prepare a checklist for your domain.