
Need to migrate some domain profiles, and would rather be doing anything but that? In this tutorial, we’ll present a way to automate this whole process, and do profile migration efficiently, and completely (so that you don’t have users complaining about missing data or personalization). In addition to profiles and files, you will also be able to copy applications and their settings, should you decide to transfer those as well.
Short answer: Zinstall Migration Kit Pro migrates Windows user profiles – with their files, settings and even the installed applications – to a new PC, to a new domain, from a local account to a domain account, or to Azure AD / Microsoft Entra ID, on Windows 11 and Windows 10. Microsoft’s own tool, USMT, runs from the command line and moves profiles, files and settings, but not the installed programs.1
We’ll cover several scenarios:
User profile migration in same domain
Profile migration to a different domain
Local profile to Domain profile migration
The simplest (and most common) user profile migration case is transferring Windows user profile from one computer to another, usually as part of a regular workstation refresh cycle.
This can be handled in multiple ways, depending on your requirements and existing toolset.
If the profiles are centrally managed / roaming profiles are implemented, and if you only need to transfer user data and basic personalization, all you need to do is add the new PC to the domain, log in and wait for the sync to complete.

In other situations, such as when workstations are not handled centrally, when roaming profiles are not available, or when you simply require a complete migration with the end result being as faithful as possible to the user’s original system, profile migration can be achieved using Zinstall Migration Kit Pro.
It is able to transfer profiles, data, accounts, settings, applications, and pretty much everything that makes the user’s system his home. It also ensures that the transfer is complete, and no user files have been missed in the process.
Note that you can also use the Kit in a command-line mode, which is useful in SCCM and other management tools integration. See “Command Line Execution” in the user guide.
That’s it! The profile contents are transferred to the other workstation – and the migration is complete.
When the goal is to move users to a new domain, the main issue is that old domain SIDs are not recognized by the new domain. This means that even if you have a way to copy the profiles over, they still won’t be accessible on the new domain.
The good news is that Zinstall Migration Kit Pro can automate most of such cross-domain migration (although not all of it). Using the product, you will be able to migrate user profiles from one domain to another, and still keep user files, settings and even applications intact.
The caveat in a cross-domain transfer is that you will not only need to join the target to the new domain, but also log in as the specific user you are transferring, in each domain. See instructions below.
This process does not disrupt the profile SIDs, and transfers settings in a way that is identical to a human operator manually transferring data and reconfiguring settings (although, unlike a human, it covers everything, and does not have to be “familiar” with a specific application in order to transfer its settings or even the application itself). This part also ensures that the new domain is not “trashed” with remnants of the old one.
The transfer works in a similar way as the regular migration instructions. The only difference is that you have to login as the original, old domain user (OLD-DOMAIN\USER) on the source machine, and as the replacement, new domain user (NEW-DOMAIN\USER) on the target machine. For more detailed instructions, see profile migration to different domain.
It also works even when you are switching to a new domain on the same PC. See instructions below, or a more detailed guide on in-place switch to a new domain.
The environment is a tangled mess of unmanaged, standalone workstations with local user accounts, and you have been chosen to untangle it and build a proper managed domain environment? That’s not going to be easy, but at least you can migrate the profiles without too much effort.
Migration Kit Pro can migrate local user profiles to domain profiles in the same way as cross-domain migration above.
Login as the local user on source, login as the domain user on target, and perform the migration (it also works in-place). See more details in local to domain migration guide.
USMT, Microsoft’s User State Migration Tool, moves user accounts, user files, Windows settings and the settings of some applications. It does not move the applications themselves, so every program has to be installed on the new PC before you restore.2 It ships in the Windows ADK and runs from the command line (ScanState captures, LoadState restores), which suits large scripted deployments.1
Join the new computer to the domain, run Migration Kit Pro on both computers, log in as the same user on both, and press Go on the new one. All of the users come over in one pass, with their files, settings and, if you want them, their applications – see the steps above.
Yes. Migration Kit Pro migrates a local user profile to an Azure AD / Microsoft Entra ID account, on the same PC or from one computer to another, keeping the user’s files and settings. Microsoft’s USMT doesn’t support Entra-joined devices.3 See how to migrate local profiles to Azure AD.
Yes. Migration Kit Pro migrates user profiles from Windows 10, or an older Windows such as Windows 7, to Windows 11, as well as between two PCs on the same Windows version, and brings the applications along if you want them. Windows 10 support ended on October 14, 2025, which is why many of these migrations happen now.4
Take the headache out of user profile migration.
(or contact us for more info and volume discounts).
Sources
1. Microsoft Learn: User State Migration Tool (USMT) overview, updated March 2025
2. Microsoft Learn: What does USMT migrate?, updated January 2025
3. Microsoft Learn: USMT requirements, updated January 2025
4. Microsoft Support: Windows 10 support has ended on October 14, 2025, updated June 2026