Microsoft 365 migration is the most-discussed and most-misunderstood IT project in Melbourne in 2026. Half the SMEs we talk to think they’ve migrated already (because they bought M365 licenses). Half think it’s harder than it is (because the project they did with their last MSP went sideways). Most are sitting somewhere in between: they have email and Teams in M365, but SharePoint is a mess, OneDrive isn’t really being used properly, and security configuration was never finished.
This is a step-by-step migration guide for a Melbourne SME of 20-200 staff in 2026. It assumes you’re either coming from on-premises Exchange and file shares, from Google Workspace, or from a partial M365 deployment that needs to be cleaned up.
Phase 0 (week 0): Honest discovery
Before you migrate anything, you map what exists. Every email account, every shared mailbox, every file share, every line-of-business app integration with email or files, every recurring meeting, every distribution list, every M365 license you’re already paying for. Most Melbourne SMEs are surprised at how much shadow IT and unused licensing turns up.
Output: a discovery document covering source environment (Exchange version, file server topology, current backup), target M365 tenant (existing or new), licensing plan (right-sized for the headcount, not over-bought), and risk register.
Phase 1 (weeks 1-2): Tenant setup and identity
Stand up the M365 tenant or clean up the existing one. Configure DNS, MX records, SPF, DKIM, DMARC. Set up Azure AD Connect (or Entra ID Connect, current branding) if you’re syncing from on-premises Active Directory. Create accounts for everyone, with named admin accounts separate from day-to-day accounts.
This is also where you set up the security baseline. Conditional Access policies. MFA enrolment for everyone (admins first, then staff in a planned rollout). Defender for Business or Defender for Office 365 enabled. Audit logging on. Don’t migrate any data into a tenant without these in place — you’ll be moving data into an unhardened environment.
The detailed configuration is what our Office 365 security hardening piece covers.
Phase 2 (weeks 3-4): Email migration
Most migrations move email first because it’s the most user-visible and the most complex. Two main approaches: cutover migration (everyone moves on a single weekend) for organisations under ~30 mailboxes, or staged migration (mailbox-by-mailbox over weeks) for larger organisations.
Things that go wrong:
- Shared mailboxes that someone uses but nobody owns. Discover them in Phase 0.
- Old archive PSTs that need to come into the new mailbox. Plan for the import time.
- Mobile devices reauthenticating with old credentials. Send the comms in advance with screenshots for both iOS and Android.
- The marketing automation tool that uses an alias that didn’t make the migration list. List every system that sends or receives email and check each one.
For more detail on this phase, see our 5 essential steps for Office 365 migration piece.
Phase 3 (weeks 5-7): SharePoint and OneDrive
File migration is where most Melbourne M365 projects under-deliver. The temptation is to lift-and-shift the existing file share structure into SharePoint. Don’t. The result is a SharePoint that’s hard to navigate, hard to govern, and stops being adopted within months.
The right approach: design the SharePoint information architecture from the business workflow up. Sites for departments. Channels in Teams for projects. OneDrive for individual work. A retention policy. A sharing policy (especially around external sharing — by default, M365 lets users share files with anyone; lock that down before migration, not after).
Then migrate file-share data into the new structure, with archiving for data older than 12 months that nobody can prove is needed. Most file shares we’ve migrated were 60-80% archived material that never needed to be in the active workspace.
Phase 4 (weeks 8-9): Teams, governance, and adoption
Teams adoption is the difference between a successful M365 deployment and a “we paid for licenses but nobody uses them” deployment. Pick three to five business processes (project communication, approvals, leave requests, customer onboarding) and design the Teams workflows for them. Train people on those specific workflows. Don’t try to teach Teams as a whole platform — teach it as the tool for the specific things they’re already doing.
Governance matters too. Who can create new Teams? Who approves external sharing? What happens to a Team when its project ends? Document these in a one-page governance model and put it somewhere people will find it.
Phase 5 (week 10): Project sign-off and ongoing operations
Before you call the project done: confirm every account has MFA enrolled and is logging in successfully. Confirm Conditional Access policies are blocking what they should and not blocking what they shouldn’t. Confirm backups are running on the new M365 environment (M365’s native retention isn’t a backup — get a third-party backup tool). Confirm the user adoption metrics in M365 admin centre look right (low Teams usage at the end of week 10 is a sign training didn’t land).
Then transition the environment to ongoing managed support. The post-migration tuning over the next 90 days catches the issues users found but didn’t report.
Common mistakes Melbourne SMEs make
From the migration projects we’ve recovered for other people:
- Migrating before security hardening. The first phishing email after migration finds an unprotected tenant.
- Choosing the wrong license tier. M365 Business Standard for 50 staff at a regulated business is the wrong call. Microsoft 365 Business vs Enterprise covers the trade-offs.
- Not turning off the old environment. Old Exchange server still receiving email two months after migration because nobody updated the MX. Or worse, on the same internal IP causing routing weirdness.
- Skipping training. Teams sits unused, OneDrive isn’t synced, file share habits never break.
- No backup of the new environment. “But Microsoft has 99.9% uptime!” — uptime isn’t backup. Ransomware can encrypt OneDrive content too.
What this should cost in Melbourne, 2026
For a 50-staff Melbourne SME with email-only currently in M365 and on-premises file shares:
- Migration project: $18,000-$35,000 fixed price across the 10 weeks, depending on file volume and complexity
- Licensing: Microsoft 365 Business Premium is $33 per user per month (AUD, ex GST, 2026 pricing)
- Backup tooling for M365: $5-$8 per user per month
- Ongoing managed IT post-migration: standard managed IT pricing, since the M365 environment becomes part of the regular operations
If you’re being quoted significantly under that, look at what’s excluded. Significantly over, look at the actual scope.
Reference points
For the Australia-wide context, our Microsoft 365 migration guide for Australia covers regional considerations. For Melbourne-specific support after migration, our Microsoft 365 support Melbourne page is the entry point.
What to do next
If you’re planning a M365 migration in the next six months, start with the Phase 0 discovery. The discovery alone tells you more about your current IT environment than most SME owners realise. We’ll do it as a fixed-fee engagement and the report is yours regardless of whether you engage us for the migration.
Book a migration scoping call — we’ll send a sample discovery output and rough quote within 48 hours.
