Business email launch guide
Email go-live should be a controlled release, not a DNS guess.
Before switching business email to Google Workspace, confirm accounts, DNS records, tests, third-party senders, mobile access, support ownership, and rollback notes.
A business email go-live is the moment new mail starts flowing through the new system. For Google Workspace, that usually means Gmail is ready, users exist, DNS records are published, authentication is configured, and the business can send and receive from real addresses.
The go-live mistake is treating this as one DNS change. A customer inquiry, invoice, support request, password reset, and website form can all depend on email. The checklist should cover the full workflow, not only MX records.
Go-live control
Quick answer
Business email is ready to go live when:
Go-live readiness checklist
- The domain is verified.
- The active DNS host is confirmed.
- Required users are created.
- Aliases and groups are mapped.
- Gmail MX records are ready.
- SPF, DKIM, and DMARC are planned or published.
- Old provider access is still available.
- External test accounts are ready.
- Website forms and business systems are known.
- Owner, support contact, and rollback owner are named.
If you are moving to Google Workspace, Google's current MX setup uses smtp.google.com, and Google notes that MX changes can take up to 72 hours to be recognized. Use Google's current instructions while implementing: Set up MX records for Google Workspace.
Before cutover
Before changing MX records, confirm the business can actually operate in the new email system.
Users, aliases, and groups exist with the correct owners.
Users can sign in and the owner can access the Admin Console.
Gmail MX, SPF, DKIM, and DMARC are prepared at the active DNS host.
External inbound, outbound, aliases, groups, forms, and invoices are tested.
The runbook and support contacts are ready.
Do not close old email access on go-live day. Keep the old provider available until historical mail, old forwarders, and user acceptance are checked.
DNS and authentication
DNS work should be written down before the change window.
Go-live DNS worksheet
| Record | Purpose | Go-live note |
|---|---|---|
| Verification TXT | Proves domain ownership | Already complete before cutover |
| MX | Routes inbound mail to Gmail | Publish current Google Workspace MX value |
| SPF | Authorizes outbound senders | Include Google and approved third-party senders |
| DKIM | Signs outbound mail | Publish selector and activate in Google Admin |
| DMARC | Monitors or enforces alignment | Start carefully and review reports |
SPF, DKIM, and DMARC are part of launch quality, not a future nice-to-have. If they cannot all be completed before the first mail day, write down what is done, what is pending, and who owns the follow-up.
Test matrix
Testing should represent real business usage.
Business email go-live test matrix
| Test | Example | Pass condition |
|---|---|---|
| External inbound | [email protected] to owner | Message arrives in Gmail |
| External outbound | Owner to non-Google mailbox | Recipient receives message |
| Alias | hello@ | Mail reaches correct owner |
| Group | support@ | Members or shared workflow receive mail |
| Mobile login | Gmail app | User can send and receive |
| Website form | Contact form | Notification reaches correct inbox |
| Invoice sender | Billing tool | Customer receives invoice mail |
| Calendar invite | External invite | Invite appears correctly |
Keep evidence. A timestamped screenshot or note helps if the owner later says a specific address was not tested.
Test sales and contact forms
Website forms are often forgotten. They may send from the web host, an SMTP plugin, or a form provider.
Test invoice and payment mail
Billing tools may need sender authentication or a new SMTP setting after domain changes.
Test support addresses
Groups and shared inboxes need external posting and member checks.
Test mobile access
Many small teams use mobile email first. Confirm sign-in and 2-step verification before handover.
Handover
The go-live handover should be usable by a future admin.
Handover package
- Domain and DNS host.
- Google Workspace admin owner.
- Users, aliases, and groups list.
- DNS records changed.
- Test matrix with results.
- Known pending items.
- Old provider shutdown plan.
- Support contact and escalation process.
- Next review date.
FAQ
What is the most important go-live test?
External inbound mail to the real business addresses is the most important first test, followed by outbound mail and public aliases or groups.
Can go-live happen before DKIM is active?
It can, but it is better to activate DKIM as part of launch quality. If pending, document the owner and timeline.
Should I lower DNS TTL before cutover?
If your DNS provider allows it and you plan ahead, a lower TTL can help. Do not rely on TTL alone; still monitor the propagation window.
How long should monitoring continue?
Monitor through the DNS recognition window and at least the first few business days for critical workflows.
What should be in a rollback note?
Old MX records, old provider access, DNS login, decision owner, and conditions that trigger rollback.
