In our recent webinar, “A Practical Playbook to Migrate Users & Devices from Local AD to Entra ID,” we moved beyond theory and into execution. Mark Rochester “The Cloud Geezer” and Stacey Farrar from BitTitan walked through a real-world approach to synchronizing identities and transitioning both users and their devices to a cloud-native model.
This post is the first of two follow-ups focused on what was demonstrated and how MigrationWiz users can apply it today.
What We Demonstrated
The session centered on a common but often complex scenario:
- Source: Local Active Directory
- Destination: Entra ID (cloud-native identity)
From there, the team showed how to:
- Synchronize users across environments
Using Directory Sync to align users, groups, and attributes between on-prem AD and Entra ID enabling coexistence and phased migration. - Migrate data with MigrationWiz
Pre-staging and migrating core workloads like mailboxes, files, and collaboration data so everything is ready ahead of cutover. - Transition devices to Entra ID
Moving user workstations from local AD to Entra ID using Migration Agent preserving profiles, reconnecting apps, and eliminating manual reconfiguration.
Introducing the New Migration Stack
A key theme throughout the webinar was the New Migration Stack, a coordinated approach that brings together:
- Directory Sync → Identity alignment and coexistence
- MigrationWiz → Data migration (mailboxes, files, collaboration)
- Migration Agent → Device and profile migration
Both Directory Sync and Migration Agent are powered by PowerSyncPro technology, extending what MigrationWiz users can do beyond traditional data workloads.
The result is a unified migration workflow where data, identity, and devices move together not in disconnected steps.
Why This Matters for MigrationWiz Users
MigrationWiz has long been the foundation for reliable data migration. What the webinar highlighted is how you can now expand that foundation:
- Add Directory Sync to maintain identity continuity during migrations
- Add Migration Agent to automate endpoint transitions
- Deliver a complete migration experience not just data movement
For MSPs, this opens the door to:
- Higher-margin services (e.g., fixed-price per-device migrations)
- Reduced labor and fewer manual tasks
- The ability to scale projects without increasing headcount
For internal IT teams, it means:
- Less hands-on effort
- Fewer post-migration issues
- A smoother transition to Entra ID
Watch the Demo in Action
If you missed the live session you can still register to receive all the materials and webinar. If you just want to take a look at the workflows both demonstrations are available as videos.
- Full Webinar
- Identity synchronization between local AD and Entra ID
- End-to-end migration including data and device transition
These walkthroughs show exactly how the New Migration Stack operates in a real environment, giving you a practical reference for your own projects. Click here to access all three videos!
What’s Next
This blog focused on the how the process and tooling behind migrating users, data, and devices together.
In the next post, we’ll cover the questions raised during the webinar, including:
- Common challenges in AD to Entra ID migrations
- Best practices for phased cutovers
- How to handle edge cases and complex environments
Final Thoughts
The shift from local Active Directory to Entra ID isn’t just an identity migration it’s a full environment transformation.
With MigrationWiz, Directory Sync, and Migration Agent, MigrationWiz users now have a complete stack to execute that transformation efficiently reducing manual work, improving outcomes, and unlocking new opportunities for growth.
Stay tuned for the Q&A follow-up.