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

TypeDescriptionBest For
Cutover MigrationMove all mailboxes at onceSmall orgs (<150 mailboxes)
Staged MigrationMove mailboxes in batchesMedium orgs using Exchange 2003/2007
Hybrid MigrationCoexistence between on-prem and cloudLarge orgs with Exchange 2010+
IMAP MigrationMove emails only from non-Exchange systems (like Gmail)Simple migrations without calendars/contacts
Tenant-to-Tenant MigrationBetween two Microsoft 365 tenantsMergers, acquisitions

2. SharePoint/OneDrive/File Migration

TypeDescription
On-prem file server to OneDrive/SharePoint
Google Drive to OneDrive
SharePoint on-prem to SharePoint Online

3. Azure Migration

TypeDescription
VM migrationMove VMs from Hyper-V, VMware to Azure
Database migrationMove SQL Server to Azure SQL Database
App ServicesLift-and-shift applications to Azure App Services

πŸ” General Migration Steps (Email Example)

πŸ“ Planning Phase

  1. Assess current environment (mailboxes, apps, size)

  2. Choose migration type (cutover, staged, hybrid, etc.)

  3. Inventory users and mailboxes

  4. Communicate plan to stakeholders and users

⚙️ Pre-Migration

  1. Verify domain in Microsoft 365

  2. Sync identities (via Azure AD Connect, if needed)

  3. Assign licenses to users

  4. Prepare source environment (backups, cleanups)

🚚 Migration Execution

  1. Set up migration endpoints

  2. Use appropriate tools (Exchange Admin Center, PowerShell, or third-party)

  3. Migrate data (emails, contacts, calendar)

  4. Monitor migration batches

✅ Post-Migration

  1. Change DNS records (MX, Autodiscover, SPF)

  2. Decommission on-prem servers (if needed)

  3. Monitor email flow

  4. Train users and support issues


🧰 Migration Tools

ToolUse
Exchange Admin Center (EAC)Native email migrations
PowerShellAdvanced control over migration
Azure MigrateVMs, servers, apps to Azure
SharePoint Migration Tool (SPMT)File/SharePoint migration
Microsoft FastTrackFree help for eligible M365 tenants
Third-Party Tools (BitTitan, Quest, CodeTwo)Tenant-to-tenant, mailbox & complex migrations

❗ Common Migration Issues

IssueCauseSolution
❌ DNS misconfigurationIncorrect MX or Autodiscover recordsVerify DNS settings post-migration
❌ Password mismatches or login issuesPasswords not synced or wrong UPNsSync identities or reset passwords
❌ Missing calendar/contactsNot included in IMAP migrationUse hybrid or third-party tools
❌ Throttling limitsMicrosoft limits how much data you can move at onceUse batching, or third-party tools with auto-throttle handling
❌ Large mailbox sizeMailbox exceeds 50 GB or 100 GB limitsArchive or split mailboxes
❌ Permissions lostCustom permissions not migratedReapply manually or via scripts
❌ User downtimeBad planning or MX record timingUse hybrid or staged migration for minimal impact

✅ Best Practices

  1. Plan thoroughly – Know what you’re migrating and the end goal.

  2. Communicate with users – Announce changes, expectations, and timelines.

  3. Pilot first – Always test with a few accounts before full rollout.

  4. Monitor logs – Use logs for errors, failures, and retry failures.

  5. Post-migration support – Be ready for user questions, password resets, and access issues.

Popular posts from this blog

Autodiscover

Azure Active Directory (Azure AD)

Active Directory (AD)