How to Migrate Your Email to a Custom Domain: The Step-by-Step Playbook

You have decided to move from you@gmail.com to you@yourdomain.com. Smart move. But the migration feels daunting — you have years of emails, dozens of services using your old address, and zero tolerance for downtime.

This playbook breaks the migration into clear phases with specific actions. Follow it in order and you will have a working custom domain email within a weekend, with zero lost emails.

Before you start: choose your approach

There are three ways to handle email on a custom domain. Choose based on your needs:

Approach	How it works	Best for	Cost
Full hosting	Google Workspace or Microsoft 365 hosts your mailbox	Businesses that need calendaring, shared drives, full suite	$6-7/user/mo
Forwarding	Custom domain aliases forward to your existing Gmail/Outlook	Individuals and small teams that want branding without new mailboxes	$5-15/mo total
Self-hosted	Run your own mail server (Postfix, Mail-in-a-Box, etc.)	Technical users who want full control	$5-20/mo (VPS)

This guide covers all three, but focuses on the first two since they apply to 95% of migrations.

Phase 1: Domain and DNS (Saturday morning, 1 hour)

Step 1: Get a domain

If you do not already own a domain, buy one. Recommended registrars:

• Cloudflare Registrar — At-cost pricing, excellent DNS management
• Namecheap — Affordable, user-friendly
• Porkbun — Cheap renewals, clean interface

A .com domain costs $10-15/year. Avoid exotic TLDs (.xyz, .club) for business email — some spam filters penalize them.

Step 2: Set up DNS records

Regardless of your email approach, you need these records:

MX record

Points to your email provider:

• Google Workspace: ASPMX.L.GOOGLE.COM (priority 1) + 4 backup records
• Microsoft 365: yourdomain-com.mail.protection.outlook.com
• Cleanbox forwarding: mx1.cleanbox.to (priority 10)

SPF record

# Google Workspace:
v=spf1 include:_spf.google.com ~all

# Microsoft 365:
v=spf1 include:spf.protection.outlook.com ~all

# Cleanbox forwarding:
v=spf1 include:_spf.cleanbox.to ~all

DKIM and DMARC

Follow your provider setup instructions for DKIM (see the DNS for Email guide). Start DMARC in monitoring mode:

v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

Step 3: Wait for DNS propagation

MX records typically propagate in 5-30 minutes. Full global propagation can take up to 48 hours, but most email will route correctly within an hour. Use dig MX yourdomain.com +short to check.

Phase 2: Mailbox setup (Saturday morning, 30 minutes)

If using full hosting (Workspace/365)

1. Create your account on Google Workspace or Microsoft 365
2. Add your domain and verify ownership (usually a TXT record)
3. Create your mailbox(es)
4. Set up the email client on your devices

If using forwarding (Cleanbox)

1. Add your domain in Cleanbox and verify DNS
2. Create aliases on your domain (you@yourdomain.com, info@yourdomain.com, etc.)
3. Point each alias to your existing mailbox (Gmail, Outlook, iCloud)
4. Emails to your custom domain addresses now arrive in your existing inbox

Phase 3: Test before going public (Saturday afternoon)

Before telling anyone about your new address:

1. Send test emails from a different account to your new domain address
2. Check delivery — do they arrive in your inbox?
3. Check spam folder — if emails land in spam, your authentication records may be misconfigured
4. Test from multiple providers — Send from Gmail, Outlook, and a work address to cover different receiving behaviors
5. Check authentication — Open a received test email, view headers, and look for spf=pass, dkim=pass, dmarc=pass

Do not proceed until all tests pass. Fixing authentication issues after announcing your new address is much harder than fixing them now.

Phase 4: Migrate services (Saturday evening + Sunday)

This is the longest phase. You need to update your email address on every service that uses your old address.

Priority 1: Critical accounts

• Banking and financial services
• Government and tax services
• Cloud storage (Google, Dropbox, iCloud)
• Password manager
• Domain registrar

Priority 2: Daily-use services

• Social media
• Work tools (Slack, Jira, etc.)
• Shopping sites you use regularly
• Streaming services

Priority 3: Everything else

• Newsletters and subscriptions
• Forums and communities
• Old accounts you rarely use

Pro tip: Do not update everything at once. Use this migration as an opportunity to create unique aliases per service via Cleanbox. Instead of changing Amazon from you@gmail.com to you@yourdomain.com, change it to amazon@yourdomain.com. You are migrating anyway — might as well add alias protection.

Phase 5: Keep the old address alive (ongoing)

Do not abandon your old @gmail.com address immediately. You will miss services you forgot to update.

1. Set up forwarding from your old address to your new one (Gmail: Settings → Forwarding)
2. Keep it active for 6-12 months
3. Monitor what still arrives there — each email that arrives at the old address is a service you forgot to migrate
4. After 12 months, most things will have migrated. You can then disable forwarding and let the old address go dormant.

Phase 6: Lock it down (next week)

Once email is flowing correctly on your new domain:

1. Tighten DMARC — Move from p=none to p=quarantine, then p=reject
2. Enable 2FA on your email account and domain registrar
3. Set up domain lock at your registrar to prevent unauthorized transfers
4. Enable WHOIS privacy to keep your personal details hidden
5. Document your setup — Write down DNS records, provider credentials, and recovery procedures

The migration timeline

When	What	Time
Saturday AM	Domain + DNS + mailbox setup	1.5 hours
Saturday PM	Testing + critical account migration	2 hours
Sunday	Remaining account migration	2-3 hours
Next week	Security hardening	30 minutes
Ongoing	Monitoring old address forwarding	5 min/week

Total active time: about 6-7 hours over a weekend. After that, you own your email identity permanently.