Everyone who has ever tried to bulk-move mail off a GoDaddy domain has heard the same three claims: forwarding is free, forwarding is instant, and forwarding is unlimited. Two of those are wrong in 2026, and the third one is only true until you hit a rate cap you never knew existed. The real story is that forwarding limits live at three different layers, and a bulk job usually dies at a layer you never configured.
Where GoDaddy email forwarding actually breaks in 2026
Start with the product layer, because that is where most people misdiagnose the problem. GoDaddy retired Workspace Email, and the old assumption that every domain purchase came with a free inbox and free forwarding is gone. GoDaddy no longer bundles free email forwarding with domains the way it once did. Email Forwarding now requires existing forwarding credits, which means anyone migrating a domain that never had them will find the forwarder option either missing or paywalled. Email Forwarding is independent of other GoDaddy email products, so buying Professional Email, which is powered by Titan, does not automatically restore a standalone forwarder on a different domain in your account.
That distinction matters because people conflate three separate things: a standalone email forwarder (an alias that relays to a destination mailbox), a mailbox inside Professional Email or Microsoft 365, and a distribution group. They behave differently under load. A standalone forwarder is a relay hop. A mailbox forward is a server-side rule. A distribution group is a fan-out list. Each one has its own ceiling, and the ceiling is rarely the one printed on the plan comparison page.
Users can forward mail without a GoDaddy email product at all, which is why the standalone Email Forwarding tool still exists in the Email & Office Dashboard and why it is still gated behind credits. If you are planning a migration, verify credit availability before you promise anyone a cutover date. GoDaddy updates help pages frequently, and the forwarding credit policy has shifted more than once, so a screenshot from last year is not a plan. If you need to forward GoDaddy email to Gmail, confirm the current requirements first.
The three layers where a bulk job dies
Here is the part that almost nobody documents in one place. A bulk-forwarding workflow passes through three independent throttles, and each one fails with a different symptom. The first is SMTP-level rate limiting on the relay. When you point a forwarder at Gmail and push a few thousand messages through it, the sending relay applies per-connection and per-minute caps. You will see temporary deferrals (4xx responses), not hard bounces. The messages are not lost, they are queued, and if the queue backs up past the retry window the relay gives up and you get a bounce days later that looks unrelated to the original send.
The second layer is per-mailbox rule throttling. If you are forwarding from inside a real mailbox using a server-side rule, the mail server enforces its own limits on how many messages a single rule can process per hour or per day. This is the layer people miss because it is invisible in the webmail settings. A rule that works perfectly for a human reading ten emails a day will silently drop or defer messages when a catch-all address suddenly receives two thousand. The rule did not fail. The throttler did its job.
The third layer is Microsoft 365 outbound message limits. Microsoft 365 restricts automatic external forwarding by default, and even when an admin enables it, the tenant enforces outbound caps (recipient rate limits and a daily message ceiling per mailbox). A workflow that forwards to an Outlook on the web destination inside a Microsoft 365 tenant can hit the tenant’s own outbound ceiling before GoDaddy’s relay ever complains. Now you have two independent caps failing in sequence, and whichever one trips first is the error you will see. The fix is not a bigger plan. It is knowing which layer is choking.
- Relay layer: SMTP rate limits produce 4xx deferrals and delayed bounces, not immediate failures. Watch your queue depth, not your bounce log.
- Mailbox rule layer: per-rule throttling is invisible in webmail settings and silently defers once a catch-all floods.
- Tenant layer: Microsoft 365 outbound caps and its default block on automatic external forwarding apply even after you fix the first two.
- Product layer: standalone Email Forwarding needs forwarding credits, and Professional Email only offers external forwarding on Pro Plus, Premium and Ultra plans.
- Destination layer: Gmail applies its own receiving limits, so a third-party destination can reject mail the relay happily accepted.
Matching the tool to the job so the caps stay out of your way
Once you accept that limits are layered, the planning gets easier. Small jobs, meaning a handful of addresses forwarding to Gmail or Outlook on the web, should use the standalone Email Forwarding tool if you have the credits. It is cheap, it is independent of your other products, and it does not care which mail client you use. The catch is that a standalone forwarder is a relay hop, so it inherits the relay-layer caps. Keep destination counts modest and stagger any bulk import rather than firing everything at once.
Larger jobs, especially anything with a catch-all address or an email alias that fans out to several people, belong inside a real mailbox with server-side rules, not a bare forwarder. That gives you visibility into the rule layer and lets you split traffic across multiple mailboxes so no single rule hits its per-hour ceiling. If you are on Professional Email, remember that external forwarding is only available on the Pro Plus, Premium and Ultra plans, so the plan you pick determines whether the rule can leave the tenant at all. On the Microsoft 365 side, get your admin to enable automatic external forwarding deliberately and check the tenant’s outbound limits before you promise a bulk migration. The Email & Office Dashboard is where you confirm what is provisioned; the tenant admin center is where you confirm what is allowed.
The practical sequence for any bulk-forwarding project is the same regardless of scale. Confirm you have forwarding credits if you are using the standalone tool. Decide whether mail should relay (forwarder) or be processed by a rule (mailbox), because they fail differently. Check the destination’s receiving limits, since Gmail and Microsoft 365 both cap inbound volume. Then throttle your own import so you stay under the relay’s per-minute ceiling instead of discovering it through a backlog. Do not trust a single support article to be current; GoDaddy updates help pages frequently, and the forwarding credit rules have changed enough that last quarter’s answer may already be stale. Test with a few hundred messages before you move a few hundred thousand, and log the response codes so you can tell a 4xx deferral from a 5xx rejection at a glance. That one habit will save you more time than any plan upgrade.

