Cloud Migration Checklist: Moving Your Business to Microsoft 365

You've decided to move to Microsoft 365. Smart call. But the migration itself? That's where things go sideways for a lot of businesses. Lost emails, broken workflows, confused employees - it doesn't have to be that way.

Here's the checklist we use when migrating Orange County businesses to M365. Follow it and you'll avoid the pain that comes from rushing the process.

Phase 1: Assessment & Planning

Inventory everything. Before you move anything, you need to know what you have:

• How many mailboxes? What sizes? Any shared mailboxes or distribution lists?
• Where does your data live? On-premise file server? Local drives? Dropbox? Google Drive? All of the above?
• What applications do your teams use daily? Do they have cloud equivalents?
• Do you have any compliance requirements (HIPAA, legal holds, data retention policies)?
• What's your current internet bandwidth? M365 is cloud-based - slow internet means slow everything.

Choose the right license tier. Microsoft's licensing is intentionally confusing. Here's the quick version:

• Business Basic ($6/user/month) - web-only Office apps, email, Teams, 1TB OneDrive. Good for frontline workers.
• Business Standard ($12.50/user/month) - desktop Office apps + everything in Basic. The sweet spot for most small businesses.
• Business Premium ($22/user/month) - adds advanced security, Intune device management, and Azure AD Premium. Worth it if you handle sensitive data.

Most of our clients land on Business Standard with Business Premium for leadership and anyone handling sensitive information.

Phase 2: Security Setup (Before Migration)

This is where most DIY migrations fail. They move the data first and think about security later. Do it the other way around:

• Enable MFA for all accounts - no exceptions. This is the single most important security step. Use the Microsoft Authenticator app, not SMS.
• Configure conditional access policies - block sign-ins from suspicious locations, require compliant devices for access.
• Set up email security - SPF, DKIM, and DMARC records. These prevent attackers from spoofing your domain. Check your current email security before you migrate.
• Configure data loss prevention (DLP) - if you handle credit card numbers, SSNs, or other sensitive data, set up DLP policies to prevent accidental sharing.
• Enable audit logging - turned off by default. Turn it on. You'll want the paper trail.

Phase 3: Data Migration

Email migration. This is usually the biggest piece. Options:

• From Exchange on-premise: Use hybrid migration or cutover migration depending on size. Hybrid is cleaner for 50+ mailboxes.
• From Google Workspace: Microsoft's migration tool works, but third-party tools like BitTitan are faster and more reliable.
• From IMAP (GoDaddy, Rackspace, etc.): IMAP migration in Exchange admin center. Plan for a DNS cutover window.

File migration. Moving files to SharePoint and OneDrive:

• Map your folder structure to SharePoint sites and document libraries. Don't just dump everything into one site.
• Use SharePoint Migration Tool (free from Microsoft) or Mover for larger migrations.
• Clean up first. That 2017 folder with 4,000 unused files? Don't migrate garbage.
• Set permissions before moving data. SharePoint permissions are different from NTFS - plan them.

Phase 4: DNS Cutover & Go-Live

The moment of truth. MX records get pointed to Microsoft 365, and new mail starts flowing to the new system.

• Schedule the cutover for a Friday evening or weekend to minimize disruption
• Lower DNS TTL values 48 hours before cutover (reduces propagation time)
• Have the old system running in parallel for 72 hours minimum
• Test mail flow immediately - send test emails from external accounts
• Verify Autodiscover, SPF, DKIM, and DMARC records are correct

Phase 5: User Training & Adoption

The migration is only half the battle. If your team doesn't know how to use the new tools, you've spent money to create confusion.

• Teams - show people how to chat, meet, and share files. Most businesses use 10% of Teams' capability.
• OneDrive - explain the difference between OneDrive (personal) and SharePoint (shared). This confuses everyone.
• Outlook - the web version is actually great. Show people the features they don't know about: Focused Inbox, scheduling, shared calendars.
• Mobile setup - get Outlook and Teams on everyone's phone. Use Intune if you have Premium licenses.

Common Mistakes to Avoid

• Not testing backups before migration - have a rollback plan
• Skipping the security setup - a fresh M365 tenant with default settings is surprisingly insecure
• Migrating on a Monday morning - Murphy's Law applies double to IT projects
• Forgetting about mobile devices - email on phones needs to be reconfigured
• No communication plan - your team needs to know what's happening, when, and what to expect

Should You DIY This?

For a 5-person company with basic email? Probably fine. For anything larger, or if you have compliance requirements, legacy systems, or complex data structures - get help. A botched migration costs more than doing it right the first time.

We've migrated dozens of Orange County businesses to Microsoft 365 - from 10-user law firms to 200-employee manufacturing companies. The process is predictable when you follow the checklist.