Does transferring a domain move your old emails?

1. Separate the registration from the message store

A registrar manages the domain registration. An email provider operates mail services, while an email app displays messages and may keep local copies. These roles can be supplied by one company or several. Moving one account does not automatically move the contents of the others, even when a bill describes them together as hosting.

The Internet Mail Architecture describes message storage as a separate component that can be on a server or a local machine. For your move, find where the important history actually lives: webmail, a desktop archive, shared mailboxes or more than one place. Seeing messages on a phone is not a complete inventory of what must be preserved.

Sources: Nominet: current UK registrar-change options ↗ · RFC 5598: Internet Mail Architecture and message stores ↗

2. If the email provider is staying, check the dependency

A registrar change does not inherently require a new mailbox service. Ask the existing provider whether mailboxes and DNS stay active when the domain registration leaves. Check whether a bundled plan has any dependency on keeping the registration there. A plan name or an unchanged nameserver list cannot answer that account-specific question.

If the mail service and DNS are staying, avoid making unrelated mail-record changes merely because the registration moves. Keep the current account accessible and the service paid for under its actual terms. After completion, test receiving and sending, then check that you can still open the historic folders. Do not cancel the mail plan just because the registrar move succeeded.

3. If email is moving too, make a mailbox worksheet

List each real mailbox, alias and shared address before choosing a migration method. An alias may deliver into another inbox rather than hold its own message history. Ask both email providers which data their supported migration or export/import process handles, what access it requires and what is excluded. Keep credentials out of ordinary support messages.

This fictional one-person business worksheet shows the questions to settle. It contains no real addresses or message counts. Contacts and calendars need their own checks; do not assume that copying email also copies every related account setting.

On a narrow screen, swipe sideways to compare the full worksheet.

4. Copy and check history before relying on the new account

Use the providers’ supported migration tools or export formats, and keep a secure copy where appropriate. Confirm that an export can actually be opened or imported with the intended software. A file appearing in a download folder is not proof that all required messages and attachments are usable.

Check a sample from the oldest and newest periods, important folders, attachments and shared mailboxes. Review any migration error report and known exclusions. Differences in folder views or counts need investigation rather than an assumption that everything copied. Agree who signs off the result before deleting an original account or removing its last accessible copy.

• Open representative messages and their attachments in the destination.
• Check Sent, custom folders and any locally stored archives.
• Review failed, skipped or unsupported items with the provider.
• Record what was checked and which unresolved items still need attention.

5. New-message routing is a separate cutover

Copying old messages does not decide where tomorrow’s mail arrives. Your new email provider supplies the required routing and sending-authentication records. Arrange the DNS change at the active host only when the destination mailboxes and agreed migration plan are ready. Preserve unrelated website records and keep a copy of the previous settings.

Test incoming mail from an independent account, send from the intended business address and check replies. Include aliases and shared addresses you actually use. DNS caching can mean different senders see a change at different times, so follow the providers’ overlap and final-copy plan rather than treating one successful test as the entire migration. Changing MX records does not copy historic messages.

Sources: RFC 5321: SMTP and mail routing ↗

6. Confirm retention before cancelling the old service

Ask the old provider what cancellation does to mailbox access, stored data, exports and any remaining DNS service. Get the actual end date and retention rules for that account. Do not infer a grace period from another provider’s help page or from the date your domain registration moved.

Keep the old service through the agreed checks and any final synchronisation. Then review remaining dependencies such as contact forms, invoice senders, recovery addresses and devices still using the old sending server. A working new inbox is a useful result, but it does not identify every account that needs updating. Record the authorised cancellation only after those tasks are settled.

7. Keep domain renewal and email costs separate

Register .co.uk for £9.99 for one year, with annual renewal currently £9.99. Or choose a new three-year .co.uk registration for £25.99. Check the selected name and term before payment. Future renewal prices can change.

Budget for the domain renewal, email plan and any migration or overlap service separately. A domain’s initial three-year offer does not pay for three years of mailboxes or transfer stored messages. Keep the registration current while the move is being planned, and ask the receiving provider for the actual transfer terms and resulting expiry.

For a new project that needs standalone .co.uk registration, visible annual renewal pricing and managed DNS controls, we recommend considering NameUK. This is our own recommendation for those needs. The prices below are new-registration and annual-renewal prices, not a transfer or mailbox-migration quote. NameUK self-service incoming transfers are not currently available; contact support before requesting an existing domain’s release.