How to prepare MetaShare for migration

Before migrating documents to MetaShare using the Migration Manager, the recommendation is to:

1. Create a workspace configuration and give it a good name, e.g. “Archive”. Do not define any “Term set that defines suggested templates”:
   
2. Do not select any content type in the workspace configuration’s submenu “Document content types”:
   
3. In the workspace configuration’s submenu “Document columns”, select the columns you want to show in the document view, e.g.:
   
4. In the workspace configuration’s submenu “Document filters”, select the filters you want to show in archive workspaces, e.g.:
   
5. Create the workspaces that you need, for the migration, based on the newly created workspace configuration.
6. If the workspaces will have more than 5 000 documents, you might want to index the columns that you will be presenting in these workspaces (document filters and/or document columns), so that these columns can be filterable and sortable. These are the columns that we recommend to index, where the “Modified” column is indexed by default:
   
7. In order to restrict the users from adding or editing documents in the migrated workspaces, for each of the migrated workspaces, logged in as a site collection administrator, do the following:
   1. Open the workspace in SharePoint.
   2. Click on the “Settings” icon on the top right-hand side of the page and then “Site permissions”:
      
   3. Click on the “Advanced permissions settings” link:
      
   4. In the Ribbon, click on the “Permission levels” link:
      
   5. Click on the “Contribute” permission level:
      
   6. Now you have two options:
      1. Easy option:
         Restrict the permission of the built-in permission level “Contribute”. Use this option when migrating using the “Preserve file share or SharePoint permissions” option, as all users that have “Write” permissions on folders/documents in the source location, will get “Contribute” permissions on them in SharePoint. Unfortunately the users that have “Full control” permission on the source location will get “Full control” permissions on them in SharePoint and there is no way to modify this permission level, as it is read-only, so either you change the permission on the folders on the file server prior to the migration else these users will be able to modify these documents in the archive workspaces.
         1. Un-check these two list permissions:
            
         2. On the bottom of the form, click on the “Submit” button:
            
      2. More complex option:
         Create a new permission level and apply the new permission to the Member’s group. Use this option when migrating without the “Preserve file share or SharePoint permissions” option, as no unique permissions will automatically be set during the migration. The advantage of choosing this option is that you are not modifying any of the built-in permission levels.
         1. On the bottom of the form, click on the “Copy Permission Level” button:
            
         2. Give the new permission level a meaningful name, e.g. “Read and delete” and a suitable description:
            
         3. Un-check these two list permissions:
            
         4. On the bottom of the form, click on the “Create” button:
            
         5. Go back to Site permissions (step 4c above) and mark the site’s members’ group:
            
         6. In the Ribbon, click on the “Edit User Permissions” link:
            
         7. Unselect the earlier permission level and select the newly created permission level and click on the “OK” button:
            
8. Now you can commence your document migration to the migrated workspaces that you have created. A recommendation for you is to first do a test-migration to a test workspace, in order to:
   1. Analyze the file-migration speed. You should probably expect approximately 30 GB/hour, but the speed depends on your internet bandwidth and the performance of the computer where your agents are running. Based on the calculated speed, you will also be able to plan how long time the final migration will take. This information can be found in the “SummaryReport.csv” log-file, under these columns:”Total GB”, “Duration” and “GB/hour”.
   2. Analyze the migration error log-file (FailureSummaryReport.csv) to see if any of the documents could not be migrated.
   3. If you select the “Azure Active Directory lookup” option, verify that the documents’ “Created by” and “Modified by” columns are linked to known users. If they are broken you probably need to create and define a “User Mapping file“.