Case Study: What Happened When Plus Aliases Hit a New Domain

When Maya moved her small design studio from Gmail to a custom domain, she expected a quiet weekend of DNS tweaks. She had built her whole signup workflow on a Gmail email alias strategy: one plus alias per client, per newsletter, per tool trial. Every message landed in one inbox, and every sender got its own label. The migration took two days, and the plus aliases never arrived. This case study walks through what happened, what she lost, and the checklist she now hands to anyone moving an alias setup between providers.

The short version: the new provider treated the plus sign as a literal character, not a routing rule, so mail to client1@herdomain.com bounced while plain mail flowed fine. She had never inventoried her aliases, so she had no list to rebuild from. Vendors that had stored the old plus strings on file kept sending to addresses that no longer resolved. The fix was not technical wizardry. It was a named alias per sender, a spreadsheet, and about 40 re-signups spread across three evenings.

Here is the thesis up front. Plus aliases are a Gmail feature, not a portable standard, and any migration plan that assumes otherwise will break routing on day one. The checklist below covers the numbers that matter: Gmail plus aliases deliver mail to the same inbox with no cap worth worrying about, Send mail as supports up to 99 addresses, Google Workspace allows 30 aliases per user, and changing your gmail.com address is allowed once every 12 months. A second Google account gives you a separate inbox, which is a different tool entirely. If you are weighing a move, read this before you touch a DNS record, and keep your alias list somewhere that does not live inside the account you are about to migrate.

How Gmail Plus Aliases Work and Why They Were the Backbone of This Setup

Before the migration, the setup was simple and it worked for six years. One Gmail account, one password manager entry, and about 40 plus aliases doing the quiet work of keeping signups, invoices, and newsletters apart. If you have ever typed yourname+newsletter@gmail.com into a form just to see who sells your address, you already understand the appeal.

Here is the checklist of what that account actually relied on, because every item on it matters once you move providers.

  • Gmail plus aliases on the main address
  • Dot aliases that Google ignores anyway
  • One second Gmail address used as a fallback
  • Send mail as configured for two outside addresses
  • Filters sorting mail by alias string

Gmail offers plus aliases on every account, free or paid. Add a plus sign and any word after your username and mail still lands in the same inbox. yourname+shopping@gmail.com and yourname@gmail.com deliver mail to the same inbox, and Gmail treats the plus string as part of the local part, so filters can catch it. That last detail is the whole trick: a filter on “to: yourname+shopping@gmail.com” files every message from that alias into its own label without touching anything else.

Creating one takes about 15 seconds and there is nothing to configure. You do not create email alias in Gmail through a settings screen, because plus aliases are not stored anywhere. You just hand out the address. The alias exists the moment a sender uses it, and it disappears from your mental inventory the moment you forget which string went where. Keep a list. The case study subject did not, and that cost hours later.

Two other pieces carried weight. The first was a second Gmail address, a plain account used for banking and government portals, kept deliberately separate so a compromised inbox would not take everything down. A second Google account provides a separate inbox, which is different from an alias, and the distinction matters. Aliases share one login, one password, and one recovery path. A second account does not.

The second piece was Send mail as. Gmail supports up to 99 addresses in Settings > Accounts and Import > Send mail as, each one needing a verification email to the target address and, for outside domains, an SMTP server and credentials. Two of those 99 slots were in use: a work address and a side-project domain. Replies routed back correctly, and the From line looked professional without a second client. That setup is worth knowing about because Google will discontinue Send as for third-party addresses starting January 2027, so anyone leaning on it now has a deadline on the calendar.

Worth noting for completeness: changing your gmail.com address is allowed once every 12 months, and only to another available username. That is not an alias feature. It is a rename, and old mail does not follow. Google documents alias limits on its help pages, and for Google Workspace the number is 30 aliases per user, which is a different product with a different ceiling. Free Gmail has no published cap on plus aliases, which is exactly why people pile them up.

AllMail publishes Gmail alias guides that cover this ground well, and the takeaway from all of them is the same. Plus aliases are free, instant, filterable, and completely invisible to any export tool. That last property is the one that bit this account holder. Everything described above lived inside Google’s interface, and none of it was a setting you could download and re-import somewhere else.

With that baseline in hand, the move to a custom domain looked like a straight swap. It was not.

The Migration to a Custom Domain: What Actually Transferred and What Did Not

The move started with a spreadsheet, as most sane migrations do. The user exported every address that touched the old Gmail account: 41 plus aliases, 12 vendor logins, 6 newsletter subscriptions, and 3 addresses used for banking alerts. The plan was simple. Point the custom domain’s MX records at the new provider, recreate the aliases, and flip the DNS. What could go wrong?

Plenty, it turned out. Here is what actually crossed the border and what quietly stayed behind.

What Transferred, What Did Not, and Why the Plus Strings Vanished

Mail flow transferred cleanly. Once the MX records propagated, every message sent to anything@customdomain.com landed in the new inbox. Email forwarding rules created at the registrar level worked on the first try. The catch-all email setting on the new provider caught stragglers addressed to names that did not exist yet, which bought the user a week of breathing room.

The plus aliases did not transfer. Not a single one. The reason is structural: a plus sign alias only works because Gmail strips the +tag portion and routes the message to the base mailbox. The new provider treated shop+orders@customdomain.com as a literal, distinct address with no base mailbox behind it. Unless someone manually created that exact string, the message bounced. The user had assumed plus aliases were portable, a misconception explained at allmail.one/blog/gmail-email-alias. They are not. They are a Gmail behavior, not an email standard.

Here is the checklist of what actually moved and what had to be rebuilt:

  • Mail delivery: transferred via MX records. Clean.
  • Contacts and calendars: exported as CSV and ICS files, imported without drama.
  • Labels: did not survive. The new provider uses folders, and nested labels flattened into a mess.
  • Gmail filters: dead on arrival. Every filter built on a plus alias address, and the new provider’s rules engine did not recognize the old strings.
  • Send mail as identities: the user had set up 4 identities in Gmail settings under Accounts and Import. Only 2 could be recreated on the new provider, and both required SMTP server credentials and a verification email round trip.
  • Plus aliases: zero of 41 transferred. All 41 needed manual recreation or replacement.

The Send mail as gap stung more than expected. Gmail supports up to 99 addresses in that panel, and the user had leaned on it for years to reply from vendor-specific aliases. The new provider capped outbound identities at 5 and demanded SMTP credentials for each one. Two of the old identities pointed at a Google Workspace alias that belonged to a former employer, so those were gone for good regardless.

One more thing did not cross: the gmail.com username itself. Changing your gmail.com address is allowed once every 12 months, and the user briefly considered it, then realized it would break every login tied to the old string. The second Gmail address that had been used as a backup inbox stayed exactly where it was, untouched, which turned out to be the smartest decision of the whole project.

Rule of thumb from this migration: count your aliases before you count your blessings. The spreadsheet had 41 rows. The new provider started with 0.

The verification emails were the tell. Three vendors sent confirmations to plus strings that no longer existed, and those messages bounced silently because the catch-all only covered the custom domain, not the old Gmail address. The user found out two weeks later when a payment receipt never arrived.

Why Plus Aliases Evaporated and How Named Aliases Restored Routing

The first support reply was polite and useless: “plus addressing is a Gmail feature, not a standard.” That one sentence explained the whole failure. On gmail.com, the plus sign alias is built into the mail server. Anything after the plus sign is stripped before delivery, so shop+amazon@example.com lands in the shop inbox. On the new host, the plus sign is just a character in a local part. No rewrite rule, no delivery. Every plus alias the user had relied on for years pointed at an address the new server treated as a stranger.

The fix took an afternoon, but the shape of it matters. Here is the checklist the user worked through, and it is worth copying before you touch your own DNS.

Rebuilding the alias map as named aliases

  1. Export the old alias list. Search Gmail for to:(+*) and pull every plus string out of the results. The user found 41 of them, including three nobody remembered creating.
  2. Create named aliases on the new domain. Instead of shop+amazon@, the alias became amazon@newdomain.com. Same routing intent, different address. The provider allowed this without a paid seat for each one, which is why the whole map could be rebuilt in one sitting.
  3. Set up catch-all as a safety net. A catch-all email rule on the new domain means any address that does not match a named alias still reaches the main inbox instead of bouncing. It is not a substitute for a clean map, but it stopped silent failures on day one.
  4. Test delivery from outside. Send from a second Google account to each new alias and confirm the email filters still fire. Gmail filters can be created on plus alias addresses, and the same filter logic works on named aliases once you update the “to” field.
  5. Update Send mail as. The new host needed its SMTP server details added under Gmail settings, Accounts and Import, so replies would leave from the new alias rather than the old gmail.com address. Send mail as supports up to 99 addresses, so there was room.

Routing came back within a day. The inbox looked normal again. Then the invoices started bouncing.

Every vendor that had the old plus string on file still had it. The bank statement, the utility portal, the two SaaS tools the user paid for monthly, the airline loyalty account: all of them stored user+utility@gmail.com as the contact address. Changing the address inside each account meant logging in, and logging in often meant a verification email sent to the address that no longer existed. The user counted 17 accounts stuck in that loop. Nine were fixed by logging in with a saved password. Four needed a phone call. Four needed a support ticket and a wait of two to five days.

The trade-off is worth stating plainly. Named aliases are cleaner to read and easier to filter, but they are not portable either. If the user moves again, amazon@newdomain.com becomes amazon@anotherdomain.com, and the same re-signup dance starts over. What actually protects you is a domain you control, so the local part survives the provider change even when the domain does not change at all. That is a lesson for the next move, not this one.

One more wrinkle: the old Gmail plus aliases did not die. They still deliver to the original Gmail inbox, which the user kept alive as a free archive. Forwarding from that inbox to the new domain closed the gap for stragglers. The plus aliases evaporated as a routing tool, but they survived as a forwarding source, and that bought the user time to finish the re-signups without losing a single password reset.

Lessons for Anyone Migrating Aliases Between Email Providers

Pull your alias inventory before you touch DNS. That single step would have saved our case study subject about three weeks of scattered vendor emails. Export every address that has ever received mail into a spreadsheet with four columns: the full alias string, the vendor or service that uses it, whether login depends on it, and the date it was last active. Gmail makes this easier than most people expect. Open Gmail settings, go to Accounts and Import, and read the “Send mail as” list. Every entry there is an alias you have been sending from, and each one needs a decision during a migration.

Check the alias limits on both sides of the move. Google documents alias limits on its help pages, and the numbers matter when you plan. Google Workspace allows 30 aliases per user. Send mail as supports up to 99 addresses. Gmail itself offers plus aliases with no practical cap, which is exactly why people pile up hundreds of them without noticing. If your new provider caps aliases at 10 or 25, rank your inventory by importance and cut the rest before the migration window opens.

  • Inventory every alias string, including plus sign aliases and dot aliases, since dot variants collapse to the same Gmail inbox but often appear as distinct addresses on vendor records.
  • Flag any alias used as a login credential. Those are the ones that break hardest when the address changes.
  • Note which aliases feed email filters. Gmail filters can be created on plus alias addresses, and those rules do not travel with a domain move.
  • Record catch-all email behavior on the new provider before you promise anyone a working address.

Assume addresses will change, then plan for it. Plus aliases are a Gmail-specific convention. Most custom-domain providers treat the plus sign as a literal character or reject it outright, so shop+orders@yourdomain.com may simply fail to route. Named aliases such as orders@yourdomain.com or shop@yourdomain.com survive provider changes far better because they are standard mailbox names. When you rebuild, prefer named aliases for anything long-lived and keep plus strings for throwaway signups only.

Build a re-signup list and work it in priority order. Start with financial accounts, government portals, and anything tied to two-factor authentication. Then move to work tools, then newsletters. For each vendor, log in first, change the contact address inside account settings, and only then update any forwarding. If a vendor sends a verification email to the old address, keep the old mailbox alive for at least 30 days after the cutover. Email forwarding from the old account to the new one buys you that buffer, and a catch-all on the new domain catches stragglers you forgot.

Watch the calendar on Gmail-specific features. Gmail will discontinue Send as for third-party addresses starting January 2027, which means setups that rely on Send mail as to push mail through an outside SMTP server need a new plan anyway. If you are already migrating, move that sending path now rather than rebuilding it twice. Also remember that changing your gmail.com address is allowed once every 12 months, so a username change is not a substitute for a proper alias strategy. A second Google account provides a separate inbox, not a second address on the same mailbox, so do not confuse the two when you sketch the new layout.

Finally, run a live test before you declare victory. Send a message to every alias on your list from an outside account, confirm delivery, then reply from each alias and check the From header. Keep the old provider active for a full billing cycle, monitor the forwarding log for missed mail, and retire the old addresses only when two consecutive weeks pass with zero unexpected deliveries. That checklist turns a messy alias migration into a boring, predictable one, which is exactly what you want.

Before you touch DNS on a migration, do one unglamorous thing: export a full alias inventory. Open Gmail settings, go to Accounts and Import, and copy every address listed under “Send mail as,” then pull the aliases from the Google Workspace admin console if you have one (30 aliases per user is the documented cap). Add every plus alias you have ever handed to a vendor, because Gmail filters built on plus alias addresses are easy to forget and impossible to rebuild from memory. Save the list as a spreadsheet with three columns: address, where it was used, and whether you can afford to lose it. That file is your migration checklist and your rollback plan.

Then decide, alias by alias, whether you are recreating a named alias on the new domain or accepting the address change and re-signing up at the vendor. Set a hard cutoff date, run both inboxes in parallel for at least two weeks, and forward the old address to the new one so nothing bounces during the overlap. Test with a verification email to each recreated alias before the cutoff, since a typo in a named alias fails silently until a password reset goes missing. Keep the old Gmail account alive for a full year if you can, because password resets and receipts will trickle in long after you think the move is done. One last check: if any of your routing depends on “Send mail as” pointing at a third-party address, plan around the January 2027 change now rather than in December 2026. Fifteen minutes with a spreadsheet today beats a week of chasing vendors who still have an address that no longer exists.

Related posts

NewLucky kassageschiedenis: lees je bonusverloop

Hellspin Bonus Spins Checklist: First-Time Claimants

GoldBet-Limits: Warum hohe Einsätze nicht automatisch sperren