Moving aliases between email providers looks simple until an address that quietly received mail for years suddenly can’t send a single message. The fix is to treat migration as an audit, not a copy-paste job. Before you point a single MX record at the new provider, inventory every alias, flag which ones can send outbound, confirm SPF and DKIM on the new domain, and test each alias with one inbound and one outbound message. Aliases that only ever received mail are the ones that fail silently after the move, and you will not notice until a customer replies to an address that no longer works.
Inventory every alias before you touch DNS
Start with a complete list, not a mental one. Log into the old provider and export or screenshot every alias, forwarding rule, and send-as identity tied to each mailbox. On Gmail, the relevant screens live under Settings > Accounts and Import, where you will find “Send mail as” addresses and the aliases attached to your account. Do this for every user, because the person who set up an alias two years ago may have left the company. A spreadsheet with columns for alias address, owner, purpose, inbound-only or two-way, and downstream dependencies will save you hours later.
Count carefully, because the numbers differ by account type. A free Gmail account lets you create Gmail plus aliases by appending a tag like +newsletters to your base address, and those plus aliases deliver mail to the same inbox as the primary. Plus aliases are handy for filtering and signups, but they are not separate addresses you can log into. A paid Google Workspace account allows 30 aliases per user, and Google documents alias limits on its help pages, so check the current cap before you promise a department twenty new addresses. If someone needs a genuinely separate inbox, a second Google account provides that, but it also means a second login and a second place to check.
Watch for the classic trap of the shared mailbox. Teams often create an alias like info@ or billing@ and forward it to one person, then forget who owns it. During migration, that forwarding chain has to be rebuilt or the alias goes dead. Note every email forwarding rule and every catch-all email setting on the old domain, since catch-all addresses will not migrate automatically. If you rely on a catch-all, decide now whether the new provider supports it and how you will route the mail.
The outbound-capable aliases are the ones that bite
This is the step most checklists skip. Sort your inventory into two buckets: aliases that only receive mail, and aliases that can send. An alias that only received mail will keep working inbound after you repoint DNS, which lulls you into thinking the migration succeeded. The moment someone tries to reply from that address, the send fails, because the new provider has no send-as identity configured for it. Mark every address that appears in a signature, a website contact page, or an invoice as outbound-capable until proven otherwise.
For Gmail, outbound sending from another address is handled through Send mail as, which supports up to 99 addresses per account. Each one requires verification, and Google sends a verification email with a confirmation code or link to the address you are adding. If the alias can still receive mail at the old provider, you can complete verification there before the cutover. If it cannot, you need another way to prove ownership, which usually means access to the DNS records for the domain; a guide such as allmail.one/blog/gmail-email-alias may help you plan this before the move, not the morning of.
One timing detail matters for anyone leaving Gmail or consolidating accounts: Gmail will discontinue Send as for third-party addresses starting January 2027. If your migration plan depends on sending from a non-Google address through Gmail’s interface, that path is closing. Move those send-as identities to the destination provider now rather than rebuilding the same fragile setup. For a second Gmail address used purely as a login, the rules are different: changing your gmail.com address is allowed once every 12 months, so a username change is not a migration strategy you can repeat.
Confirm DNS, SPF, and DKIM on the new domain
Aliases are only as good as the domain records behind them. Before you migrate, pull up the DNS zone for the domain and write down the current MX, SPF, DKIM, and DMARC records. The new provider will give you its own MX targets and its own SPF include. If you stack two SPF records or forget to remove the old provider’s include, mail will fail authentication and land in spam. There should be exactly one SPF record per domain, and it should list only the senders you actually use.
DKIM is where migrations quietly break. Each provider publishes its own DKIM keys, usually as a selector record like selector1._domainkey. When you move, you add the new provider’s DKIM record and, once mail is flowing, remove the old one. Sign with the new key before you switch MX, or your first outbound messages will go out unsigned. Test by sending a message to a Gmail address and checking the original message headers for pass results on both SPF and DKIM. A message that authenticates at the old provider tells you nothing about the new one.
If you are moving between consumer providers, the stakes are lower but the mechanics are the same. Yahoo and Outlook both publish their own sending requirements, and neither will sign mail for a domain it does not host. For a custom domain, you control the records, so verify them yourself rather than trusting a migration wizard’s green checkmark. For a plain gmail.com or outlook.com address, there is no domain to configure, which is exactly why those addresses are easy to migrate and hard to replace.
Test every alias inbound and outbound before the cutover
Build a test matrix from your inventory and run it twice: once against the old provider to establish a baseline, and once against the new provider before you commit. For each alias, send one message in from an external address like janedoe@gmail.com and confirm it arrives in the right inbox or folder. Then send one message out from that alias to an external address and confirm the recipient sees the correct from address and that the message passes authentication. Record the result for each line. A spreadsheet with a pass or fail column turns guesswork into evidence.
Pay special attention to plus aliases and dot aliases, which behave differently across providers. Gmail treats john.smith@gmail.com and johnsmith@gmail.com as the same mailbox, but many providers do not, so a dot alias that worked at Gmail may become a distinct address or fail entirely elsewhere. Plus aliases like janedoe+orders@gmail.com are a Gmail convention, and not every provider recognizes the plus sign. If your workflows depend on those patterns, test them explicitly. Gmail filters can be created on plus alias addresses, so any filter that routes +orders to a folder has to be rebuilt on the new side, or the mail will pile up in one undifferentiated inbox.
Recreate filters, labels, and forwarding rules as part of the test, not after it. A filter is invisible until it stops running, and the first sign of trouble is usually a missed invoice or a complaint that nobody saw. Run a full day of real mail through the new setup on a small group of users before you move everyone. That gives you a window to catch the alias that works inbound but cannot send, which is the exact failure this checklist exists to prevent. AllMail publishes Gmail alias guides that walk through these settings screen by screen if you need a reference while testing.
Keep the old provider active for at least two weeks after the cutover so you can compare results and catch stragglers. Retire the old MX records only after every alias in your inventory has passed both tests, filters are running, and SPF and DKIM show pass on real outbound mail. Document the final alias list, who owns each address, and which ones can send, then store it somewhere the next person can find. A migration that ends with a clean, tested inventory is one you will never have to redo from scratch.