How to forward emails to a Google Workspace alias to an external email
You can forward emails sent to an alias to an external email address, but it requires admin-level setup since direct user aliases don't support external forwarding on their own.
Yes, in Google Workspace, you can forward emails sent to an alias to an external email address, but it requires admin-level setup since direct user aliases don’t support external forwarding on their own. This can be achieved by using Email Routing/Maps in the Admin console, converting the alias to a Google Workspace Groups (which allows external members), or by creating a Gmail filter rule on the primary account.
Recipient Mapping
Admins can configure routing rules to map an alias (e.g., olduser@company.com) to an external address. Access Gmail > Routing in the admin console, add the alias under recipient maps, and set it to forward externally.
In the Admin console
- go to Apps > Google Workspace > Gmail > Routing.
- Use the “Email forwarding using recipient address map” setting to map the alias address to the external email address.
Enable “Also route to original destination” if needed, and set it to apply only to non-recognized addresses to avoid conflicts with future users. If context is important, be sure to check Add X-Gm-Original-To header. This prevents loss of context in the chain.
Google Workspace Groups
Create a group with the alias email, set it to allow external posting, and add the external address as a member. Emails to the group alias forward directly to the external recipient without needing a licensed user. This is often more flexible than user-based aliases, as it does not require a license and supports external members.
- Create a Group (e.g., info@company.com) and
- add the external email address as a member.
- Enable external membership and “Allow external users to post.”
Emails to the group forward automatically to members.
How Recipient Mapping and Google Groups Compare
| Method | Pros | Cons | Best For |
|---|---|---|---|
| Recipient Mapping | Admin-only, precise routing | Requires admin access | Former employee catch-alls |
| Google Groups | No cost, easy external adds | Group management overhead | Team or shared aliases |
Gmail Filter Rule
Gmail filter rules can forward emails, but they have limitations for aliases in Google Workspace. User-level filters catch emails after they reach the primary inbox, not standalone aliases.
How Gmail Filters Work
- Create filters via Gmail Settings > Filters > Create new filter.
- Use criteria like “To: alias@domain.com” then select “Forward it to” an external address (must be pre-verified).
- Admins must enable user forwarding first in Admin Console > Gmail > User Settings.
Gmail Filter Rule Limitations for Aliases
| Scenario | Works? | Why |
|---|---|---|
| Active user alias | ✅ | Delivers to primary inbox first, filter catches it |
| Unrecognized alias | ❌ | Bounces unless admin routing/catch-all configured |
| External forwarding | ⚠️ | Requires verification; Workspace admins often restrict |
For true standalone alias forwarding (no primary inbox), use admin recipient mapping or Groups instead—filters alone won’t intercept before delivery fails.
More Information ℹ
Be polite and constructive with your point.