Email Migration in 2026: A Safe Checklist for Mail, Login, and Delivery

Moving email safely takes more than copying messages. You need a recoverable copy, a way to bring over old mail, a plan for new messages arriving during the switch, and—if you use a custom domain—a carefully timed DNS change. First decide whether you are moving one personal mailbox or an organization: work and school accounts may be restricted by an administrator.

Time-sensitive Gmail change: Google says Gmail web will stop fetching third-party accounts with POP and remove Gmailify in January 2027; new setups may already be restricted. Gmail’s mobile app and third-party mail clients such as Outlook, Apple Mail, or Thunderbird can still access outside accounts using supported sign-in methods. If your current migration plan depends on “Check mail from other accounts” in Gmail on the web, choose another route now. Google’s current transition notice has the details.

Before you move: make a copy and list what must follow

1. List what is in scope. Mail messages, attachments, folders or labels, contacts, calendar events, rules/filters, aliases, signatures, shared mailboxes, and the address book are separate data. A mailbox copy may not carry all of them.
2. Make an independent archive. For personal Gmail, Google Takeout can export mail for your records or use elsewhere. Workspace accounts may have admin controls or export limits. Store the archive somewhere protected and confirm it opens before changing or deleting the old account.
3. Check capacity and access. Compare the source mailbox size with the new provider’s quota. Confirm you can sign in to both accounts, complete multifactor authentication, and access any app-specific or administrator approvals needed.
4. Choose the transfer method. Prefer the destination provider’s supported import tool or an approved mail client that syncs both accounts. POP imports can behave differently from IMAP, may omit folders/labels, and can be affected by source settings. Do not assume that “import complete” means every folder and message is present.
5. Test a small sample. Move a few messages with attachments, sent mail, and older mail. Check sender, date, attachment, folder/label, and search before transferring the full mailbox.

Google’s export documentation says Gmail exports can include message content, headers, attachments, labels, and account settings, but some organization-managed data may not be available. Treat the export as a safety copy; an archive file is not automatically imported into the new provider in the same structure. See Export your data from Gmail and the applicable import guide for your destination.

Choose a transfer route that matches your provider

Moving into Gmail

Google’s current guidance for Gmail on the web still describes importing messages and contacts, while its planned January 2027 change affects ongoing POP fetching of outside accounts and Gmailify. These are not the same feature. For ongoing access to another provider, Google points users toward the Gmail mobile app or a separate mail client. Check the current Gmail instructions for adding or importing another account immediately before the move; available methods and setup screens can change.

Moving into Outlook.com

Microsoft publishes the current connection settings for Outlook.com. Its support page says POP and IMAP access are disabled by default and that Outlook.com requires Modern Auth/OAuth2. This matters because an older migration tool that asks you to type your normal password may fail—or may be inappropriate for your account. Use Microsoft’s current POP, IMAP, and SMTP settings and the destination’s own import workflow rather than copying server settings from an old blog post.

Moving into iCloud Mail or Yahoo Mail

Apple offers an import option for existing messages when setting up a custom email domain with iCloud+, but says not all providers are supported and that the import may take time. It also describes manually moving mail with the Mail app if the import is unavailable. Yahoo publishes IMAP connection settings and may require an app password for a mail client. In either case, first verify the exact account type and current provider instructions: consumer accounts and custom-domain mail hosted by another company can follow different rules. See Apple’s iCloud custom-domain mail import guide and Yahoo’s IMAP settings.

Keep new messages from falling between accounts

For a personal address at a provider such as Gmail or Outlook.com, you usually keep the old account active during the transition and use the provider’s supported forwarding or account-access feature. Send test messages from an unrelated account to the old address and the new one. Confirm which inbox receives them, whether spam filtering changes, and whether replies use the address you intend. Keep a record of services that still send password resets, bills, or security alerts to the old address.

For a custom domain, changing MX records changes where new mail is delivered; it does not copy old messages. Before changing DNS, document the existing MX, SPF, DKIM, and DMARC records, lower the MX record’s TTL in advance if appropriate, and have the new provider’s exact records ready. Publish the new records, verify them with the provider’s tools, and keep the old mail service available during the overlap. Do not delete the old mailbox just because one test message arrived at the new one.

Verify the move before closing the old account

• Compare the number of folders/labels and a sample of old, recent, sent, and attachment-heavy messages.
• Search for a known sender, subject, and date range in the destination. Open the attachments rather than checking only that a message count changed.
• Send test messages from at least two unrelated services to the new address, and reply from the new account. Check spam and junk folders.
• Update account recovery addresses, financial services, subscriptions, login alerts, and mailing lists. Prioritize accounts that use email for password recovery or security notices.
• Keep the old account, archive, and any forwarding route active for a defined overlap period. Confirm the new account receives mail reliably before cancelling paid service or deleting data.
• If the transfer is for work, confirm retention, legal hold, access-control, and administrator requirements before moving company mail to a personal or unapproved provider.

Common migration mistakes

• Assuming folders and labels are identical: providers map them differently; some import methods do not copy them at all.
• Deleting the source too soon: a completed import is not proof that every message, attachment, or rule transferred.
• Changing MX before the destination is ready: new mail can bounce or split across providers while DNS records update.
• Using an old password-based setup tutorial: providers change authentication requirements. Google and Microsoft currently recommend or require modern sign-in in many client scenarios.
• Confusing forwarding with migration: forwarding handles some future messages; it does not archive and transfer the historical mailbox.

Sources

• Google: Changes to third-party email support in Gmail
• Google: Export your data from Gmail
• Google: Add or import another email account
• Microsoft: POP, IMAP, and SMTP settings for Outlook.com
• Apple: Import existing email to iCloud custom domain
• Yahoo: IMAP server settings

Image credits

1. Photo by Jakub Zerdzicki on Pexels
2. Photo by Stephen Andrews on Pexels
3. Photo by İsmail Enes Ayhan on Unsplash