Use the Copy as File Share Directory action to copy SharePoint sites, document libraries and documents into a File Share. This allows you to move content back and forth between SharePoint and the File Share environment.
You can:
·copy SharePoint sites and document libraries into a File Share connection as a directory (folder) while maintaining the existing sub-structure
OR
·copy SharePoint documents as documents under a selected File Share node.
To copy a SharePoint site or document library as a File Share Directory
1.In Explorer View, select the SharePoint site or document library that you want to migrate.
2.Right-click and choose Copy Site or Copy List .
3.Select the target File Share directory.
4.Right-click and choose Paste Site > As Directory or Paste List > As Directory.
5.Continue with Configuring Copying Options.
To copy SharePoint documents into a File Share Directory:
1.In Explorer View, select the SharePoint document library that contains documents to be migrated.
2.Switch to Items View.
3.Select the documents to be copied.
4.Right-click and choose Copy Selected Documents.
5.Select the target File Share directory.
6.Right-click and choose Paste Documents.
Continue with Configuring Copying Options.
The File Share Migration Using CSV feature allows you to perform bulk migrations from file system folders to a corresponding SharePoint target using a single CSV file. This feature allows folders to be migrated as a document library, streamlining the migration process.
This feature supports both SharePoint Online and SharePoint on premises targets.
Key Features:
·Facilitates bulk migration in File Share Edition using a single CSV file.
·Allows migration of folders as a document library to a SharePoint target.
·Supports hierarchical SharePoint nodes by allowing you to connect a parent folder in Content Matrix and include its child folders in the CSV file. This means that any subfolders under the connected parent folder will be recognized during migration.
Note:
·Metadata entries are directly stored and cleared from the current job source.
Prerequisites:
·Connections in Content Matrix
oValid file system source and SharePoint target connections exist in Content Matrix. Any missing connections or connections that are in an error state will invalidate the migration scenario for that CSV entry.
oThis feature supports validating sites and subsites in the CSV using different connection types, including Tenant, Farm, Web Application, Site Collection, and Subsite connections.
·CSV Validations
oIf duplicate source entries in the imported CSV file will invalidate the associated connection combination.
oMultiple CSV entries with same source and target will be consolidated into a single entry.
oClear messages will be displayed if there are missing details in the CSV.
oSeparate CSV files need to be created for on premise targets and SharePoint Online targets. Both connection types cannot be used simultaneously in a single CSV.
Preparing the CSV File
Before starting the migration, prepare a CSV file in the following format. Enter the path to each source folder in the Source field and the URL of the SharePoint target site in the Target field.
Source,Target
C:\Folder1,http://target:5000/website/teams/Sub1
C:\Folder2,http://target:5000/website/teams/Sub2
C:\Folder3,http://target:5000/website/teams/Sub3
To perform a migration using CSV:
1.In the Content Matrix ribbon toolbar, select Connection > Migrate from CSV.
2.In the Migrate Content Using CSV dialog, click the browse button to select the CSV file. Once selected, all rows from the CSV file will be displayed, along with a Status column that indicates whether each CSV row is valid for migration.
NoteS:
·If the source and target specified in a CSV row are connected in Content Matrix, or their corresponding Tenant, Farm, or Web Application connections are established, the status will be marked Valid. If any required connections are missing or have an error status, the status will be marked Invalid.
·If the target in the first row is a SharePoint Online site, all connected SharePoint Online site connections related to the migration will be marked Valid.
·Similarly, if the target in the first row is an on-premises site, all connected on-premises site connections will be marked Valid.
·If the user is creating parent connections in the application and using child nodes in the CSV file, the connections may take some time to load.
3.Select Proceed.
4.In the Paste Folder Settings dialog, select the appropriate copying options as needed. For more information, see Configuring Copying Options.
5.Once all the settings are configured, you can proceed with one of the following options:
a)To start the migration job now, select Run. All migration combinations with a valid status will be initiated. Once successfully finished, their status will change to Completed.
a)To save the configuration and run the migration later, select Save. For example, you may want to export the PowerShell script and run the migration later from the PowerShell console.
Note: As with other migration jobs, you can run the job from the Content Matrix Console or using PowerShell. The only difference is how the migration is logged:
·Running the migration from the UI creates a single migration job in the job source, which will contain logs for all migrations combinations included in the CSV file.
·Running the migration via PowerShell creates separate migration jobs in the job source, each corresponding to a different target location.
The Paste [Object] dialog provides a tabbed interface that enables you to configure a migration according to your specifications. Available tabs will vary based on the type of migration that you initiated.
If you chose to Migrate Folders as SharePoint Sites or Document Libraries,complete the Folder options tab as described below.
To configure Folder Options:
1.If you want to Migrate sub-folders, make sure this box is checked.
NOTE: If you uncheck this box, only the folder from which you initiated the migration will be copied.
2.For Replace invalid characters in file names with: select the character that you want to use as a substitute for any characters disallowed by SharePoint.
3.Select the action that you want Content Matrix to take If a folder with the same name already exists on the target. Use the information in the following table for guidance.
|
If you to ... |
Select ... |
|---|---|
|
prevent Content Matrix from copying a folder from the source if a folder with the same name already exists on the target (in the same hierarchy structure) |
Do not copy the folder. |
|
allow Content Matrix to overwrite any existing folders on that target, if they have the same name as a folder that is being migrated |
Overwrite the existing folder. |
|
allow Content Matrix to migrate files and other folders directly into a folder that already exists on the target, if a folder with the same name is being migrated from the source. |
Use the existing folder. |
|
allow Content Matrix to migrate a folder from the source, even if a folder with the same name already exists on the target. |
Copy the folder with a unique filename. NOTE: If you select this option, the folder from the source will be created on the target using a unique name (typically the original file name with "_1" appended). For example, if a folder named "Marketing Programs" is migrated from the source, and a folder with the same name exists on the target, then a new folder will be created on the target called "Marketing Programs_1", and the contents of the folder will be migrated into this new folder. |
4.Select the Content type options to use when setting the content type for any folders that are migrated to SharePoint. Use the information in the following table for guidance.
|
If you want to ... |
Then ... |
|---|---|
|
use the default SharePoint content type for any migrated folders |
select Use default content type (No folder metadata). |
|
specify the content type that should be associated with folders when migrating content. |
·Select Use custom content type AND ·Either: §select an available content type from the drop-down OR §click [Edit Field Mappings] and specify your own target content type using the procedure for Mapping Field Types. |
5.If you want to migrate to a SharePoint Online target using the Import Pipeline, check the Use Import Pipeline box and either:
·keep the default option - SPO Provided Azure Containers
OR
·select Azure private containers (if configured), and enter the Azure Storage Connection String in the following format:
DefaultEndpointsProtocol=https;AccountName={your account name};AccountKey={your account key}
NOTE: When using Azure private containers, you also have the option to Encrypt Azure jobs. (When using SPO Provided Azure Containers, jobs are always encrypted.)
