Moving to Microsoft 365 from an on-premises server, another cloud platform, or a hodgepodge of consumer email accounts is one of the most impactful technology upgrades a business can make. It is also one of the most commonly botched. Missing emails, broken permissions, disconnected integrations, and employees locked out of their accounts are all preventable with proper planning.
This Office 365 migration checklist covers every step from initial assessment through post-migration validation. Follow it in order and nothing falls through the cracks.
Office 365 migration checklist: pre-migration (steps 1-4)
1. Inventory your current environment. Document every mailbox, distribution list, shared mailbox, and mail-enabled group. Record mailbox sizes, important folder structures, and any server-side rules. Identify all applications that send email through your current server (scanners, CRM, accounting software). Every sending source needs to be reconfigured for Microsoft 365.
2. Audit your domain and DNS. Confirm you have administrative access to your domain registrar. You will need to modify MX records, add SPF and DKIM records, and eventually configure DMARC. If you cannot access DNS, solve this before starting migration.
3. Choose your licensing tier. Business Basic for email and web apps only. Business Standard adds desktop Office applications. Business Premium adds advanced security features. Do not over-license users who only need email, and do not under-license users who need compliance features. Our Microsoft 365 management team can recommend the right mix.
4. Set up the Microsoft 365 tenant. Create the tenant, verify your domain, configure organizational settings, and set up the admin accounts. Apply Microsoft security defaults including MFA for administrators immediately. This step establishes the foundation everything else builds on.
Migration (steps 5-8)
5. Create user accounts and assign licenses. Provision every user account in Microsoft 365 with the correct license tier. Set temporary passwords and prepare welcome communications. Do not send login credentials to users yet.
6. Configure security before migrating data. Enable conditional access policies, configure anti-phishing and anti-malware settings, set up data loss prevention rules, and enforce MFA for all users. Tenant security configuration must happen before data arrives, not after.
7. Migrate email and data in staged batches. Start with a pilot group of 5 to 10 users to validate the migration process. Monitor for errors, verify email delivery, and confirm calendar and contact sync. Once the pilot succeeds, migrate remaining users in planned batches during off-hours to minimize disruption.
8. Cut over DNS records. Update MX records to point to Microsoft 365. This redirects incoming email to the new platform. Allow 24 to 48 hours for DNS propagation. During this window, monitor both old and new systems to ensure no email is lost in transit.
Post-migration (steps 9-12)
9. Verify data integrity. Spot-check migrated mailboxes for completeness. Verify calendar events, contacts, and shared mailbox access. Confirm distribution lists route correctly. Check that line-of-business applications (scanners, CRM, accounting) can send email through the new platform.
10. Configure OneDrive and SharePoint. Set up OneDrive for Business with Known Folder Move to redirect Desktop, Documents, and Downloads to cloud storage. Migrate shared file server data to SharePoint or shared drives with appropriate permissions.
11. Train users. Schedule training sessions covering Outlook, OneDrive sync, Teams basics, and security expectations (MFA enrollment, phishing reporting). Provide written quick-reference guides for the features your team will use daily.
12. Decommission old systems. Once migration is verified complete and users are stable on the new platform, decommission the old email server or cancel the previous provider. Do not rush this step. Keep the old system accessible in read-only mode for 30 days as a safety net.
What goes wrong without a checklist
The most common migration failures: email from scanners and line-of-business apps stops sending because SMTP relay was not reconfigured. Shared mailbox permissions break because they were not documented before migration. Calendar events disappear because the migration tool was not configured to include them. Users cannot log in because MFA was enforced before they were enrolled.
Every one of these is preventable with planning. Every one of them causes real business disruption when missed.
SADOS cloud migration services follow this checklist on every engagement with a dedicated project manager tracking each step through completion. If you are planning a migration and want it done right the first time, start with a conversation about your current environment and timeline.
