Is Microsoft 365 right for your team?
Before the playbook, a five-minute honest comparison. M365 is not automatically the right answer for every small business.
Choose Microsoft 365 if:
Your team is primarily on Windows devices
You work in a regulated industry — finance, legal, healthcare — where Outlook and Excel are standard
You need device management across multiple locations (Intune is genuinely better than Google's MDM for this)
You have existing Microsoft infrastructure to migrate from
Consider Google Workspace instead if:
Your team is fully remote, mostly on Macs, and already lives in Google Docs
You have under 10 people and want the simplest possible setup
Real-time collaborative editing matters more than Outlook features
The hybrid reality: some businesses use M365 for security and device management alongside Google Docs for specific workflows. This works but adds cost and complexity. Standardise on one platform if you can.
Before you start: the checklist nobody gives you
The most common reason migrations go wrong isn't technical complexity — it's skipping the pre-migration audit. Before any migration work begins, confirm all of the following:
Domain and DNS:
Your domain is registered in your business's name, not your IT provider's
You know who controls your DNS records (usually your domain registrar)
You have access to the domain registrar account with 2FA enabled
Email inventory:
List every mailbox: individual users, shared mailboxes (billing@, info@, hello@), and service addresses
List every alias — multiple email addresses routing to the same inbox
Confirm whether mailboxes have calendar or contact data that needs migrating
Existing data:
Where are your files currently? Local drives, a NAS, Dropbox, Google Drive?
Do these files need migrating, or can your team start fresh in SharePoint?
Is there a verified backup of everything before the migration starts?
Licences:
Decide on the M365 tier. For most small businesses: Business Standard (email + Office apps) or Business Premium (everything + Intune + Defender). Business Premium is worth the extra €8/user/month if you want device management.
Count exact users. You can add licences as you grow — don't over-provision.
Timing:
Avoid migrations at month-end, during your busy season, or the week before a major deadline.
Allow 3–4 weeks minimum.
Plan the DNS cutover for a Friday afternoon — that gives you the weekend for any surprises.
The week-by-week plan
Week 1: Tenant setup and security baseline
Your new M365 tenant is configured before a single email is moved:
Create the tenant and add your domain
Create all user accounts (without licences yet)
Enable MFA for all users
Apply Conditional Access policies
Set up shared mailboxes and aliases
By end of Week 1: every user can log into M365 and access OneDrive and Teams. Email is not yet pointing here.
Week 2: Data migration
Files first, email second:
Migrate shared file storage from current location to SharePoint
Set up Teams channels — start simple, a few channels, not 40
Run a 30-minute team walkthrough: where files live and how to access them
Email migration runs in the background via Microsoft's native tools or BitTitan. The old email system stays live throughout this week.
By end of Week 2: files are in SharePoint, email is syncing quietly, old system still active.
Week 3: Device setup (Business Premium / Intune only)
Enrol Windows devices into Intune
Push configuration profiles: encryption, password policies, automatic updates
Configure Windows Autopilot for any new or replacement devices
Enrol Macs via Apple Business Manager if needed
Test remote wipe and lock on a spare device
Week 4: DNS cutover
The only irreversible step:
Update the MX record to point to Microsoft
Update SPF, DKIM, and DMARC records
Test send and receive from Outlook, iPhone Mail, and all shared mailboxes
Monitor for 24 hours before declaring success
If anything goes wrong: the DNS change is reversible in minutes. Migrated email stays in M365 regardless.
After a clean 24 hours: decommission the old email platform.
The three mistakes that cause downtime
Mistake 1: Cutting DNS before enabling MFA
If email points to M365 before MFA is active, every account is exposed with just a password. Security baseline first, DNS cutover second — always.
Mistake 2: Forgetting shared mailboxes
The billing address, the info@ account, the support inbox — these get missed in almost every migration. Document every shared mailbox before you start.
Mistake 3: No backup before cutover
Before touching DNS: confirm (a) you have a recent export of existing email, and (b) your backup solution is running on the new tenant. Migration mistakes are recoverable with good backups. Without them, they're not.
What to expect from your IT provider
If a managed IT provider is running this migration for you, here is the minimum standard:
A written pre-migration checklist, shared with you, before anything starts
You hold all admin credentials — the provider administers them, not owns them
You're notified before any DNS change is made, not after
A tested backup restore before cutover
Post-migration monitoring for at least 48 hours
Written handover documentation showing how everything is configured
If your provider won't give you these, that's worth knowing before the migration starts — not after.
