Forward custom domain email to Gmail.
Use your main Gmail inbox to read product mail. Plan the sending identity separately, so a reply does not expose the wrong address.
Verify the destination
Confirm ownership of the Gmail address before enabling a forwarding route. Signing in with Google identifies your account; it does not automatically grant another service access to all Gmail messages or permission to send mail.
Inspect the domain’s current MX
Find out which provider currently receives the domain’s email. Keep existing MX records until you have planned and tested the migration. A support subdomain is an option, but support@mail.example.com is a different address from support@example.com.
Create and test the forwarding route
With a provisioned forwarding provider, create the support address and map it to the verified Gmail destination. Test from another email provider. Check the original sender, product identity, attachments, spam placement and failure behavior.
Plan replies beyond Gmail Send As
Google says Gmail support for third-party Send As addresses ends in January 2027; Google Workspace aliases and other Gmail addresses you own are unaffected. Forwarding does not authorize sending. Prefer a verified web reply path; test a reply proxy separately before relying on it.
Use labels deliberately
A forwarding service’s internal labels do not automatically become native Gmail labels. Gmail filters or a separately authorized integration can help organize the forwarded mail. Do not grant broad Gmail access just to create a login.