[Connetic #313307] Google to Microsoft Migration - Initial Migration Scan for Drive Objects
4/1/2024 - Joshua Mathis:
Here is the initial scan results from the Migration tool, in reference to Drive Data.
Two files: One will be the entire scan in its entirety. Second where I stripped out only the ones that had issues that will need to be reviewed.
The ones with issues is saying that these files will be skipped, and they list the reason for the error. These might either be personal shortcuts, or files that just aren't supported that are from another 3rd party application. I am actually pleased at the low amount of these within the report but we will still nonetheless have a decent number to mitigate.
Refer Google My Drive / Google to Microsoft Migration
To further this along. It looks like most of the items that are not able to migrate are due to naming. Anything with a special character in name ( : . * & ) in the name will have to be renamed without it.
kms review:
Failure reason for every one: Shortcut is not supported for migration
There were some paths with “*” in them, but they were also Shortcuts.
kms reply to the ticket email:
Looking at the Failure Reason column, each one of the +/- 78 items is flagged as "Shortcut is not supported for migration".
Since OneDrive does support file & folder shortcuts, it seems to me that the best way to handle this is:
- Let our team know that shortcuts will not be migrated
- Provide them with a list of shortcuts
- Have them recreate their shortcuts in OneDrive after the migration.
Your thoughts?
Joshua:
The reason why its not supported is because of the special characters. Or at least most of them are because of this. Microsoft does not support special characters in folder structure. We can discuss this more in depth in the meeting here shortly and come up with a game plan.
kms:
Looking a bit deeper, our problem items seem to be where the shortcut name itself is fine, i.e., no special characters, but in the path that contains the shortcut, the name of one of the folders contains special characters ..
For example: Marketing / Website / *2024 rebrand / system data and faq / shortcut1, shortcut2, shortcut3
kms:
- Need specifics re characters allowed, in folder and separately, files.
- Can fix by removing special characters or shortcuts. TBD.
- Approach ...
- kms:
- Set up test folders and files with Shortcuts & Special Characters:
- Do a couple of tests. Rename folders.
- Then rescan
- kms:
4/2 reply to the ticket:
Hi Joshua,
Per our call yesterday, I have set up two test folders, one containing a special character in the form of an asterisk in the name, the other without. And within these folders both regular files and shortcut files.
The two folders are in Google Shared drives / Operations / RH_IT.Information Technology and are named as follows:
“* GTMM Test Folder with asterisk”
“GTMM Test Folder”
Please re-run your Migration Tool scan, maybe against only the Operations drive to keep the focus narrow if that will help.
It will be interesting to see the scan results and which items fail along with the Failure Reasons. Thanks
4/2 - Joshua:
Here are the results for the tests you are trying. I am attaching them in.
4/2 - kms:
From this small test it seems to me that only the shortcuts failed the migration scan.
But to be sure I am going to create additional folders and files that incorporate more unsupported characters.
Per Restrictions and limitations in OneDrive and SharePoint the following characters are not supported in file and folder names in OneDrive:
" * : < > ? / |
Also, leading and trailing spaces in file or folder names also aren't allowed.
I will let you know when I am ready for another test scan.
4/4 - kms:
Hi Joshua,
Please re-run the Migration Tool scan against Shared drives / Operations / RH_IT.Information Technology
Within the “* GTMM Test Folder with asterisk” and "GTMM Test Folder" I have created several more test folders and files with various combinations of special characters and shortcuts.
Please share the scan results when you have them.
Objective is to be sure we know exactly what will not be migrated. At this point it seems to be shortcuts.
Thanks.
4/4 - Joshua: Attached you will find the new Scan results.
Refer Google My Drive / Google to Microsoft Migration / Scan 4-4-24.xlsx
kms summary during 4/8 call - seems to be any and all shortcuts. Only.
4/9 - Joshua:
With this in place and the discussion we had, I believe since it is the shortcuts only that are having issues, and will be skipped ultimately in the migration, I am going to move this over to resolved. As discussed the shortcuts will no longer be valid on the 365 side, and as long as user expectation is set, knowing that they will disappear we will mitigate anything dealing with permissions that may arise, after the data pull over to Microsoft. Any issues with me moving this over to resolved?
All good.
Smartsheet updated.
Documentation updated.
RH_240410_GTMM - Shortcuts that will not be migrated
RH_240410_Google To Microsoft Migration - Impacts and Changes