To move email to a new .eu domain without losing messages, create the new addresses first, keep the old ones working as aliases, copy the old mailbox content with your provider’s migration tool, update SPF, DKIM and DMARC, and test deliverability before you announce the change. Keep the old domain renewed for as long as people still write to it.
What should you do before the switch?
Make a list of every mailbox, alias and shared address on the old domain, and of every service that sends mail as you: invoicing tools, newsletters, contact forms and printers.
Tell your users and key contacts the date in advance. Microsoft also lists communicating the change to users as a standard step of a mailbox migration.
How do you keep the old address working?
Make the old address an alias of the new mailbox, so mail sent to either arrives in the same inbox. In Google Workspace, an alias reaches one user, and each user can have up to 30. Google says alias changes can take up to 24 hours.
If your provider has no aliases, use a forwarder from the old mailbox. Either way, keep it for months rather than days.
When should you lower the TTL?
Lower the TTL of any DNS record you will change a day or two beforehand. Google explains that a change takes effect only after the TTL has expired, so a long TTL slows every correction. Restore a longer value once everything works.
How do you copy the old mailboxes?
Use your provider’s own tool. Google’s data migration service imports from IMAP servers and Exchange Online, needs a licensed user with Gmail turned on, and can run a delta import later for newer messages.
Microsoft’s IMAP migration needs the mailboxes to exist first and moves mail folders only, not contacts, calendar items or tasks. Export those separately.
What else needs updating?
Authentication records come first: publish SPF, DKIM and DMARC for the new domain, as explained in our guide to SPF, DKIM and DMARC. Google advises starting DMARC with p=none.
Then change email signatures, website contact details, invoices, social profiles, marketplace accounts and every login that uses the old address. If the website moves too, follow how to move a website to a .eu domain.
How do you test before announcing it?
Send messages from the new address to several providers, and reply from them. Check the message headers for SPF and DKIM passes, and watch the DMARC reports.
Test the old alias too, and confirm that replies go out from the new address.
Key facts
- Create the new mailboxes and aliases before any announcement.
- An alias receives mail for one user; Google allows up to 30 per user.
- IMAP migration with Microsoft moves mail folders only, not contacts or calendars.
- A shorter TTL only helps if you set it before you change the record.
- Start DMARC with
p=noneand tighten it later. - Renew the old domain: if it expires, its aliases and redirects stop working.
Frequently asked questions
How long should I keep the old domain? Until mail to the old address has stopped. Google says site redirects should generally stay for at least a year, and email deserves the same patience.
Will old emails move automatically? No. New mail goes to the new mailbox, while existing mail stays where it is unless you migrate it.
Can I use the same mailbox on both domains? Yes, if your provider supports aliases or secondary domains.
What happens if the old domain expires? Mail to the old address stops arriving. Read what happens when a .eu expires.
See hosting and email with your .eu domain for mailbox options, and email on your .eu domain for the basics.