Migration Areas

The work behind a clean transition.

Discovery & Readiness

Understanding identities, workloads, dependencies, data volume, compliance, applications, and the real source environment before moving anything.

Identity Transition

UPNs, authentication, synchronization, Conditional Access, guest identities, application access, and the identity changes users feel first.

Workload Migration

Exchange, Teams, SharePoint, OneDrive, voice, permissions, and the service-specific behavior that needs to survive the move.

Coexistence & Cutover

Routing, domain changes, staged moves, coexistence, communications, and the decisions that determine how disruptive cutover becomes.

Security & Compliance

Retention, labels, encryption, DLP, Defender, Conditional Access, and the governance framework that must be carried into the target state so security, compliance, ownership, and data controls remain intact after migration.

Validation & Recovery

Pilot validation, delta passes, user acceptance, failure analysis, remediation, and proving the target works before declaring success.

Migration Articles

Lessons from the move.


No Migration articles have been published yet.

How I Approach Migrations

Design for the user experience at the other side of the move.

My migration approach starts with discovery and the target-state experience. I map dependencies, identity, workloads, security, compliance, and coexistence before choosing the migration path. I use pilots and validation to prove assumptions, then measure success by whether users can work effectively in the target — not simply by whether the migration tool reports completed.