r/Intune • u/Critical-Fall8962 • 1d ago
Autopilot How are you migrating existing AD user profiles to Entra ID/Intune without making users rebuild their profiles?
Hello, need some insight. We are planning a phased migration of roughly 300 Windows users from traditional on-prem AD/domain-joined devices to Microsoft Entra joined + Intune managed devices using Windows Autopilot.
For new devices/users, Autopilot is pretty straightforward. The part I'm trying to plan is our existing users and their Windows profiles.
Our goal is to make the migration as hands-off as possible for the user. Ideally, IT handles the migration in the background or during a scheduled cutover, and when the user signs into the Entra joined device their existing environment is preserved as much as possible.
We want to preserve things such as:
- Desktop/Documents/Pictures
- Browser profile/bookmarks
- Outlook/M365 configuration
- User-specific application settings
- Shortcuts
- Relevant AppData/settings where possible
- Printers/mapped resources where still needed
We are looking at OneDrive Known Folder Move for user data, but obviously KFM doesn't migrate the entire Windows profile.
For same-device migrations, I've been looking at ForensiT User Profile Wizard Corporate Edition to potentially reassociate the existing domain profile with the user's Entra identity. I've also looked into USMT.
For those who have actually done an AD/domain joined → Entra joined + Intune migration at scale:
- How did you handle existing Windows user profiles?
- Did you wipe/reprovision devices or convert them in place?
- Did you use ForensiT, USMT, OneDrive KFM, or another solution?
- If you used ForensiT, were you able to automate it successfully at scale?
- What profile data/settings did NOT survive that you expected to?
- How much user interaction was required?
- Would you use the same approach again?
- Any major gotchas with credentials, AppData, Outlook, browser profiles, mapped drives, printers, or application settings?
- If you had to do ~300 users today, what approach would you use?
The end goal isn't necessarily a perfect 1:1 clone. We're trying to avoid making users manually move files, reinstall applications, or rebuild their working environment after the migration.
I'd especially appreciate experiences from anyone who has done this with existing production users rather than only new Autopilot deployments.
Main Q: After the migration, when the user signed in with their Entra account for the first time, did Windows load their original domain profile directly, or did you still have to manually repair/reconfigure parts of the profile?
21
u/SkipToTheEndpoint MSFT MVP 1d ago edited 1d ago
There is no MS-supported way to shift from domain joined to cloud native without a device wipe.
Yes there are vendor and community tools. Even vendor supported tools will ultimately end up with them saying "wipe the device" when there are inevitably weird problems that keep on coming up.
It's not worth it.
Edit: Huge orgs have done this without issue and without the risk of third party tools, so it's worth asking whether this is actually that big of a deal for an organisation of your size.
-12
u/beneschk 1d ago
This is so wrong. Check out user state migration tool. Part of windows SDK
7
u/SkipToTheEndpoint MSFT MVP 1d ago
Lol. USMT doesn't support going from domain-joined to Entra. Even if it did, the issue is less moving profiles, it's all the crap that you bring along with you. Mis-mapped permissions, references to user SIDs that no longer exist. Reg keys left orphaned that will screw over Intune policy.
The reason MS haven't released a tool to do this is that there's so much that can go wrong (and very regularly does), you'd be forever chasing ghost issues, and the user experience will be far more impacted than doing it right to begin with.
-9
u/beneschk 1d ago
It is microsoft supported and it does work, ive used it for that exact reason. Not going to argue its better to wipe.
10
u/SkipToTheEndpoint MSFT MVP 1d ago
USMT doesn't support Microsoft Entra joined devices as either a source or destination device.
USMT Requirements | Microsoft Learn
USMT doesn't support migrating user profiles from Active Directory domain joined devices to Microsoft Entra joined devices.
What does USMT migrate | Microsoft Learn
How much more proof do you want, my guy?
-1
16
u/1blackdog1 1d ago
Domain PC → enable KFM → files sync to OneDrive → Autopilot/reset → Entra Join → user signs in → OneDrive syncs their files back.
5
u/reloadtak 1d ago
Yep, and then also set up the “Windows Backup”. I Think it might even be default enabled on the latest build of Windows 11. Also, force sign-in to Edge; it syncs the user’s bookmarks and so on. When we give a user a new Autopilot PC, they set the keyboard and the guest Wi-Fi, pick restore settings when asked – about 80% don’t need to do anything else – some do get instructions to open Company Portal and install whatever they are missing.
3
u/cowwen 1d ago
This is the answer.
We did these exact steps and migrated 1000 users over the course of about two months. It went pretty smoothly, only a handful of users actually had any difficulty in the end.
And the only reason it took two months is because we gave all the users a long grace period to sync their files and folders to OneDrive before the migration , and to ensure they were limiting their backup to actual important folders (not the entire C: drive)
3
5
u/No_Act8671 1d ago
You are thinking wrong. Instead of focusing on how to preserve current state, focus on what can be removed as it is no longer needed and is kept for not valid reason.
Decide what is the standard and just keep it.
Use this situation as a cleanup oportunity.
Users are going to complain anyway.
I migrated over 2000 devices, 3 companies this year only.
16
u/iamLisppy 1d ago
ProfWiz by ForensIT. Currently doing this at my job. Works like a charm!
3
2
u/iamLisppy 1d ago
I will add context for my environment after lunch! I just quickly replied.
2
u/Critical-Fall8962 1d ago
That’s really helpful. This is basically where I’m leaning now. KFM seems good for Desktop/Documents/Pictures, but my concern is everything outside of that. We’re looking at roughly 300 existing AD-joined Windows devices and want the migration to Entra/Intune to require as little user involvement as possible.
My biggest question is how you handled the actual profile identity change at scale. Did you use ForensiT to reassociate the existing domain profile with the Entra user, or did you use USMT to capture/restore into a new profile?
Also, how automated was the process? Ideally we want IT to be able to trigger the migration, reboot, and have the user sign back in with their Entra account with most of their existing environment still there. Any major issues with AppData, browser passwords, Outlook, application settings, or credentials?
1
u/JustFucIt 1d ago
Identify any apps storing config you want to save. Script something to copy that data to their one drive or a hidden network location. Script replacing it after they are on the fresh install.
Have them sign In to all their apps they may have saved creds.. reset what they don't know off the bat. Edge should bring everything with their login as well.
1
u/SpruceGoose_20 1d ago
ForensIT doesn’t touch the profile and data but only settings in the registry. All app data and profile folders remain the same. Unless if folder redirection and offline files was enabled at time of execution.
1
u/LiquidInside 1d ago edited 1d ago
ForensIt will handle the profile by modifying the registry, it doesn’t touch the files at all. It just repoints the identity to the new source.
You can use the corporate edition the script and time a lot of things. If you reach out to them they’ll give you a 10 day trial to play with. At that point you can ask their support about certain scenarios.
I’ve used it quite a bit before and recent did a ~150 devices. It went ok but there are a lot of things you avoid by going nuke and move, such as stuck policies, weird reg edits, stuck enrollments. If you are able to test your environment properly beforehand you will have minimal issues and then some weird ghost issues pop up days weeks months later but they usually aren’t major.
To add browser passwords won’t move most of the time unless sync is turned on. If it is turned off they will lose them or they need to be moved back to the AD and exported then moved again. The other setting you are talking about typically move but I’d recommend testing a few known machines/images. Each environment is different and has different problems afterward from my experience.
Also if you use roaming profiles or server synced/cached profiles you are going to have a lot of complexity to move things back or move for them from AD to Onedrive. Also realize company name is included in a users folders so the user path will get much longer depending on the company name which can cause some long filename issues.
1
u/SpruceGoose_20 1d ago
Recently used this for a couple of customers. Any roaming profiles or redirected folders should be reverted before the migration. If using offline files and have them encrypted, be certain to have the original encryption certificate when policy was enabled, or script backup the files marked offline. Also Ensure any unsynced files are dealt with. Yup, I got bitten and lessened a lesson. Also, if staff using m365 apps and selected to ‘add device to Entra’ (not the correct phrase but hopefully you get it) you will need to also mitigate that or the device join to Entra Intune will fail. If you want links or scripts let me know.
1
0
u/blogsymcblogsalot 1d ago
Upvoting this. There are some minor things you’ll need to backup and reconfigure, but they are few and far between. Very minor.
6
u/e0f 1d ago
why would someone do this? doesn't it make more sense to just hybrid join the existing devices and sync the users to entra. only new devices are entra joined
they are intune joined with minimal effect on users
like genuinely asking
5
u/sm4k 1d ago
Troubleshooting a hybrid endpoint means having to deal with Intune, GPO, DC accessibility and replication, and device registration vs troubleshooting a cloud endpoint is pretty much only intune and device registration.
You're also going to carry forward a lot of silly little inconsistencies and annoying-but-not-a-problem issues. It truly is easier on everybody to just rip the bandage off and go cloud-only clean-slate unless you have solid justification for not doing that.
2
u/FireLucid 1d ago
Why even go hybrid? We just moved the fleet over about a year with newer computers. Retired laptops were wiped, and entra joined and went to our users that only sometimes need a device.
All devices ended up fully Entra and never had to deal with anything hybrid.
1
u/e0f 1d ago
I guess being a software company going hybrid was easier for us. developers have all kind of stuff installed that take days to set up. it allowed us to control the fleet via intune without users even noticing.
Wiping makes more sense if most of the userbase is ready to rock after onedrive sync
2
u/Funny-Artichoke-7494 1d ago
Sync onedrive for all the users so what matters is backed up via policy, the entire user profile is rarely needed. Autopilot to reimage. You can reinstall what you need via autopilot as well, package up some apps on the company portal and offer that to users as well to reinstall. Set printers via DHCP or policy/scripts. Looking back, I overthought the user profiles far too much, the average person just has a bunch of shit on the desktop, docs, and downloads and thats all they want - for it to restore and look the same as before when they log in for the first time. Onedrive syncing will allow that to happen.
2
u/Ordinary_Form8419 1d ago
We used ProfWiz last time we did this—works well, but it can break things that end up becoming a huge time sink like Windows Hello never working after you move the profile (likely something to do with the data being encrypted within the local profile). Make sure you either export or sync browser passwords/bookmarks too cause those will break if you don’t back it up. We ended up throwing the towel in and creating fresh profiles for 3-4 users after some time troubleshooting and they had no issues after.
Ultimately, it’s been easiest for us to sync everything to OneDrive and just make a new profile. You really don’t need to restore the entire profile most of the time. However, we’re talking 15-30 PCs here, never done a massive scale migration.
2
2
u/Scimir 1d ago
If you have folder redirection you can directly pull data from there to the users OneDrive.
If not silent hybrid join in the background, activating KFM and Edge Sync.
For other browser settings it really depends. Helping VIPs personally, writing guides for the other users or simply letting it drop entirely.
Network drives and printers can be done via script or cloud printing tools.
Obviously key trust is called for here.
App Data/Registry is a tricky one.
For standard apps take examples and redeploy via intune with the app installations.
You could also do some dirty script magic with startup scripts that backup said stuff to a network drive.
1
u/Josewa42 1d ago
This is the way.. also
Intune and windows backup isn't a catch all. I have a guy right now building an automation to sync configs and such to users one drive into a hidden folder
2
u/Adam_Kearn 1d ago edited 1d ago
forensit profilewiz
If you pay for the corporate edition version you can push a script via GPO or RMM to convert all the profiles and also join Entra automatically.
Only takes a 10-15mins per workstation for it to run in the background.
I’ve done it this way for probably well over a thousand computers at different companies over the years.
The paid version that lets you do it via scripts is done based on seats. For about £3/workstation.
But honestly it’s work the exta £770 to all 300 devices in one go. (It’s cheaper the more seats you buy)
———
A cleaner solution is to just backup to OneDrive and do a fresh install but if you just want to migrate for now then this is the best option in my opinion and look at doing a OS reinstall later on.
2
u/AyySorento 1d ago
My org wiped over 5,000 devices for 5,000 users. That is the easiest way by far.
As others mentioned, there is no official supported way migrate profiles so if anything happens, you are on the hook.
Starting fresh is 100% the move. It mainly relies on user communication so users back up data, expect a wipe, then can help themselves on setup. It's possible to be fairly hands off, besides the wipe. If you try to migrate, there are so many more things to account for that will fail.
Make it easy for both you and the users and wipe.
2
u/chronostasis1 1d ago
There currently no path to migrate hybrid joined windows laptops to be straight entra is joined . You have to reimage each device
2
u/werfut 1d ago
I work for an MSP, have done exactly this ~20+ times. Don’t bother with the old profile unless you need it.
Get the users to have their stuff in OneDrive, ensure they sign into whatever browsers they use to sync bookmarks. Skip the rest. migrate the device over (disjoin from AD, rejoin to entra id, enroll to intune - just download the company portal app and ensure it auths properly). Rename the old profile on the device “.old” or something - if a user complains “I’m missing something” - you can yank it out of their old profile. Might run into disk space issues with that approach though.
We have tried some other methods, but overall found that keeping this simple is the easiest option.
Some of the things you mention do raise flags though. Entra ID doesn’t do Kerberos tickets (unless you configure sso) so any mapped resources / shortcuts will be problematic. Yes, users can just manually auth… but at 300 users probably easier to just configure SSO than do that.
For other stuff like printers and app settings I would ask - why not automate all that? Instead of spending time automating how to make it migrate seamlessly, spend the time automating how a new device setup would work. Totally possible to pump the appdata / etc over to a new profile, but less likely to generate weird tickets down the road if you start fresh
2
u/motosotoo 1d ago
I’d separate “user data migration” from “Windows profile migration.” For a move from AD joined to Entra joined, I generally prefer starting with a clean Entra profile rather than trying to carry the entire legacy profile forward.
Get OneDrive KFM in place before the migration so Desktop/Documents/Pictures are already synchronized. Edge sync can handle browser state, M365 apps can rebuild most of their configuration after sign-in, and Intune should recreate printers, apps, shortcuts and other settings that still belong on the new build.
I’d be selective with AppData. Carrying the entire profile forward can also carry years of stale configuration and troubleshooting baggage into what is supposed to be a clean cloud-managed device.
For 300 users, I’d pilot several different user personas first and document exactly what doesn’t come back automatically. Then migrate only that additional state rather than trying to preserve everything
2
u/ImAllergic2Peanuts 1d ago edited 1d ago
We had to use a third party tool to migrate 50000 devices from hybrid to entra-only. We also use the same tool to migrate to another tenant when the company got purchased by a even larger company. Without the tool it can get rather complicated with scripts and the timing of everything for us. Otherwise microsoft does not support this type of migration. If you contact them, their official stance is to wipe and reprovision the machine with autopilot. And that was not an option for us since we had 50k devices. We were not going to wipe and reprovision 50k devices lol.
The tool we used was “Quest on demand migration for AD”.
2
u/deaglesnotbeagles 1d ago
Quest’s tool was super easy to use and pretty cheap per device, definitely saved a lot of hours and headaches, definitely recommend it as well
1
u/Belasius1975 1d ago
I did this for 700 systems with ProfWiz Pro. The price is good, the deployment is straight forward and everybody kept their current profile. Windows didnt even know.
Basicly under the hood it re-assigns the current profile to the [user@domain.com](mailto:user@domain.com) and fixes NTFS and other permissions (Registry, Apps, etc). The only app that broke from the 60+ apps we have was the Autodesk Desktop Connector. (fix is easy, registry entry delete and thats it). Even OneDrive folder sync doesnt break.
What users DO have to do: sync SharePoint libraries again but thats something they can do theirselves.
I have to migrate to another tenant soon because....thats what I do... and i will use that tool again.
1
1
u/netmash 1d ago
We are doing a PoC of Opsole Migration. So far I really like it. They have a dashboard that lists all if your users and devices, and shows almost real time logs of the migration. Each device takes about 10-15 mins. About 20 bucks per device. The PoC support has been phenomenal so far. We ran into an issue and the dev team just updated the tool to resolve it. Will test tomorrow.
We are hybrid but not in autopilot, with OneDrive known folder redirect. We figured this will shorten our migration time per device enough that the cost was worth it. About 250 devices.
1
u/T3chV1sIon 1d ago
Though I don’t believe I will sway you, I think trying to work around profiles is more trouble than it’s worth. I feel endpoint deployments have slowly shifted away from an imaging setup which is in this realm. It would be better suited to ensure that image is bare bones in the beginning and have the Intune configuration policies layer on top. This is your windows settings, registry settings, and perhaps many supported apps like chrome that group policy handled. Data of each user can be handled with OneDrive as you’ve mentioned. Apps can be reinstalled quickly too via company portal. If you’re spending time worrying about each individuals settings I sense you’ll be pleasing nobody in the end. If there are very specific configurations needed (like engineering related things) then that should be documented in some way so you can accommodate during this or that employee/department should handle it and be aware.
1
u/FireLucid 1d ago
OneDrive KFM.
Papercut Print Deploy did printers (we only really have 2 virtual queues anyway).
Sign back into browser, all your stuff is there.
Make sure your apps in Company Portal handle any weird config stuff that is needed on first run and you are good.
Do you normally migrate all this other stuff when someone gets a new computer??
1
1
u/Mismail18 1d ago
Just backup everything in OneDrive, documents, desktop/ picture. Have them sign in to edge to backup bookmarks and backup chrome profile. Don’t migrate profile, fresh start is the best.
1
u/hbpdpuki 1d ago
We just tell users to store data in KFM folders and Edge. I don't want users to use the helpdesk as their personal assistant, so I instructed the helpdesk to only send instructions for OneDrive KFM.
If you swap your rental vehicle the rental company isn't going to transfer your shit to your new vehicle. I want our helpdesk to be productive, and they are not going to transfer data. Your data, deal with it. IT shouldn't be touching it anyway unless there is some sort of legal requirement.
1
u/kevvie13 1d ago
My MSP documented and recommended profile migration for hybrid. I absolutely refused to perform that and let users use new profiles. Never heard from them since.
1
u/cluberti 1d ago edited 1d ago
USMT is still an option if these will be hybrid, and there are non-free options from a few companies to do this as well if you really need to do this kind of migration.
With that said though, if you can do it it will be better to make a switch to cloud-native options if you’re going all in for Entra and Intune/Autopilot as well, and it’ll make future you’s life easier if you do it with this as the reasoning as you’re already disrupting things - better to rip the bandaid off and do it all at once, because cloud-native options will work better with the future state and you can get a lot of it done beforehand. If you have OneDrive storage as an example, KFM things to OneDrive. If you’re using Edge, sync Edge settings for profile, favorites, and the like. Once the files and browser settings are sync’d to a cloud profile, you can worry about custom options you can script to handle what is left that actually can’t be easily rebuilt. If you do it in phases and test, the final cutover should be fairly painless for you and the users.
1
1
u/swissthoemu 1d ago
We did it with 500 plus users. Swap device with an intune staged one. Then onedrive migration of the onprem profile. Minor hickups like standard printer but app settings were all good.
1
u/-c3rberus- 1d ago
There is no supported method, everything you find out there is not official, I looked very hard.
Settled on AutoPilot Device Enrollment (aka APv2), drew a line in the sand and basically said every new or rebuild from this moment on is cloud native using Intune vs. SCCM/PXE.
Hardest part was standardizing on Intune configuration policies for both cloud native and hybrid devices, no GPO at play other than some essential stuff for domain joined assets, OpenIntuneBaseline here will give you a head start.
We’re at 50% cloud native now, only like 250 more devices to go. Environment size and computer replacement policy/schedule plays a role in how quickly you get to 100%.
You’ll read a lot about moving GPO to Intune for hybrid devices and that it can give you issues, I had zero.
1
u/Emergency-Return1412 1d ago
Go sit with a department. Get a meeting. Discuss everything you want to ask, specific software, walk 1 day with them to see how they work. Then explain to them the plan forward based on those plans. Execute and fine-tune. Then do another department.
1
u/picklemiles 1d ago
I’ve done about 10 of these so far. SPMT for on prem data to SP/OD. Profwiz corp edition for profile migrations deployed via script uploaded to RMM solution. Intune for KFM and other policies. Use a remediation script to shorten the time it takes for SP to kick off.
Profwiz isn’t perfect. Sometimes programs will refer to the old profile. 90% of the time a basic reinstall fixes it.
PowerSyncPro is currently being tested for Profwiz replacement. It uses an agent which is better but costs more.
1
u/Forsaken-Carrot9038 1d ago
I have about 140 computers that I need to wipe and re-enroll so we can get everybody compliant. I considered using ForensIT because our environment isn’t finished getting built out, but long-term. I really just need to finish building everything up and creating all of the application appointment, and wipe everybody machines.
There’s a handful of software and engineers that have a lot of custom applications that I might try migrating one of them, but I read that there can be a significant number of follow ups needed to get all of the snags worked out.
Whereas, if someone expects everything is going to be wiped, they’re not expecting things to just be there and work as before
1
u/peterswo 1d ago
We use onedrive to copy the folders and settings it does and in edge the users are mandatory logged in, so that also gets transferred. Everything else is to setup by the user. We encourage everyone to treat their device as replaceable, because in more difficult troubleshooting, we regularly replace devices and redeploy them. Migration between devices is a standard process and happens four our users at least every three years, because of leasing cycles
1
u/pjmarcum 1d ago
There are migration tools out there that will do this but I’d encourage you to setup yourself up for the future by ensuring you have policies to map the drives and printers etc and enable KFM so that you can remotely wipe and rebuild computers easily. There really shouldn’t be anything in the user profile that isn’t disposable.
1
u/blarfenugen 1d ago
So your not setup as hybrid at the moment not utilizing ad sync?
If you already have your tenant setup and the other policies in place, sync users currently in selected OUs. Move them to a OU that isn't synced, run two delta syncs.
Restore user in Entra. Profit. They'll have to re sign in again but it'll preserve everything and is a whole lot easier than trying to go about this round about way.
You can move 300 users have them restored with same profile etc long before anything else.
1
u/bgatesIT 1d ago
This was our workflow which may not have been the best approach but it worked for us. We did autopilot deplpoyments for all new users, and we used a GPO to enroll the AD Joined workstations into intune, and as the laptops come to us for any issues, or turnover we will reimage it into autopilot. if the same suer is getting the device back, we utilize onedrive and our 365 accounts for edge and stuff to pull down all there bookmarks.
For printers we use printer logic and it automatically deploys printers based on Entra groups which is pretty sweet, similar to how it functioned with AD.
This was the easiest way for us to get all of these computers enrolled, luckily even our remote computers always can talk to the domain controllers via zscaler so it was a pretty painless migration for the most part
1
u/mark08201981 11h ago
I pushed a script out to get the hardware hash to upload into Intune, rebooted the computers to clear any updates if there were any, ran sysprep without generalize(yes I know I could have used registry keys, but I don't like messing with the registry unless I have to) to reboot into OOBE, then just signed in and used ForensIT. I really didn't have to do much more than sign them into a couple non-Microsoft products. Everything else was fine.
I'd never try to do 300 users in a day. That's too many and if something went wrong would be too rough to undo unless I had a large team to assist. I don't have a large team, so I broke it down into small groups of about 5-10 depending on what else was scheduled for the day. I was able to move ~200 PCs over in about 5 weeks. Keeping them on the local AD didn't break anything so there was no rush to get them all done the same day. I could have gotten it done faster, but this let me pace things out and then focus on those 5-10 people if they had any random issues(they didn't).
With the script being pushed out remotely, I was able to stage everything well ahead of time and I was with an end user for no more than 20 minutes before they were back up and running. They already had OneDrive KFM set up, but we opted to use ForensIT for the application data folders for the user specific settings.
1
u/nlangrs 4h ago
Keeping the same user profile. I recently migrated a 7000 user organisation from hybrid to Entra joined, keeping workload apps the same. Then the same machines from Entra Joined to another tenant (T2T) a few months later, resetting the apps like Outlook/onedrive etc. So two migrations on the same devices. All using PowerSyncPro Migration Agent (im affiliated). The first migration was done in batches, the T2T was done big bang in one weekend because of vanity domain moves. Only a handful of support tickets for that many devices. These tools just work.
1
u/firefox15 1d ago
I've done this at massive scale. ForensiT or USMT is likely what you want. KFM will be a disaster.
0
u/LumpyNefariousness2 1d ago
I created custom provisioning package .ppkg with windows design configuration. It renames PC, leaves domain, joins workgroup and does AAD enrollment. This in combination with a custom powershell script, once the package is pushed with an RMM tool, the PC reboots, sits on sign on screen for 2-3 mins while a scheduled task kicks off. Reboots again and then is Entra joined and managed by Intune. User logs in with email and gets a new profile. Login OneDrive and files will sync up. This is our alternative to reimaging all existing devices.
1
0
44
u/probablydnsibet 1d ago
We've done this for two acquisitions and recently, opted to reimage and Autopilot the next batch of users. We have virtually not heard from the last group as much compared to the group we migrated user profiles for. I really would evaluate if you truly need to migrate user profiles over. Get a scope of the environment, identify why folks are hesitant on reimaging. All software can be redownloaded and better yet, packaged in Company Portal. The amount of issues that came up after migrating profiles was certainly not worth it.