Microsoft 365 Migration Guide for Small Businesses

We do M365 migrations regularly for NY/NJ businesses as part of our cloud services practice — moving from on-prem Exchange, hosted email, or Google Workspace. Here is the playbook, condensed.

Phase 0 — Decide if M365 is the right answer

It usually is, but not always. Reasons it might not be:

• You are on Google Workspace and your team has built around it. The cost of moving is real.
• You have specific compliance constraints that need a sovereign or dedicated tenant (rare for SMBs).
• You have an industry-specific email platform (some EHR systems, some legal practice management systems) that integrates more cleanly with hosted Exchange than with M365.

If those don’t apply, M365 is almost always the right answer for an SMB.

Phase 1 — Discovery (1 week)

Before touching any production systems:

• Inventory current mailboxes — count, sizes, archive volumes, public folders, shared mailboxes, distribution groups.
• Inventory current authentication — on-prem AD, Azure AD, Google Workspace SSO, none.
• Document current third-party integrations — CRM, ERP, helpdesk, line-of-business apps that send or receive email.
• Audit current licensing — what M365 SKUs do users actually need? E3? E5? F3? Business Basic / Standard / Premium?
• Identify retention and compliance requirements — eDiscovery, litigation hold, regulatory retention.

Output: a written migration plan with scope, licensing recommendation, timeline, and risk register.

Phase 2 — Tenant prep (1 week)

• Provision the M365 tenant.
• Verify domain ownership and add domains.
• Configure DNS records — but don’t change MX yet.
• Set up Entra ID (Azure AD) — sync from on-prem AD if hybrid, or use cloud-only with Entra ID Connect Cloud Sync if you are starting fresh.
• Configure conditional access policies — MFA, device trust, location-based rules.
• Set up data loss prevention (DLP) policies if compliance requires.
• Create user accounts and assign licenses.

Phase 3 — Mailbox migration (1–2 weeks for typical SMB)

The migration method depends on the source:

From on-prem Exchange:

• Hybrid migration (Exchange Hybrid Configuration Wizard) for cleanest experience.
• Cutover migration for orgs under 150 mailboxes that don’t need a phased approach.
• Both run in waves — pilot users first, then phased waves of 25–50 users.

From Google Workspace:

• Use the Microsoft Migration Manager or a third-party tool (BitTitan, Quest, AvePoint).
• Migrates mail, calendar, and contacts. Drive content moves separately to OneDrive/SharePoint.

From hosted Exchange:

• IMAP migration for simple cases.
• Exchange Online native migration if the source supports it.

From cPanel / generic IMAP:

• IMAP migration. Slow but reliable.

During migration, your old mailbox stays live. Mail is mirrored. Users keep working in the old environment.

Phase 4 — Cutover (1 evening / weekend)

• Final delta sync — bring across any messages received since last sync.
• Cut MX records to M365.
• Verify mail flow inbound and outbound.
• Update Autodiscover.
• Remove old mail server / decommission cleanly.
• Verify every user can send and receive on the new tenant.

A staged cutover means zero-mail-loss is realistic, not aspirational.

Phase 5 — Post-cutover (2 weeks)

• Outlook profile setup for every user — auto-discovery usually handles this; expect a few exceptions.
• Mobile device setup — typically just re-add the M365 account.
• Distribute end-user training (a short video or PDF) — what’s different, where things are, how to find help.
• Active support for the first two weeks — most issues surface in week 1.
• Decommission old infrastructure once you are confident.
• Optimize licensing — many migrations end up with too many or too few of certain SKUs; right-size after 30 days.

Common pitfalls

• Underestimating the size of mailboxes. A 25-user migration with 100 GB average mailboxes is not the same project as 25 users with 5 GB mailboxes.
• Forgetting public folders. Often used for shared calendars and contacts. Migration paths exist but require explicit planning.
• MFA rollout mishandled. MFA is non-negotiable, but rolling it out to a hostile user base on cutover day creates churn. Roll out MFA before migration, not during.
• Service accounts left behind. That scanner that emails PDFs? That copier? They have email addresses too. Inventory them in discovery.
• Conditional access too aggressive on day one. Start permissive, tighten over weeks, not on cutover day.
• Backup overlooked. M365 has built-in retention but is not a backup. Add a third-party M365 backup (Veeam, Datto, Druva, AvePoint) on day one.

What it costs

For a 25-user migration with average mailbox sizes:

• Project price typically $4,500–$9,000 (one-time)
• M365 licenses, ongoing: depends on SKU mix
• M365 backup, ongoing: $3–$5/user/month

For a 100-user migration: typically $15,000–$30,000 project price.

Timeline reality check

A typical 25-user M365 migration is 3–4 weeks end-to-end. Larger or more complex environments scale linearly. Anyone telling you they can complete a meaningful migration in a weekend is either lying or skipping discovery.

Related services

• Cloud Services — M365 migration, tenant management, and ongoing cloud administration
• Managed IT — post-migration support, licensing optimization, and day-to-day M365 operations
• Backup and Disaster Recovery — third-party M365 backup from day one, because Microsoft’s built-in retention is not a backup

If you are evaluating an M365 migration for a NY/NJ business, book a 30-minute discovery call. We will give you a written scope and quote within 48 hours.