Cloud Services / Microsoft 365
The week before a Microsoft 365 migration is rarely the problem — it's day two, when three employees can't access email, a shared mailbox has gone missing, and your cutover window was supposed to be "just a few hours." Understanding what a migration actually involves before you're in the middle of one is the only way to prevent that scenario.
What a Microsoft 365 Migration Actually Involves for an SMB
A Microsoft 365 migration covers far more than moving email. A complete migration includes mailbox migration, SharePoint Online and OneDrive data transfer, Teams provisioning, Entra ID and MFA setup, and license assignment — making it a multi-day project, not a weekend task.
The Full Scope of a Small Business Migration
- Exchange Online mailbox migration: Every user's email history, calendar, and contacts must transfer — not just the inbox.
- SharePoint Online and OneDrive provisioning: Shared drives need to be rebuilt with correct folder structure and permissions.
- Microsoft Teams provisioning: Channels, owners, and guest access policies must be configured — Teams doesn't self-populate from an old file server.
- Entra ID setup: Every user account must be created and verified before go-live.
- MFA enrollment: Multi-factor authentication must be configured per user before cutover, or day-one lockouts follow.
- License assignment: Each user needs the correct license tier assigned before accessing any service.
Skipping any one of these steps produces day-two chaos. A migration for small business environments typically runs five to fifteen business days when pre-migration discovery, pilot testing, and post-cutover support are included.
The Three Decisions That Determine How Smooth Your Migration Goes
Three choices made before cutover determine whether a Microsoft 365 migration runs cleanly or generates weeks of cleanup: migration method, legacy data strategy, and licensing tier. Getting any one wrong adds cost, downtime, or security gaps after the move.
Cutover Migration vs. Staged Migration
A cutover migration moves all mailboxes in a single pass — right for businesses under 150 seats with a single mail domain. A staged migration moves users in batches over weeks and suits larger organizations or complex on-premises Exchange environments. Choosing cutover for a 200-seat company on a legacy Exchange hybrid is a common cause of extended downtime.
What Legacy Data to Migrate vs. Archive
Migrating every email from the past decade inflates Exchange Online storage and slows the transfer window. Deciding which data migrates live versus moves to a low-cost archive tier before cutover prevents ballooning license costs — a step most vendor checklists skip.
Licensing Tier Selection: Business Basic vs. Standard vs. Premium
| License Tier | What's Included | Where SMBs Get It Wrong |
|---|---|---|
| Microsoft 365 Business Basic | Web/mobile Office apps, Exchange Online, Teams, SharePoint Online | No desktop Office apps — staff can't use Word or Excel offline |
| Microsoft 365 Business Standard | Everything in Basic plus desktop Office apps and webinar hosting | Chosen when Premium's security features were actually needed |
| Microsoft 365 Business Premium | Everything in Standard plus Intune, Defender for Business, and Entra ID P1 | Skipped to save cost — leaves endpoint security and conditional access undeployed |
Businesses that skip Business Premium and later need Defender for Business or Intune face a mid-year license upgrade and retroactive security remediation.
What Can Go Wrong — and What to Do About It Before Day One
The most disruptive Microsoft 365 migration failures are predictable and preventable. MX record propagation delays, Exchange hybrid misconfigurations, MFA enrollment gaps, and orphaned shared mailboxes are the four failure modes that consistently cause day-one support tickets for NJ SMBs.
MX Record Propagation Delays
MX records are DNS entries that tell the internet where to deliver email. Global DNS propagation after cutover can take up to 48 hours, routing inbound mail to the old server while staff expects it in Microsoft 365. The fix is DNS pre-staging: lowering MX record TTL 24-48 hours before cutover so propagation completes before the switch.
Legacy Exchange Hybrid Misconfiguration
Businesses on on-premises Exchange sometimes attempt hybrid coexistence — running Exchange on-premises and Exchange Online simultaneously during migration. Misconfigured hybrid connectors break mail flow silently, producing bounce errors with no clear cause. A managed migration validates connector configuration before any mailbox moves begin.
MFA Enrollment Gaps and Day-One Lockouts
Users never walked through authenticator app setup face immediate lockouts on first login from a new device. A pilot rollout of five to ten employees surfaces these gaps before the full company goes live.
Orphaned Shared Mailboxes
Shared mailboxes — accessed by multiple users for roles like info@ or billing@ — go missing at cutover when not explicitly added to the migration scope, without triggering an obvious error. Auditing shared mailboxes and distribution groups before migration begins is a step most checklists bury at the bottom.
CNS Data Inc. serves businesses across New Jersey and New York with on-site and remote cutover support — so when a propagation delay or lockout surfaces at 8 a.m. on go-live day, a local team handles it, not a vendor ticket queue. That coverage, same-day helpdesk access, and a fixed-scope engagement is what separates managed IT services for New Jersey businesses from a DIY migration guided by a generic checklist.
Frequently Asked Questions
How long does a Microsoft 365 migration take for a small business?
A small business Microsoft 365 migration typically runs five to fifteen business days when pre-migration discovery, pilot testing, cutover, and post-cutover support are included. Seat count, legacy platform complexity, and data volume are the main variables. Single-weekend timelines are realistic only for very small teams with clean source environments.
Will we lose email during the Microsoft 365 migration cutover?
Email loss during cutover is preventable with proper DNS pre-staging. Lowering MX record TTL 24-48 hours before cutover ensures propagation completes before the switch. Without this step, inbound email can route to the old server for up to 48 hours after go-live, causing messages to bounce or go undelivered.
Does Microsoft 365 migration require downtime?
A well-planned Microsoft 365 migration requires a short scheduled cutover window — typically a few hours outside business hours — but does not require days of downtime. MFA pre-enrollment, DNS pre-staging, and a pilot user rollout completed before cutover are what keep that window short and staff productive on day one.
What happens to our existing files and shared drives during migration?
Existing files and shared drives must be explicitly scoped and migrated to SharePoint Online or OneDrive — they do not transfer automatically when mailboxes move. Folder structure, file permissions, and shared drive access all need to be rebuilt or mapped in Microsoft 365 as a separate workstream from the microsoft 365 email migration.
Not Sure Where Your Microsoft 365 Migration Should Start? Let's Map It Out.
When you reach out to CNS Data, you get a scoped migration plan — timelines, licensing recommendations, and a clear cutover strategy — before any work begins, so there are no surprises on go-live day.
Schedule Your Free Migration Discovery Call
