How to Move from Free Gmail to Your Domain Email

Using yourbusiness@gmail.com for business tells your customers something about you. It says you're small enough that you haven't figured this out yet. It also makes you a softer target—free email services lack the authentication controls that make impersonation harder.

Switching to domain email (you@yourcompany.com) takes a weekend and costs less than your monthly phone bill. Here's how.

Why Bother

Security With free email, anyone can register yourcompany.com and start sending emails "from" you@gmail.com. You can't set up SPF, DKIM, or DMARC. You have no control over who fakes your identity.

With domain email in Microsoft 365 or Google Workspace, you control authentication. Fake emails from your domain get blocked by receiving mail servers.

Professionalism Invoice from sales@yourgmail.com or sales@yourcompany.com? The second one closes more deals.

Control Your email identity is tied to your domain, not to a third party's terms of service. Google can shut down your Gmail account tomorrow if they decide you're violating their terms (and small businesses sometimes get caught in automated sweeps).

Compliance Some industries and clients require business email with proper authentication. Healthcare, legal, financial services—your free email service won't cut it.

What It Costs

Domain registration: $10-$20/year. Buy from Cloudflare, Namecheap, or Google Domains. Don't use GoDaddy unless you want upsells and renewal traps.

Email hosting:

• Google Workspace: $6-$12/user/month
• Microsoft 365 Business Basic: $5-$6/user/month
• Microsoft 365 Business Standard: $12-$22/user/month (includes desktop Office apps)
• Zoho Workplace: Free for up to 5 users, then $3-$5/user/month

Migration:

• Built-in migration tools: Free
• Third-party migration service: $0-$500 depending on mailbox size
• Consulting for setup: $500-$2,000 if you want hand-holding

Total first year: $60-$300 for a 5-person team. After that, $60-$300/year.

What Can Go Wrong

"We forgot to update our DNS" You set up the new email but didn't update MX records. Every email bounces for a week. Customers think you're ignoring them.

"Our forwarding didn't work" Old emails stay in the old Gmail. After migration, no one can find the email from last March. Three months later, someone realizes there's a pending issue buried in Gmail that nobody's been watching.

"Employees can't log in" Passwords didn't migrate. MFA setup confused someone. They're locked out of their new email on Monday morning.

"Customers reply to the wrong address" You changed from yourbusiness@gmail.com to you@yourcompany.com. Customers keep replying to the Gmail address because that's what's in their contact list. Those replies go to the old, unmonitored inbox.

"SPF/DKIM wasn't set up" New email goes to spam because it fails authentication. You've got a new professional address that nobody receives.

Minimum Viable Implementation

Week Before Migration

1. Register your domain. If you don't have one, buy yourcompany.com from Cloudflare or Namecheap. $10-$20/year.

2. Choose your email host. For most SMBs, Microsoft 365 Business Basic or Google Workspace works fine. Compare pricing for your team size.

3. Set up your email host. Create your account, add your domain, create user accounts.

4. Export everything from old email. In Gmail: Settings > See all settings > Forwarding and POP/IMAP > Add a forwarding address. Then manually export what you need, or use a migration tool.

Day of Migration

5. Update MX records. This tells the internet where to send email for your domain. Your email host gives you specific records to add. Remove old MX records.

6. Set up SPF and DKIM. Most hosts do this automatically. Check that it's working.

7. Set up DMARC. Add v=DMARC1; p=none; rua=mailto:dmarc@yourcompany.com at _dmarc.yourcompany.com.

8. Update DNS propagation. DNS changes take up to 48 hours to fully propagate (usually faster). Plan for a day or two of transition.

Week After Migration

9. Test everything. Send emails to and from various providers. Check spam folders. Verify signatures work.

10. Set up email forwarding from old accounts. Forward old Gmail to new email for 30 days. Check the old inbox daily for misdirected replies.

11. Update email signatures. New address, new domain, no more Gmail references.

12. Notify key contacts. Vendors, customers, partners—let them know you've moved.

13. Set up your team. Walk through basic email hygiene. How to use the new interface. How to set up MFA.

Migration Options

Built-in migration (Microsoft 365) Use the Microsoft Migration wizard in the Exchange Admin Center. Supports Gmail IMAP migration. Free with your subscription.

Built-in migration (Google Workspace) Migration mode in Admin console. Import mail from other IMAP providers. Free with your subscription.

Third-party tools

• Spinbackup: $5-$10/user/month, includes backup and migration
• Vyond: Migration-specific services
• IT consultant: $500-$1,500 for hands-on migration

Manual export/import Export Gmail to .mbox, convert to PST, import to Exchange. Technical but free.

Vendor Questions (Copy/Paste)

1. "What's your process for migrating from Gmail? Do you handle the DNS changes, or do we?"

2. "What's your average migration time for a [X]-user company?"

3. "What happens to our old email during migration—do we need to keep the old account active?"

4. "Do you help configure SPF/DKIM/DMARC, or is that on us?"

5. "What training do you provide for users switching from Gmail?"

6. "What's your uptime SLA for email delivery?"

When to Hire Help

DIY-friendly if:

• Under 10 users
• Simple email usage (no complex rules or shared mailboxes)
• Comfortable with DNS changes
• Can dedicate a few hours over a weekend

Get professional help if:

• Over 20 users
• Complex shared mailboxes or distribution lists
• Previous email deliverability issues
• Need to migrate from multiple old accounts
• No one comfortable managing DNS
• Previous phishing or impersonation issues

Warning signs you need help:

• You're currently using free email for business and have had impersonation attempts
• You've already had a phishing incident
• Your team is not comfortable with technology changes
• You're not sure what your MX records are