NOTE: This only works between like profile versions.  eg. You can’t migrate your 2008R2 profiles to Server 2016 and expect it to work.  See this chart.

I moved from UPM to FSLogix earlier this year, and decided to write my own powershell script to convert the UPM profiles to .vhd.  FSLogix has its own conversion process (which I didn’t find a whole lot of info on), but I decided to create my own.

What this script does:

1. Gets a list of all UPM profile directories in the root path (that you supply) and displays them to you to select which one(s) you would like to convert via out-gridview
2. For each profile you select:
   1. Gets the username from the profile path – you will have to edit this part for your environment… explanation in the script
   2. Use the username to get the SID (FSLogix profiles use the username and sid to name the profile folder)
   3. Creates the FSLogix profile folder (if it doesn’t exist)
   4. Sets the user as the owner of that folder, and gives them full control
   5. Creates the .vhd (my default is 30GB dynamic – edit on line 70 if you wish to change it) – if it doesn’t exist (if it does skip 7, 9-10)
   6. Attaches the .vhd
   7. Creates a partition and formats it ntfs
   8. Assigns the letter T to that drive (edit on line 73 if you wish to change that)
   9. Creates the T:\Profile directory
   10. Grants System/Administrators and the user full control of the profile directory
   11. Copies the profile from the UPM path to the T:\Profile directory with /E /Purge – if you are re-running this script on a particular profile it will overwrite everything fresh
   12. Creates T:\Profile\AppData\Local\FSLogix if it doesnt exist
   13. Creates T:\Profile\AppData\Local\FSLogix\ProfileData.reg if it doesn’t exist (this feeds the profilelist key at logon)

Here is the script!