Export These Forwarding Artifacts Before Workspace Retires

The most expensive thing to lose in a Workspace Email retirement is not your mail. It is the routing logic around it: the forwarder destinations, catch-all rules, distribution groups, and alias mappings that quietly decide where messages go before anyone opens a mailbox. Those are configuration objects, not messages, so a standard mailbox export will not capture them. If you migrate mailboxes and leave the routing behind, you discover the gaps weeks later when a customer replies to an alias that no longer resolves or a team address silently stops delivering.

Why a mailbox export will not save your forwarding setup

GoDaddy retired Workspace Email, and a lot of migration guides still frame the job as «export your messages, import them somewhere else, update DNS.» That framing is incomplete. Forwarders, catch-alls, and distribution groups live in the control plane, not the mail store. A PST or MBOX export captures what arrived in a mailbox. It does not capture the rule that said «send a copy of everything addressed to info@ to three inboxes and one external address.»

The same gap applies to aliases. An email alias is a pointer, not a mailbox, so export tools that enumerate mailboxes will skip it entirely. If your domain used ten aliases pointing at two real inboxes, the export gives you two mailboxes and zero record of the other eight addresses. Rebuilding them from memory after the fact is where migrations turn expensive.

There is a second myth worth killing: that GoDaddy email forwarding is a leftover freebie you can lean on indefinitely. GoDaddy no longer bundles free email forwarding with domains, and Email Forwarding now requires existing forwarding credits. If you held a grandfathered setup, treat it as configuration you must document and re-establish deliberately, not as a default you can assume survives the transition.

The four forwarding artifacts to export before the cutoff

Build your checklist around four categories. Each one is configuration, each one is invisible to a mailbox export, and each one has a different failure mode if you lose it.

Forwarder destinations and catch-all settings

Start with every forwarder and its exact destination address. Record the source address, the destination, whether a copy is kept in the original mailbox, and whether the destination is internal or external. External destinations are the ones that break silently, because deliverability rules on the receiving side may reject forwarded mail even when your configuration is correct. Microsoft 365, for example, restricts automatic external forwarding by default, so a forwarder that worked from Workspace Email may be blocked the moment the destination becomes a Microsoft 365 mailbox.

Then document catch-all behavior. A catch-all address accepts mail sent to any misspelled or unlisted address on the domain. Some Workspace Email accounts had it enabled, some did not, and almost nobody remembers which. If catch-all was on, you need to know before you rebuild, because turning it off during a migration converts every typo’d inbound address into a bounce. Turning it on by accident at the new provider turns your domain into a spam magnet. Capture the current state, the destination, and any exclusions before you touch DNS.

Note also whether forwarding was independent of other GoDaddy email products on the account. Email Forwarding is independent of Professional Email and Microsoft 365 in the GoDaddy catalog, which means a domain could have had forwarding credits active while its mailboxes lived elsewhere. Users can forward mail without a GoDaddy email product at all. That independence, a familiar part of GoDaddy email forwarding in 2026, is convenient day to day and confusing during a migration, because the forwarding records may sit in a different place than the mailboxes you are exporting.

Distribution groups and alias mappings

Distribution groups are the artifact people forget most often. A group such as sales@ or support@ looks like a mailbox in daily use but is really a list of members. Export the group address, every member address, and whether external senders were allowed to post to it. If the group had nested members or a moderation step, capture that too. Rebuilding a five-person group is trivial. Rebuilding a group with twelve members, two external recipients, and a posting restriction is an afternoon you did not budget for.

Alias mappings need the same treatment. For each alias, write down the alias address and the target mailbox or forwarder it resolved to. Aliases frequently chain: an alias points to a forwarder, which points to an external destination. If you record only the first hop, you rebuild half the path. Where you have the option, consolidate chains during the migration rather than reproducing them, since every extra hop is another place for mail to stall.

One practical shortcut: the GoDaddy Email & Office Dashboard is the authoritative source for what is actually configured, not your memory or an old onboarding document. Pull the current state from the dashboard and screenshot or export each screen before the retirement window closes. GoDaddy updates its help pages frequently, so a tutorial you bookmarked last year may describe a flow that no longer exists. The dashboard reflects reality; the help page reflects the version of reality that was current when it was written.

Matching each artifact to the right destination

Once the four categories are documented, decide where each one lands. The trade-offs differ by artifact type, and picking one destination for everything usually produces a worse outcome than splitting the work.

Artifact Best-fit destination Trade-off to weigh
Simple forwarder to one address Email Forwarding with existing credits, or a rule in the new mailbox Forwarding credits are finite and tied to the domain; inbox rules scale but only apply after mail reaches a mailbox
Forwarder to an external address Professional Email on Pro Plus, Premium, or Ultra, or Microsoft 365 with forwarding explicitly enabled Professional Email offers external forwarding on Pro Plus, Premium, and Ultra plans only; Microsoft 365 blocks automatic external forwarding by default and needs an admin change
Catch-all address New provider’s catch-all setting, or a dedicated mailbox Catch-all catches typos and spam equally; a dedicated mailbox costs a license but gives you a review queue
Distribution group Native group or list feature at the new provider Groups with external members need explicit permission settings; some providers restrict external posting by default
Alias mapping Domain-level alias at the new provider Aliases are free but easy to lose in bulk; chained aliases should be flattened during the move

The table hides one important asymmetry. Professional Email is powered by Titan, and its forwarding behavior is governed by the plan tier, not by a single global setting. Microsoft 365 behaves the other way around: the platform supports forwarding broadly but restricts automatic external forwarding by default at the tenant level. If your Workspace Email forwarders pointed outside the domain, those two destinations require different amounts of administrative work to reproduce the same behavior.

Gmail deserves a separate note because it is the most common external destination. Forwarding into Gmail works reliably, but confirm the destination address is verified and that the receiving account is not filtering the forwarded mail into spam. A forwarder that delivers to Gmail but lands in spam is functionally broken, and you will not notice until someone complains about a missed message. Test each external destination with a real send before you decommission anything.

For teams that only ever used Workspace Email as a forwarding layer, a specialist forwarder service is worth considering. Tools like AllMail exist for exactly this pattern: domain-level forwarding without full mailboxes. That route suits domains with many aliases and few real inboxes, which is a common shape for small businesses that parked a domain and routed everything to one Gmail account.

A practical export sequence that finishes before the cutoff

Work in this order: inventory, capture, test, then cut over. Inventory means listing every forwarder, catch-all setting, distribution group, and alias from the Email & Office Dashboard. Capture means writing each one down with its full chain, including external destinations and any posting restrictions. Test means sending a real message through each path to its intended destination before the old configuration is removed. Cut over means rebuilding the configuration at the new provider and only then changing DNS records.

Two details save grief. First, keep the old configuration documented after the migration, because you will need it to answer «why did this address used to work» questions for months. Second, re-check the GoDaddy help pages on the day you execute, not the day you plan, since the documentation moves faster than most migration schedules. The mail itself is the easy part to export. The routing is what deserves the checklist.