When a small design studio moved its mail from GoDaddy Workspace Email to Professional Email last spring, the owner expected a quiet cutover. Instead, replies to the info@ address kept landing in the old inbox while the new panel showed nothing, and a handful of client messages simply vanished. The culprit was a catch-all email rule set years earlier in Workspace Email that nobody remembered, still sitting active after the migration and quietly shadowing the new configuration. Two GoDaddy panels were fighting over unrouted mail, and only one of them was supposed to win.

How a forgotten Workspace Email rule survived the move

Workspace Email is GoDaddy’s legacy mail platform, the one with the older webmail interface and a separate settings area for domain-level forwarding. Professional Email is the newer product, built on a different back end with its own admin console. Migrations between the two copy mailboxes, contacts, and aliases, but they do not always retire legacy forwarding behavior. A catch-all configured in Workspace Email can stay live at the domain level, which means the old panel keeps accepting mail for any address that does not match a real mailbox.

Here is why that matters. A catch-all is the rule that says «anything sent to this domain that does not match a specific mailbox goes here.» When you set it in Workspace Email, GoDaddy stores it against the domain, not against the mailboxes it copies. Professional Email then sets up its own catch-all toggle in its own panel, and the two rules coexist. The new panel believes it owns unrouted mail. The old panel still has a claim on it. Whichever one GoDaddy’s routing evaluates first wins, and that order is not something you can see from either settings screen.

The studio’s symptoms fit the pattern exactly. Mail to real mailboxes, like the owner’s personal address, arrived fine in Professional Email. Mail to addresses that had never existed, like the old events@ alias the team used for a 2022 conference, went to the Workspace Email catch-all and sat there. Replies to info@ bounced between the two depending on which rule fired. This is the hidden conflict: not a broken migration, but an incomplete one, where a legacy setting keeps acting like it is still in charge.

Why the conflict is invisible until mail goes missing

Neither panel warns you about the other. The Workspace Email settings page does not know Professional Email exists, and the Professional Email console does not audit legacy forwarding rules. The first sign is usually a user complaint about missing mail, days after cutover, when the trail has gone cold. In the studio’s case, the tell was a Workspace Email inbox that kept receiving automated receipts for a domain that had supposedly moved. That inbox should have gone quiet. It did not, because the catch-all was still feeding it.

The general principle applies well beyond GoDaddy: a catch-all must be set where the MX records point. When MX records move to a new mail platform, any catch-all or forwarder left on the old platform becomes a shadow rule. It only catches mail if some path still delivers there, and legacy panels often keep a delivery path open for a while after migration. cPanel behaves the same way. cPanel calls the catch-all the Default Address, and it is used by Namecheap shared hosting and GoDaddy cPanel hosting alike. If you migrate off cPanel hosting but leave the Default Address configured, and any mail still reaches that server, the rule keeps firing.

Domain-level forwarders make it worse. In both cPanel and GoDaddy panels, a domain-level forwarder can override the Default Address for specific addresses, so the routing order is forwarder first, catch-all second, mailbox last. allmail.one/blog/catch-all-email-cpanel-namecheap-godaddy offers additional context worth reviewing. After a migration, that stack can be split across two systems, with forwarders in one panel and the catch-all in another. Debugging it means checking both panels, not just the one you think is live.

A cleanup sequence that actually resolves the split brain

Start with an MX record lookup from a public resolver. Confirm which platform currently receives mail for the domain. In the studio’s case, MX records pointed to Professional Email, which is why real mailboxes worked, but GoDaddy’s routing still consulted the Workspace Email catch-all for addresses with no mailbox match. The lookup tells you which panel is authoritative and which one is a ghost.

Next, log into the legacy panel and disable the catch-all there. In Workspace Email, that means clearing the catch-all address field or setting it to discard. Do not just change where it forwards; turn it off. A catch-all left pointing at a mailbox you still monitor will keep collecting spam and, worse, keep intercepting mail that should reach Professional Email. Then set the catch-all in the new panel, where the MX records point, and test with an address that has never existed on the domain. Send one message, wait two minutes, and check both inboxes. If it lands in the new panel’s catch-all target and nowhere else, the conflict is resolved.

Expect a spam wave when you enable the new catch-all. Spammers may cause large amounts of spam at the default address, because a catch-all accepts dictionary attacks and misaddressed mail that would otherwise bounce. The studio saw roughly 40 junk messages a day within a week of turning it on. The spam trade-off is real: a catch-all catches typos and legacy addresses, but it also catches everything a spammer can guess. If the domain has been public for years, consider routing the catch-all to a dedicated mailbox you check weekly rather than a person’s primary inbox.

The same split-brain risk shows up on other platforms. Google Workspace requires its own catch-all rule, configured in the admin console under routing settings, and it does not inherit a catch-all from a previous provider. Namecheap offers catch-all via free email forwarding, which lives in a different part of the dashboard than Private Email mailboxes, so a domain using both can end up with forwarding rules that surprise the mailbox owner. GoDaddy provides a catch-all toggle in Professional Email, but the toggle only governs that panel. The lesson from the studio’s migration applies everywhere: before you flip a catch-all on in the new panel, find and kill the one in the old one.

If you are planning a GoDaddy migration, write the catch-all setting into your cutover checklist alongside MX changes and mailbox exports. Note the current catch-all target, disable it in the source panel on cutover day, enable it in the destination panel, and test with a fake address. Keep the old panel accessible for at least 30 days so you can audit for mail that still arrives there. A catch-all is a small setting with outsized reach, and during a migration it is the setting most likely to keep working when it should have stopped.