How Long Does a Windows Device Migration Take?
How long does it take to migrate a Windows device with PowerSyncPro Migration Agent?
09 November 2026On average, PowerSyncPro Migration Agent migrates a Windows device in as little as 15 minutes, including restarts. The clock runs from the moment the runbook starts to the moment the user could sign in with their target account.
Treat 15 minutes as a planning figure, as we can not guarantee. The same runbook can take under 5 minutes on one device and much longer on another. Typical ranges:
- Lab or test virtual machine with one fresh profile: under 5 minutes.
- Modern laptop with a solid state drive, fast internet, no large applications/data or attached disk, and one user: 15 minutes or less, including restarts.
- Shared PCs in hospitals, schools, libraries and contact centres with dozens of user profiles: longer, because every profile is processed.
- Older desktops with spinning hard disks or large attached data drives: longer again.
What affects migration time
Most of the time goes on re-permissioning. PowerSyncPro Migration Agent does not copy data. It updates the security settings on every file, folder and registry key that belongs to a migrated user, so they point to the new account. These factors decide how long that and the rest of the runbook take.
- Disk speed. Re-permissioning touches the security settings of every file on the volume(s). A solid state drive does this many times faster than a spinning hard disk.
- Number of files, not their size. A profile with 300,000 small files takes longer than one with a few large video files, because each file has its own permissions to update.
- Number of user profiles. Each profile in the translation table has its files and registry hives re-permissioned. A shared PC with 60 profiles does that work 60 times.
- Attached disks. Secondary volumes and data drives in scope are re-permissioned too.
- Servers could take considerably longer due to their complexity.
- Restarts. A change of join state needs two restarts. Pending Windows updates, slow firmware, heavy startup applications and old hardware all lengthen each restart.
- Runbook settings. Every option you turn on adds steps: application resets, join state change, printer and file share updates, and pre and post migration scripts. Custom scripts add their own run time.
- Security software. EDR and antivirus tools often inspect mass permission changes and can slow or stop the agent. Add the recommended exclusions before you migrate.
- Network. The device needs a steady connection to the PowerSyncPro server for the whole run, plus a domain controller for AD joins or internet access to Microsoft Entra for Entra joins.
- What do you count as a completed migration? For example, Hybrid Joined cannot be forced, but encouraged, and the same with Intune enrolment. PowerSyncPro has a completed log message for when the user could log in, but also one post login when they have accepted the toast notification (and any AppX step has completed). If they do that the next morning, this could skew your averages. Also, if they struggle to put in a WHfB passcode or set up MFA that also might not be the best reporting mechanism.
What happens after the user signs in
At first sign-in, a short step re-permissions Store apps such as Company Portal (appx) in the user’s own context. Since version 3.1 this usually takes under a minute. Outlook, Teams and OneDrive then connect to the target tenant for the user to sign in to for the first time, if the runbook resets the apps. Microsoft Entra hybrid join (formerly hybrid Azure AD join) and Intune enrolment finish in the background, so the user can start work.
How to get an accurate figure for your estate
Time a pilot batch that matches your real fleet: a standard laptop, a shared PC and your oldest supported desktop. The PowerSyncPro console logs every runbook step, so you can see where the time goes and size your migration windows from real numbers.
Tell users not to sign in until the migration finishes, and turn on Prevent Login to enforce it. An early sign-in locks the profile, stops re-permissioning and usually breaks the migration.
Latest from Blog
GCC High migration: identity and device migration
21/10/2026GCC High migration: how to move identities and Windows workstations securely
Learn More →
Why it's time to replace FIM & MIM
04/08/2026As MIM approaches end-of-support, we ask what is the path forward for identity management? For decades, Microsoft Identi...
Learn More →
How to make your Windows migration a success
29/07/2026Everything you need to know before your next Windows migration project. Whether you're planning a tenant-to-tenant migra...
Learn More →