How to Move Email from Gmail or iCloud to Microsoft 365

Sooner or later most small businesses outgrow personal Gmail or iCloud email. The trigger is usually the same — a client politely asks why your address is yourbusiness@gmail.com, you realise you can't share a mailbox with your bookkeeper, or you need a real calendar that works with Teams. This guide covers the practical steps to move your email to Microsoft 365 without losing a single message — and the pitfalls that catch people out.

Why Businesses Migrate

A few honest reasons we hear every week:

• Professional address. you@yourbusiness.com.au wins quotes that yourbusiness@gmail.com doesn't, especially in trades, professional services and B2B.
• Shared mailboxes. info@, accounts@, service@ — multiple staff need to see the same inbox without sharing one person's login.
• Real calendars. Booking meetings across staff, seeing free/busy, hosting Teams calls from a calendar invite that actually works.
• Compliance and security. Insurance, ATO records retention, ASIC requirements. Personal Gmail isn't appropriate for client records.
• Teams, SharePoint, OneDrive. Once you've got 365 you get the whole suite — see our why Microsoft 365 overview.
• You got hacked. Sadly often. See our email hacked guide — moving to 365 with MFA is usually part of the recovery.

The Decision Before You Start: Domain Name

If you've already got a custom domain (yourbusiness.com.au) — great, you'll just point its mail records (MX records) at Microsoft 365 at cutover time. If you don't, this is the moment to buy one. Don't migrate to 365 and stay on a @gmail.com address; that misses the whole point. A .com.au domain is around $20/year and one of the highest-ROI things a small business can buy.

Step-by-Step: Small Mailbox Migration (Under 50 GB)

For a single-person or small-team migration where each mailbox is under 50 GB, here's the path we use. If you're more than 5 mailboxes or have shared mailboxes already, skip to "When to call us".

1. Buy Microsoft 365 Business Standard (or Basic)

Either through Microsoft direct, a partner, or us. Business Basic ($10.20/user/month) gives you the mailbox + web Office. Business Standard ($17.20/user/month) adds desktop Office apps. Most small businesses go Standard.

2. Add and Verify Your Domain

In the Microsoft 365 admin centre, add your domain. Microsoft gives you a TXT record to add at your domain registrar (CrazyDomains, VentraIP, GoDaddy, etc) to prove you own it. This takes 5 minutes plus DNS propagation.

3. Create User Mailboxes

For each person, create a 365 user with their new name@yourbusiness.com.au address. Don't change DNS yet — at this point new email is still going to your old system.

4. Pre-Migrate Existing Email (Before Cutover)

This is the part that matters. You want all the existing Gmail or iCloud email copied into the new 365 mailbox before you flip the switch, so users don't lose anything.

For Gmail / Google Workspace: Microsoft has a built-in Gmail migration tool in the admin centre that uses Gmail's API. It's the cleanest option. You authenticate it to your Google account, point it at the target 365 mailbox, and it copies messages with folder structure (Gmail "labels" become folders).

For iCloud: No direct migration tool exists. You either use IMAP migration (set up iCloud as an IMAP source in 365) or the manual Outlook drag-and-drop method (open both mailboxes in Outlook, drag emails across). For a single mailbox the manual method is fine; for any volume, IMAP migration.

For other IMAP mailboxes (anything else): 365 has an IMAP migration tool. You provide source server settings and credentials, it pulls messages over.

5. Update DNS (the Cutover)

Once mailboxes are pre-loaded, change your domain's MX records to point at Microsoft 365 (Microsoft provides the exact values). Within a few hours, new email starts arriving in 365 instead of the old system. Leave the old system active for a week as a safety net — late-arriving mail will trickle in there.

6. Set Up Clients

Install Outlook on each user's PC/Mac, sign in with their new credentials. On phones, set up the Outlook mobile app or use the built-in mail with Exchange settings. Older versions of Outlook (2016 and earlier) don't always play well with modern 365 — upgrade if needed.

7. Enable MFA, Set Up Backups

Before you tell users the migration is "done", turn on MFA for every account. We treat this as part of the migration, not optional. See our MFA guide. Also set up third-party 365 backup — Microsoft does not back up your mailbox in a way that protects against accidental deletion or ransomware.

The Pitfalls That Catch People

Calendar invites

Existing calendar invites on Gmail don't migrate cleanly. Recurring meetings in particular often need to be recreated. Plan to manually re-issue any standing meetings.

Contact groups / labels

Gmail labels are messier than Outlook folders. A Gmail message with three labels appears in three "folders" in 365 (one duplicate per label). Contact groups don't migrate at all — they need to be re-created as distribution groups in 365.

Email aliases

If you had sales@ and info@ all forwarding to one Gmail, you'll want them set up as proper shared mailboxes or aliases in 365. This is a config job at migration time.

Filters and rules

Don't migrate. Re-create the important ones in Outlook after cutover.

Signatures

Set up fresh signatures in Outlook — old ones won't carry across.

Apps and integrations

Anything that was sending email through your old Gmail (Xero, MYOB, your CRM, your website contact form) needs reconfiguring to send via 365. Easy to miss — and you only notice when invoices stop arriving.

SPF/DKIM/DMARC

Email authentication records need updating to include 365 as a valid sender. Skip this and your emails start landing in spam folders. We always check and configure these as part of migration.

When to Call Us

Honestly, for a single-user migration with a small mailbox, the Microsoft tools are workable if you're technical and patient. Where we earn our money:

• Multi-user migrations — getting 5+ people across without a stuff-up requires planning, a cutover window, and someone to be available when something breaks at 7am Monday.
• Mailboxes over 30 GB — IMAP migrations get slow and flaky at size. We use Microsoft's bulk migration tools and run them in scheduled batches.
• Existing Exchange or Google Workspace — these support proper "cutover" or "staged" migrations that preserve calendar items, contacts, the lot. Worth doing properly.
• You need it done outside business hours — most migrations cut over Friday evening so Monday morning everyone is on the new system.
• You want it to come with MFA, backup, DMARC, all configured — that's our standard delivery.

See our Microsoft 365 Townsville page for our typical migration pricing.

Frequently Asked Questions

Will my email be down during migration?

If done properly, no. Mail keeps flowing into the old system until the DNS cutover, after which it flows into the new system. You'd be unaware anything was happening except a slightly different login screen.

What happens to my old Gmail/iCloud account?

Stays exactly as it was. We typically leave it active for 30 days then archive it (export to a .pst or .mbox file kept locally) and close it.

How long does a migration take?

A single mailbox of 5 GB takes a few hours of elapsed time, mostly waiting on data transfer. A 5-user migration with 30 GB each takes a day of preparation, an overnight bulk move, and a Monday morning checkpoint. Most SMB migrations are quoted at 4-8 hours of our time.

Do I lose anything by leaving Gmail?

You lose Gmail's search and AI features (Outlook search is fine but not as quick). You gain shared mailboxes, calendars that don't fight Outlook, Teams, SharePoint, and a stack of compliance tools. Most businesses don't look back.

Can I keep using Gmail's interface with a 365 mailbox?

Technically yes (via IMAP), but it disables most of what makes 365 useful — calendar sharing, Teams integration, etc. We don't recommend it. Outlook on web/mobile is genuinely good now.