Home › Guides › Microsoft 365 Migration Plan

The 10-Step Microsoft 365 Migration Plan We Use for Sydney Small Businesses

A clean Microsoft 365 migration for a 5–25 person Sydney business takes 1–2 weeks end-to-end and starts from $1,200. The cutover itself happens in a single after-hours window. Everything before and after that window is what separates a smooth go-live from a week of "I can't get my email" tickets. This is the playbook we run.

Before you start: three things to get right

Most failed migrations don't fail at the cutover. They fail at the assumptions made before the cutover. The three things to nail down up front:

• What are you migrating from? Google Workspace, on-prem Exchange, IMAP/POP, or a mixed mess of cPanel mailboxes — each has a different migration path and a different gotcha list.
• What licence tier do you need? Business Standard for very small teams with minimal compliance exposure, Business Premium for anyone who wants Defender, Intune, and conditional access (which is most businesses these days).
• Who's the change champion? Someone in the business needs to communicate to staff, capture questions, and own the small post-migration friction. It doesn't have to be technical, just available.

The 10-step plan

Step 1 — Pre-flight assessment

Audit the current mail platform, total mailbox sizes (this drives migration time), shared file storage, line-of-business apps that touch email or calendar, and the device fleet. Document everything. The hidden Outlook plugin nobody told you about is the kind of thing that turns a 4-hour cutover into a 12-hour cutover.

Step 2 — Tenant setup and licensing

Provision the Microsoft 365 tenant in the correct region (Australia, for an Australian business), choose the right SKUs, and verify the primary domain. This step is invisible to staff — get it done early.

Step 3 — Identity and accounts

Create user accounts or set up Microsoft Entra Connect for hybrid environments. Enforce MFA from day one — it is far harder to retrofit MFA after staff are settled in. Configure baseline conditional access policies that match how the business actually works (block legacy auth, require MFA for admins, geo-restrict to Australia if appropriate).

Step 4 — Mailbox migration plan

Choose the migration method based on source and size: cutover for clean small migrations, staged for larger Exchange environments, IMAP for messy or non-Microsoft sources. Pick the cutover window (almost always after-hours on a quiet day). Communicate the timing to staff at least a week in advance with clear expectations of what will and won't work during cutover.

Step 5 — Pilot batch

Migrate 1–3 friendly users first. Don't skip this. Validate mail flow, calendar sharing, signature blocks, mobile device setup (iOS and Android both), and any line-of-business app integration. The pilot finds the surprises while there is still time to react.

Step 6 — Full cutover

Migrate the remaining users, update the DNS MX records, and monitor mail flow continuously for the first 24 hours. Have someone available to answer staff questions on the first business morning.

Step 7 — Post-migration validation

Confirm every mailbox is sending and receiving. Confirm every shared mailbox, distribution list, meeting room, and resource calendar made it across. Confirm OneDrive is syncing. Run the "boring checklist" so the surprises surface now, not three weeks from now in front of a client.

Step 8 — Security baseline

Enable Microsoft Defender for Business, configure anti-phishing and safe attachments, set tenant-wide MFA, configure self-service password reset, and baseline the tenant against the ACSC Essential Eight. This is the difference between "we have Microsoft 365" and "we have Microsoft 365 set up properly".

Step 9 — Backup configuration

Set up third-party Microsoft 365 backup. Microsoft does not provide long-term backup — the default retention is not a backup, the Recycle Bin is not a backup, and litigation hold is not a backup. Most owners are quietly shocked to learn this. Fix it on day one of go-live.

Step 10 — Documentation and handover

Document the tenant configuration, the admin accounts (with MFA evidence), the recovery procedures, and the runbook for adding and removing staff. Hand over to the in-house owner or, if you're moving to managed IT, to the team that will run it ongoing. This is the step most migrations skip — and the one that determines whether the configuration survives the next staff change.

How long it takes and what it costs

Indicative ranges for a typical Sydney small business:

• 5–10 users, clean source: 1 week, from $1,200.
• 10–25 users, modest complexity: 2 weeks, $2,500–$5,000.
• 25–50 users, hybrid identity or on-prem Exchange: 3–4 weeks, $5,000+.

These are starting points. Real numbers come out of the pre-flight assessment in Step 1.

Common mistakes we see in Sydney migrations

• Skipping the pilot batch. "It's only 12 users, just cut them all over." Then a SharePoint sync issue takes out half the team on Monday morning.
• Not enforcing MFA on day one. Retrofitting MFA on a tenant where staff are already comfortable is a political fight you don't need.
• Assuming Microsoft does backups. They don't. Litigation hold and the Recycle Bin are not a substitute.
• No documentation. Six months later, nobody can remember which admin account has which role, and the answer is buried in someone's personal OneNote.
• Buying Business Standard "to save money". Then needing Defender, Intune, and conditional access six months later and having to upgrade everyone anyway.

Frequently asked questions

How long does a Microsoft 365 migration take for a small business?

1–2 weeks end-to-end for 5–25 users, with the cutover itself in a single after-hours window. Larger or more complex environments stretch to 3–4 weeks.

How much does a Microsoft 365 migration cost in Sydney?

Indicative starting price from $1,200 for a clean small-business cutover. Final pricing depends on user count, mailbox size, source platform, and identity complexity.

Will my email go down during the migration?

If the migration is run properly, no. Mail flow stays on the source until the DNS cutover, then transitions in minutes. Brief delivery delays in the first hour are normal; outages are not.

Do I need Business Premium or is Standard enough?

Premium for any business that cares about cybersecurity, insurance, or compliance. Standard only for very small, low-risk teams.

Should I back up Microsoft 365 separately?

Yes. Microsoft does not provide long-term backup, despite what most owners assume.