Migration
π What is Migration?
Migration is the process of moving data, applications, or services from one environment to another.
In the Microsoft ecosystem, this typically means:
Mail Migration (e.g., from on-prem Exchange to Microsoft 365)
Tenant-to-Tenant Migration
File/SharePoint Migration
Active Directory or user migration
VM/data center to Azure (cloud)
π¦ Types of Migration
1. Mailbox (Email) Migration
Type | Description | Best For |
---|---|---|
Cutover Migration | Move all mailboxes at once | Small orgs (<150 mailboxes) |
Staged Migration | Move mailboxes in batches | Medium orgs using Exchange 2003/2007 |
Hybrid Migration | Coexistence between on-prem and cloud | Large orgs with Exchange 2010+ |
IMAP Migration | Move emails only from non-Exchange systems (like Gmail) | Simple migrations without calendars/contacts |
Tenant-to-Tenant Migration | Between two Microsoft 365 tenants | Mergers, acquisitions |
2. SharePoint/OneDrive/File Migration
Type | Description |
---|---|
On-prem file server to OneDrive/SharePoint | |
Google Drive to OneDrive | |
SharePoint on-prem to SharePoint Online |
3. Azure Migration
Type | Description |
---|---|
VM migration | Move VMs from Hyper-V, VMware to Azure |
Database migration | Move SQL Server to Azure SQL Database |
App Services | Lift-and-shift applications to Azure App Services |
π General Migration Steps (Email Example)
π Planning Phase
Assess current environment (mailboxes, apps, size)
Choose migration type (cutover, staged, hybrid, etc.)
Inventory users and mailboxes
Communicate plan to stakeholders and users
⚙️ Pre-Migration
Verify domain in Microsoft 365
Sync identities (via Azure AD Connect, if needed)
Assign licenses to users
Prepare source environment (backups, cleanups)
π Migration Execution
Set up migration endpoints
Use appropriate tools (Exchange Admin Center, PowerShell, or third-party)
Migrate data (emails, contacts, calendar)
Monitor migration batches
✅ Post-Migration
Change DNS records (MX, Autodiscover, SPF)
Decommission on-prem servers (if needed)
Monitor email flow
Train users and support issues
π§° Migration Tools
Tool | Use |
---|---|
Exchange Admin Center (EAC) | Native email migrations |
PowerShell | Advanced control over migration |
Azure Migrate | VMs, servers, apps to Azure |
SharePoint Migration Tool (SPMT) | File/SharePoint migration |
Microsoft FastTrack | Free help for eligible M365 tenants |
Third-Party Tools (BitTitan, Quest, CodeTwo) | Tenant-to-tenant, mailbox & complex migrations |
❗ Common Migration Issues
Issue | Cause | Solution |
---|---|---|
❌ DNS misconfiguration | Incorrect MX or Autodiscover records | Verify DNS settings post-migration |
❌ Password mismatches or login issues | Passwords not synced or wrong UPNs | Sync identities or reset passwords |
❌ Missing calendar/contacts | Not included in IMAP migration | Use hybrid or third-party tools |
❌ Throttling limits | Microsoft limits how much data you can move at once | Use batching, or third-party tools with auto-throttle handling |
❌ Large mailbox size | Mailbox exceeds 50 GB or 100 GB limits | Archive or split mailboxes |
❌ Permissions lost | Custom permissions not migrated | Reapply manually or via scripts |
❌ User downtime | Bad planning or MX record timing | Use hybrid or staged migration for minimal impact |
✅ Best Practices
Plan thoroughly – Know what you’re migrating and the end goal.
Communicate with users – Announce changes, expectations, and timelines.
Pilot first – Always test with a few accounts before full rollout.
Monitor logs – Use logs for errors, failures, and retry failures.
Post-migration support – Be ready for user questions, password resets, and access issues.