Prompt
building a startup and need to move off our old mail server
Latest observation
Absolutely — moving off an old mail server is a common startup inflection point, and it’s worth doing carefully so you don’t lose mail, break logins, or get flagged by inbox providers.
Here’s a practical migration plan you can follow:
1) Decide what “off” means
Figure out whether you want to:
- Replace email hosting only
- Also move calendar/contacts
- Migrate shared mailboxes, aliases, and distribution lists
- Keep the old server in read-only mode for a while
Most startups end up moving to:
- Google Workspace
- Microsoft 365
- Sometimes Fastmail, Zoho Mail, or Proton depending on needs
2) Inventory everything on the old server
Before touching DNS, list:
- All user mailboxes
- Aliases / forwarding rules
- Shared inboxes
- Catch-all addresses
- Mailing lists
- SMTP relay settings for apps/services
- Any app passwords or devices that send mail
- Current DNS records:
- MX
- SPF
- DKIM
- DMARC
- Autodiscover / Autoconfig if applicable
3) Pick the new provider and set it up first
Create the new mail environment before switching traffic:
- Add your domain
- Verify domain ownership
- Create users and aliases
- Configure security policies
- Generate DKIM keys
- Set up SPF and DMARC plan
4) Migrate mail data
Depending on the old system:
- IMAP migration is common and usually easiest
- If using Exchange, use Exchange migration tools
- For hosted systems, sometimes provider import tools work well
Typical approach:
- Migrate historical mail first
- Run a delta sync near cutover
- Then switch MX records
5) Update DNS carefully
You’ll usually need to change:
- MX to the new provider
- SPF to authorize the new sender
- DKIM to sign mail from the new provider
- DMARC to monitor and enforce
- Potentially autodiscover records for client configuration
Important:
- Lower TTL on DNS records 24–48 hours before cutover if possible
- Keep the old MX live temporarily if you want to catch stragglers
6) Cutover plan
A clean cutover usually looks like:
- Freeze mailbox changes briefly
- Sync remaining mail
- Switch MX records
- Verify inbound/outbound mail
- Monitor queues, bounces, and delivery issues
- Re-enable normal operations
7) Test everything
Send and receive tests from:
- Gmail
- Outlook
- External domains
- Mobile clients
- Your app’s transactional email service
Check:
- Authentication headers
- Spam placement
- Reply-to behavior
- Threading
- Shared mailbox access
8) Keep the old server around temporarily
Don’t shut it down immediately. Keep it for:
- Mail delivery stragglers
- Retrieving missed messages
- Audits / compliance
- Troubleshooting
Usually 2–4 weeks is enough, but it depends on your risk tolerance.
9) Secure the new setup
After migration:
- Enable MFA for all accounts
- Disable legacy auth if possible
- Review admin roles
- Rotate any SMTP/API credentials
- Set up alerts for unusual login or sending activity
If you want, I can help you with one of these next:
- A step-by-step migration checklist
- A DNS record template for Google Workspace / Microsoft 365
- A mail migration plan for your exact old server type
If you tell me what mail server you’re moving from and to, I can make this very specific.