Overview:
SharePoint Online Sites migration projects are complex, customized projects. They cannot be performed on-demand in the self-service portal. These projects require Cloudiway product licenses combined with Consulting Services. The minimum timeline to start a SharePoint Online Sites migration project is two weeks. Please contact your Sales Manager for more details.
This guide is aimed at experienced system administrators who are capable of connecting to remote systems and using a variety of administration tools.
1.1. What is migrated
You will find the list of what can be migrated on the product page: Google Sites and SharePoint migration.
Regarding the limitations, you’ll find further information here, please don’t hesitate to contact us if you have any concerns.
1.2. Performance & Security
For more information about security, please refer to this article.
For more information about migration performance, please refer to this article.
1.3. License Management
Cloudiway platform automatically assigns the licenses, for more details regarding the license management, check out this page.
1.4. Delta Passes
Delta migration is a Cloudiway functionality that allows you to migrate incrementally. Changes are migrated during delta passes. Deletions are not propagated.
1.5. Support
Although we provide support for our own products, we do not provide support for third-party products such as PowerShell nor SharePoint administration.
If you are concerned you might have any difficulty completing these steps, please consider a solution with our consulting team, contact us. This will ensure a fast, cost-effective, and stress-free implementation.
2.1. How it works
Migration uses a mix of Graph APIs and CSOM calls. Therefore it requires to configure specific permissions at the source and at the target to execute Graph and CSOM calls.
2.2. Mapping Table
In SharePoint Online, there are permissions and metadata (createdby, modifiedby, etc.) that contain email addresses. During the migration, these addresses must be converted into target accounts.
To achieve this, Cloudiway uses a mapping table to perform the conversion.
Important: the mapping table must be exhaustive, any missing email address will not be converted, and would end up with loss of file permissions and metadata. Cloudiway automatically populates this mapping table when source users are discovered by Get List functionality from Mail or File sections. However, make sure if the mapping table was populated automatically that you are not missing any email address.
2.3. Source Prerequisites
2.3.1 Create a source Office 365 service account
First, we recommend creating an account dedicated to the migration, that can be deleted once the migration is completed.
2.3.2. Source Azure Active Directory Application
Graph APIs calls are performed through an Azure Active Directory Application which is granted specific permissions.You can either create an Azure Active Directory Application manually or let the platform create one for you.
Please consult how to create the Azure Active Directory Application and associated permissions.
2.4. Target Prerequisites
2.4.1 Create a target Office 365 service account
We recommend creating an account dedicated to the migration, that can be deleted once the migration is completed.
Cloudiway automatically creates the Site collections and subsites, therefore they don’t have to exist prior to the migration. If they already exist, they will be used and data appended to them.
2.4.2. Target Azure Active Directory Application
Graph APIs calls are performed through an Azure Active Directory Application which is granted specific permissions.
You can either create an Azure Active Directory Application manually or let the platform create one for you.
Please consult how to create the Azure Active Directory Application and associated permissions.
To facilitate the SharePoint Site migration, the Cloudiway platform needs to be able to communicate with both your source and target domains. To do this, Cloudiway uses connectors. You will need to set up a connector for each source tenant and each target tenant. Please refer to this page to configure your connectors.
For large projects, it’s possible to create multiple connectors that will be used in parallel. Please contact Cloudiway consulting services if you need to set up this configuration.
Note: to test the migration, you can use a Trial License, please consult this article to assign a Trial License.
To perform the Site migration, navigate to Sites > Site List
You have 3 different ways to fill the list:
4.1.1. Option 1: Get Sites
The Get Sites entry under the MIGRATION menu connects to the source and retrieves the full list of Site collections and subsites.
Select the connector you want to connect, click on GET.
Note: you can monitor the progress of this task in the Global Logs.
Once the job is completed, the list displays all the sites. Next, you need to assign a target connector to all the entries.
Select the entries, click on MANAGE, then Assign Target.
Select the connector, click on Assign.
4.1.2. Option 2: CSV file import
If you have a CSV file of all your sites, you can upload the file to Cloudiway.
Click on MANAGE, Import, select the CSV File, the Source and Target Connectors, then click Upload.
4.1.3. Option 3: Create an entry manually
Many of our first-time customers create a single Site for testing purposes.
Click on MANAGE, Create.
Click on OK.
Add a Prefix to the Target?
You can add a Prefix to the Target Site Name and Target URL.
In the Site List, check one or multiple objects, go to MANAGE then click on the “Add Prefix” button.
Enter the Prefix in the pop-up then SAVE.
At this point, you are ready to migrate.
You can review the settings in Global Settings.
Migration of Permissions: Disable it if you want to migrate the Site without permissions.
Migration of TermStore: Disable to improve performances if you are not using TermStore.
The audit is optional and purely informative. It consumes the Cloudiway license. You do not have to run it, unless you wish to see how many files and folders you have in the source site.
This feature reports information about the Source Site:
To Audit a Site, in Site List, select it and click on MIGRATION, Audit.
The pre-processing tool creates the Site at the target if it doesn’t already exist.
What does the pre-processing tool in detail?
At the target:
To pre-process a Site, in Site List, select it and click on MIGRATION, Pre-Processing.
The Site is now ready to be migrated.
Custom script needs to be allowed in the target site.
Note: The next commands should be run on PowerShell version 5
Please follow the below steps:
Install-Module -Name Microsoft.Online.SharePoint.PowerShell
Connect-SPOService -Url <SharePointOnlineAdministrationUrl>
Set-SPOSite <SiteURL> -DenyAddAndCustomizePages 0
Please consult: https://docs.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script
Before starting the migration, you must run the pre-processing (see step above) of the Site.
To start the migration, in Site List, select it and click on MIGRATION, Start.
This will schedule the migration. The migration will start as soon as there is a free spot on the platform.
You can monitor your migration by clicking on the Site in the list.
Cloudiway provides an extensive knowledge base with many resources, including common error messages, video guides, and downloads.
Please visit the knowledgebase here: https://help.cloudiway.com/
