Skip to main content
Version: 4.52.0

SPO-Migration

This component allows you to migrate to Sharepoint Online (using migration packages) into existing sites. It uses the Sharepoint Migration API. It does this by communicating with Azure Storage and Sharepoint Online to perform the migration. Packages and binaries are uploaded to Azure storage and then the migration is triggered from Sharepoint Online.

In migration mode the component creates two containers (folders) in Azure Storage blob storage, these can be found under Data storage -> Containers, named in Azure Storage as manifest container and source container. When the containers are created the following is being processed in order:

  • manifest container: the manifest files from the package will be uploaded to this container as blobs. Documentation on the manifest files can be found here

  • source container: the files (that will be migrated to Sharepoint Online) on the local file system or MongoDB will be uploaded to this container as blobs.

    Above actions will be performed using the Azure Blob Storage.

  • When all blobs are uploaded into the manifest and source container, the content will be imported to Sharepoint Online from Azure Storage Containers using the Sharepoint Migration API.

Detailed process description

Configuration

Inputs | Outputs


SPO-Migration
Input
Output
Error
00 0 (ilysju47)

Config mode set to Migrate

The component expects a message with the key packagePath when mode is set to Migrate. In this example, the manifest (package) files are located in C://Training.

Example:

{
"packagePath": "C://Training"
}

Config mode set to Retrieve logs

The component expects a message with key manifestContainerName when mode is set to Retrieve logs. In this example, the logs from the migration above are retrieved. By using the azureContainerManifestUri, azureQueueReportUri and migrationJobId from the output of that exampleWhen using provisioned containers make sure to add the encryptionKey as 4th required key.

Example: (using storage account):

{
"azureContainerManifestUri": "manifest-sd233-2flg3-sss21"
}

Example: (using storage account if migrated with setting Encrypt storage account migration data):

{
"azureContainerManifestUri": "manifest-sd233-2flg3-sss21",
"encryptionKey": "key"
}

Example: (using provisioned containers enabled):

{
"azureContainerManifestUri": "manifest-sd233-2flg3-sss21",
"migrationJobId": "22-dfs2fsd-wew34dfs-wds",
"azureQueueReportUri": "https://spodb1am1m038p2.blob.core.windows.net/22-dfs2fsd-wew34dfs-wds",
"encryptionKey": "key"
}

Config mode set to Delete containers

The component expects a message with key containerNames when mode is set to Delete containers. In this example, the manifest and source container created in Azure Storage with the migration from the example above will be deleted. By using the manifestContainerName and sourceContainerName from the output of that example

Provisioned containers are deleted automatically by Sharepoint.

Example:

{
"containerNames": ["manifest-sd233-2flg3-sss21", "source-saf3d-dw3fg-sdf32"]
}