This guide is to help you plan a process for moving your network drive content to MS365 cloud storage. We recommend that R-drive content should be moved to either Microsoft Teams FILES OR to a SharePoint Online site.

Before you begin: How about “Notes for choosing files for Migration”?(based on my notes below)

• You can copy files simply by drag and drop from the network drive to the MS365 cloud storage location. This works reasonably well for simple and small file moves. This is before step? Is it more of a note? When I think of Before you begin, I think of steps I need to do or things to check.

• For larger migrations OR when there is a need to retain file metadata such as last edited and last modified information a tool such as SharePoint Migration Tool should be used.

• are there special permissions they need that we should add here?

SharePoint Migration Tool

Microsoft provides the SharePoint Migration Tool (SPMT) for moving files from local drives, network drives, or SharePoint 2016 sites.

• Information on using SPMT can be found here: https://docs.microsoft.com/en-us/sharepointmigration/how-to-use-the-sharepoint-migration-tool#using-the-sharepoint-migration-tool

• The current version of SPMT can be downloaded here: https://spmt.sharepointonline.com/install/default.htm

• You must be a workstation Administrator to install this software on your workstation add to the above section?

  • To copy metadata and content, you must have Full-Control Permissions on both the Source and Destination locations. Metadata is written to system indexes. Add to “Before you begin”?

• A “wired” connection on a Domain joined workstation should be used

Clean-up content

The SharePoint Migration Tool (SPMT) does run a SCAN before migrating content. We recommend that you do this SCAN to catch the following errors:

• Path names length

• Invalid Filenames

• Files that are locked

• Files that are too big (SPMT supports files up to 250 GB)

• Find and remediate problematic files like:

  • leading or trailing space in file or folder name (rename without the space)

  • leading underscore in file or folder names (rename without hyphen)

  • search for and delete or rename (turn on view for Hidden Items in File Explorer first):

    • file:~"*~*.tmp" (starts with ~ and ends in .tmp, probably delete)

    • file:~"*~*.doc" (delete if 162 bytes)

    • file:~"*~*.docx" (delete if 162 bytes)

    • file:*.txt~"*~*" (probably delete if it ends in dot tilde)

    • file:.DS_Store

    • file:desktop.ini

    • file:Thumbs.db

    • file:~"*~*" (delete files starting with ~$, probably less than 200 bytes)

Migrating to Private Channels

When migrating to Private channels in Teams, those channels will not show up if you indicate you are migrating to Teams. For Private channels, you need to indicate you are copying content to SharePoint and get the SharePoint link to the Teams Files location.

Verify Location

• When copying files using a SharePoint URL, it is easy to correctly specify the Files location in the Private channel and accidentally copy things to one level above the Documents folder for a channel. The URL does appear to be where channel however one must remember to specify the Folder for the channel itself.--please check the wording of this sentence. If something appears to be missing after a migration, go to the expected location in SharePoint and look one level higher up.

• When migrating the content from the shared network file shares, give the users advanced notification about when the migration is happening.

• If possible

  • set the network shares to read-only so that the content will not be changing during migration.

  • schedule iterative copies to capture changes if needed.

• NOTE: if users are accessing and creating files during the migration they may create temp and lock-files that will cause an error. How will the error show? Does the user get an alert?

Workstation issues

SPMT doesn't clean up after itself very well so you'll need to occasionally empty the following folders.

• C:\Users\YOURUSERID\AppData\Roaming\Microsoft\MigrationTool\uwaterloo.ca
  and

• C:\Users\YOURUSERID\AppData\Roaming\Microsoft\MigrationToolStorage\uwaterloo.ca

Should this sentence be part of Before you begin? ->The SPMT mirrors files that are being migrated to the local hard disk and copies to Teams from there. That means that if you are migrating 500Gb from a network share to Teams, you need to ensure you have more than 500Gb free on C:

For large migrations, you can go into “View all settings”, under Advanced, you can specify a different “SharePoint Migration Tool working folder”.Why would someone need to go there in a large migration I redirect that to a folder in an 8Tb internal drive on my office machine when I was using SPMT to migrate super large shares. Using large external storage, I did not need to worry about local file space constraints. The largest individual folder I have migrated was about 4Tb – which then had to move to a private channel. This clone took 36 hours to run. Can we reword this to take the “I” out please?

Set Source to Read-only if possible

Once the migration is done, leave the content as read-only on the netapps (On the netapps? have we told them how to do that? do we mean R:drive?) so that users can look at the original folders to confirm that everything has migrated.

Related articles

• Page:
  Outlook for Mac - mailbox delegate access
• Page:
  Eduroam certificate verification
• Page:
  Getting Started with Jira Service Management
• Page:
  Quiz reports
• Page:
  Attempts in Progress