Why Migrate from Local to Domain?
When a PC originally set up as a standalone workstation gets added to a corporate Active Directory domain, the existing local user account does not automatically carry over. Windows creates a brand-new profile for the domain account, leaving all the user's files, Outlook data, browser bookmarks, and application settings in the old local profile — inaccessible from the new account without manual intervention.
ProfWiz solves this by reassigning the existing local profile to the new domain account. The user logs in with their domain credentials and finds everything exactly as it was — no re-configuration, no data loss.
Prerequisites
- The PC must already be joined to the target domain before running ProfWiz
- You must run ProfWiz with local administrator privileges
- The domain account must exist in Active Directory before migration
- Download and install ProfWiz from this website
- Take a full system backup or at minimum a profile backup before starting
Step 1 — Join the PC to the Domain
Before ProfWiz can migrate the profile, the workstation must be a domain member. Open Settings > System > About > Join a domain (Windows 10/11) or use the classic Computer Name dialog in System Properties. Reboot after joining.
Step 2 — Log In as Local Administrator
After the reboot, log in using a local administrator account — not the local account you want to migrate, and not the domain account you are migrating to. This ensures neither profile is locked by an active session.
Step 3 — Launch ProfWiz
Right-click the ProfWiz executable and choose Run as administrator. The ProfWiz interface displays all local profiles it has detected on the machine.
Step 4 — Select the Source Profile
In the profile list, locate the local account you want to migrate. Click its row to select it. The right panel shows profile details including the SID, profile path, and last-used date.
Step 5 — Map to the Domain Account
In the Domain\User field, type the target domain account in the format DOMAIN\username or username@domain.com. ProfWiz will validate the account against Active Directory and confirm it exists before proceeding.
Step 6 — Run the Migration
Click the Migrate button. ProfWiz will:
- Remap the profile registry hive from the local SID to the domain SID
- Update the
ProfileListregistry key - Update NTFS ACLs throughout the profile folder
- Log every action to a migration log file
Depending on profile size, this typically takes two to five minutes.
Step 7 — Reboot and Verify
Once ProfWiz reports success, reboot the machine. Log in with the domain account. All desktop icons, Start Menu pins, application settings, and files in Documents, Desktop, and other shell folders should be present and accessible.
Troubleshooting Common Issues
Profile Not Listed
If the local profile does not appear in ProfWiz, the account may have a corrupt profile entry. Check HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList in the registry editor to confirm the profile is registered.
Domain Account Not Found
Ensure the machine has line-of-sight to a domain controller. Check DNS settings — the preferred DNS server should point to a DC. Run nslookup yourdomain.com to confirm resolution.
Access Denied During Migration
ProfWiz must be run as a local administrator. If you see access-denied errors, right-click and choose Run as administrator, or open an elevated command prompt and launch ProfWiz from there.
Automating with the Command Line
For bulk migrations, ProfWiz supports a fully scriptable command-line interface:
ProfWiz.exe /domain:YOURDOMAIN /user:newusername /MigrateLocalProfileThis makes it straightforward to wrap ProfWiz in a logon script, Group Policy startup script, or an SCCM task sequence.
Conclusion
Migrating from a local account to a domain account with ProfWiz is a reliable, repeatable process that takes less than ten minutes per machine. By following the steps above you preserve the user's entire working environment while seamlessly integrating the workstation into your Active Directory infrastructure.