File Share to Microsoft 365

File Share to Microsoft 365

Before starting your migration project, make sure you have setup the File Share and the Microsoft 365  configuration guides. Ensure that both tenants have passed their connectivity tests with no errors.

The destination for the file share can be a SharePoint document library or a user OneDrive.

The SharePoint Admin URL needs to be populated on the Destination Advanced Options.


  1. Adding File Shares as Migration Items
  2. Execute Migration
  3. File Name Conflicts

Adding File Shares as Migration Items

The auto discovery function within CloudM Migrate does not work for File Shares so each file share need to be added manually.

To add a File Share navigate to Step 3 within CloudM Migrate and select +Add items to migrate. Select Add User and populate the following fields:

  • Export Type: User
  • Import Type: Team Site
  • Export Name: Any value that refers to source such as E:\
  • Import Name: SharePoint Document Library (example: sites/site-name) or OneDrive UPN
  • Given Name \ Item Name: Documents
  • Family Name: SharePoint Site Name
  • Password: N/A
  • Document Path: Full UNC path on source (example: \\hostname\rootfolder\subfolder)

Validate Migrate and Drive are checked and select Save to add the migration line item. Repeat for each file share in scope for migration. The folder structure entered under Document Path will be preserved on the destination unless otherwise specified by having Migration Top Level Folder checked and target folder specified.

Execute Migration

When ready to execute, select the Paper Airplane on the left and select Start to begin the migration. CloudM Migrate will first index the source to validate access to the entire folder structure. Once completed, the folder structure is applied to the SharePoint site. Files are then copied into an Azure container before being surfaced in SharePoint.

File Name Conflicts

If CloudM Migrate moves a file to the destination that already has a file with the same name the migrating file will be renamed with a _ character in the beggining of the file name.

If the file was perviously migrated and has been updated on the source, the Overwrite Files can be enabled to overwrite based on Created Date or Modified Date.

Was this article helpful?
0 out of 0 found this helpful