Cloudiway’s site migration solution helps businesses perform elaborate technical migrations through a simple SaaS interface. As a result, site migrations require no additional software installation or overhead, and migrations can be performed securely and quickly.
The Cloudiway platform is flexible enough to support all types of migration paths. Your migration strategy will depend on your business setup, type and size. Whichever migration path you choose, Cloudiway provides all the essential features such as site content, permissions, site layout and URLs (included rewrites where required). Delta passes are also available, which means you can complete a migration to capture any changes since the initial pass.
The solution migrates from SharePoint Online to SharePoint Online.
On Premises scenario are not supported.
1.1. Supplementary tools
Cloudiway has developed a number of tools to enable seamless migration for the most intricate migrations. Our supplementary tools include:
For more information about security, please refer to this article.
For more information about migration performance, please refer to this article.
4.1. What can be migrated?
When migrating from SharePoint to SharePoint, the following site items can be migrated:
4.2. Migration limitations
SharePoint to SharePoint migrations are relatively straightforward, but some elements cannot currently be migrated or are migrated in a specific way, and will need to be identified and addressed as part of any remediation work.
Links between site collection cannot be migrated (converted) and may get broken during the migration, in particular if you have reorganized your sites and moved some sites to new site collections with different names at the target.
Versioning enables you to store, track, and restore items in a list and files in a library as they are changed. During migration, only the current version is migrated.
SharePoint workflows are pre-programmed mini-applications that streamline and automate a wide variety of business processes — from collecting signatures, feedback, or approvals for a plan or document, to tracking the current status of a routine procedure. They are not migrated by the SharePoint site migration tool.
Typically, a SharePoint solution is deployed to a SharePoint server by using a solution package (.wsp) file. Microsoft SharePoint Foundation has its own system for installing solutions on a SharePoint Foundation farm that is different from other Windows applications and platforms. There is no MSI file or ClickOnce technology involved. The system provides a way to bundle all the components of a SharePoint Foundation extension into a single new file, which is called a solution package. Solution packages are neither migrated nor activated by the SharePoint site migration tool.
Alerts are an email and Short Message Service (SMS) notification service in SharePoint Foundation. Users can create rules to receive notifications of changes to list items (item-level alerts), documents, lists (list-level alerts), or document libraries. Alerts are not migrated by the SharePoint site migration tool yet.
You can apply composed looks to your SharePoint sites. Composed looks are out-of-the-box themes that are included in SharePoint 2013 and SharePoint Online. Additional themes are not migrated. The SharePoint site migration tool only migrates composed looks natively existing in any SharePoint sites.
A web part is a modular unit of information that forms the basic building block of a Web Part Page. They enable you to customize a SharePoint page to display content or business data from many sources on the same page. You can also use web parts to display information from external sources, such as RSS feeds or news sites. There are many web parts included with SharePoint Foundation. You can also buy web parts from other companies, or, if you want to try your hand at writing code, you can develop your own. The site migration tool will only migrate web parts included with SharePoint Foundation. Custom or third-party web parts are not migrated.
SharePoint Add-ins are self-contained extensions of SharePoint websites that you create, and that run without custom code on the SharePoint server. (Microsoft) Apps are not transfered during Cloudiway SharePoint migration.
Permissions on individual libraries are not migrated. (However, Permissions at site level and file and folder level are migrated).
Views are migrated. However the default view cannot be currently set.
Delta migration is a Cloudiway functionality that allows you to migrate incrementally. This functionality is currently used for page and document migrations only. This means that pages and documents will never be duplicated at the target.
For lists, the delta pass mechanism is not efficient, it deletes the list items and pushes them again. This is not efficient if a list has more than 10 000 entries.
This guide is aimed at experienced system administrators who are capable of connecting to remote systems and using a variety of administration tools.
Although we provide support for our own products, we do not provide support for third party products such as PowerShell or server administration of Google or Microsoft products.
If you are concerned you might have any difficulty completing these steps, please consider a solution with our consulting team, contactable via email@example.com. This will ensure a fast, costeffective and stress-free implementation.
5.1. Before you start
Before you start, you will need to ensure you have the details outlined in the following table.
|Cloudiway login||Stores details and provides communication
between the systems you already use.
|Our extensive knowledge base is always
accessible, with videos, troubleshooting
tools, samples and more.
|Sharepoint Tenant administrator account||Account with Sharepoint Tenant administrator that bypasses SSO
and is able to authenticate using
preferably with the format:
|We recommend you create an
account with admin access
especially for migration. After all
migrations are complete, simply
delete this admin account.
5.2. Pre-migration checklist
To ensure successful migration, we also recommend that you follow the checklist
Prepare any mapping tables for users and groups in CSV format, ready to upload later on.
If you let the platform create the site collection, the migration account must be SharePoint administrator.
Ensure the source and target migration accounts have admin access to all site collections.
5.3. Permissions Pre-requisites
Our Site Migration product come with a pre-processing task, that is able to create the site collections in your target tenant. To achieve that, migration uses a mix of Graph Apis and CSOM calls.
Graph APIS require application permissions on groups, users and sites.
For CSOM access, the migration account must be SharePoint administrator.
6.1. Create your source connector
To facilitate site migration, the Cloudiway platform needs to be able to communicate with both your source and target domains. To do this, Cloudiway uses connectors, which are configured on apps.cloudiway.com. You will need to set up a connector for each source tenant and each target tenant.
You can choose to manually set up your connectors, or you can use the simpler process of the wizard. The steps below will walk you through the manual process.
6.2. Create your target connector
With the source connector now configured on the Cloudiway platform, it’s time to create and configure the target connector. Follow the steps below to configure a SharePoint Online target connector.
6.3. Import sites with the Get Sites command
The Cloudiway platform provides a tool called Get Sites which returns a list of all sites from the domain you added to the source connector (using the admin credentials you supplied in the source connector). This is a useful tool which provides you with a complete picture of sites to be migrated.
You should therefore run this tool prior to site migration to avoid having to manually enter details of each site: any syntax errors or spelling mistakes will prevent Cloudiway from finding the intended site. This is by far the simplest method of listing the sites to be migrated.
6.4. Import sites with the Get Sites command
The Get Sites tool will have captured as many source site details as possible for you, to help avoid spelling mistakes or missed sites. However, it cannot specify target site details.
6.5. Add a SharePoint site manually to Cloudiway
You can manually add the details of a SharePoint site to your list on the Cloudiway platform. Due to the possibility of typos, we recommend you only use this option if it’s impossible to rerun the Get Sites command. You might wish to test migration on a test site you’ve set up especially for that purpose. In this case, adding the site manually might be preferable to using Get Sites. The straightforward process is outlined in the following steps.
You can manually change each site’s name at the target, as well as choose whether to migrate directly to the root site of the collection or somewhere else (the dropdown for Target site collection contains the list of collections you created in section 6.4).
Toggling the Migrate to the root site of the collection option will change the relative URL, and you can use the target fields to create the correct relative URL to suit your needs.
Use the Target site relative URL field to preview the final site URL (relative to the target domain) each time you make a change to the other target fields.
6.6. Complete target site details
With all sources and target site collections added, you can pinpoint specific target locations within site collections to obtain your preferred site structure at the target. You can also delete sites that don’t need migration, configure individual sites and assign licenses.
Before any migration can start, you must assign a license for each source site. You can purchase site licenses these within the Cloudiway platform (or contact firstname.lastname@example.org for further information), and these will be displayed on the License dropdown after purchase.
Logically, you need to add a target connector from the Target dropdown list before migration can begin, as well assign any target site collection locations to your source sites prior to migration.
Remember, you can manually change each site’s name at the target, as well as choose whether to migrate directly to the root site of the collection. You can use the Target site relative URL field to preview the final site URL (relative to the target domain) each time you make a change to the target fields.
Note: You can assign a target connector and collection by entering into the details of the site and editing it (See above).
You can also assign a target to multiple sites from the Action bar at the bottom of the screen. To blanket assign a connector, go to the Manage menu and select Assign Targets (this will apply to all sub-sites).
To blanket assign a collection, go to the Set Collection menu and select a collection from the list.
To blanket assign a license, go to the Manage menu and select Assign Licenses (this will apply to all sub-sites).
6.7. Import or create a mapping table of user and group details
In order to migrate access rights for the list of users who have access to each source site, a mapping table of users must be defined. Office 365 security groups rights can also be migrated using a mapping table. A list of mail users is used as mapping tables as it defines who has access to the different sites. It is also used to migrate metadata for files and folders.
You can upload a user or group list via CSV, use Cloudiway’s automated Import Users tool, or manually add each user on the Cloudiway platform.
6.7.1. Option 1: CSV import
If you have a CSV file of all your site users and another one for groups, you can upload the files to Cloudiway. The files must have the following fields in the header row:
User CSV: FirstName;LastName;SourceEmail;TargetEmail
Group CSV: Name;SourceEmail;TargetEmail
If you perform more than one upload, any CSV data already uploaded will not be overwritten by following uploads. Therefore, duplicates can occur. Sample CSV files are available to download during the steps below.
6.7.2. Option 2: Create a single user or group
Many of our first-time customers create a single user and/or group for testing purposes. This provides a means of watching the migration process without affecting all users. Single users and groups can also be created for migrations affecting just a few users.
6.8. Perform an audit
Cloudiway provides an auditing tool which will help identify potential errors prior to migration, such as unfound sites or broken items. We recommend that you run this audit as many times as required prior to migrating to ensure your migration list is fully prepared and ready.
6.9. Perform preprocessing
Cloudiway provides a preprocessing tool that will set automatically all the required permissions at the source and at the target and provision the groups and teams at the target.
What does the preprocessing tool?
At the target:
At the end of the preprocessing, the status of the migration is set to “Not Started”. The sites are now ready to be migrated.
6.10. Activate and monitor your migration
Now that you have performed all the pre-migration steps within your tenants and within Cloudiway, you’re ready to migrate. We recommend you run a test migration on a single site first to check that your configuration produces the outcome you expect.
To start your migration, select the site you wish to migrate and click on the Start button. Your batch will be scheduled and will begin as soon as resources are available.
Cloudiway provides an extensive knowledge base with many resources, including common error messages, video guides and downloads.
Please visit the site migration knowledge base area here:
Please visit the entire knowledge base here (where you can search for keywords or read through topics): http://kb.cloudiway.com/
The knowledge base also contains information on how you can ask for further support, should you require it.