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.
1.1. Supplementary tools
Cloudiway has developed a number of tools to enable seamless migration for the most intricate migrations. Our supplementary tools include:
1.1.1. Automatic provisioning
Cloudiway offer an automatic account provisioning tool. It synchronizes your Active Directory infrastructure with Office 365 and lets you manage your cloud users from your local Active Directory. It synchronizes users, groups and contacts, and also provides real time password synchronization. It supports multi-domain and multi-forest environments and avoids costly directory consolidation projects. Visit www.cloudiway.com for more information, or contact us.
1.1.2. File migration
During site migration, files embedded on or attached to web pages can be migrated with the Cloudiway file migration tool. Make sure you select the right license for your requirement. The file migration platform is also useful for businesses planning to migrate entirely from one remote system to another, such as Google Apps for Work, Microsoft OneDrive or SharePoint. Visit cloudiway.com for more information, or contact us.
To discuss supplementary tools and licensing, please get in touch with your existing Cloudiway contact, or via email@example.com
We take your privacy and security seriously at Cloudiway, and we have invested significant effort into making our platform and your data secure. Cloudiway provides a cloud-based application hosted in Windows Azure. It means that the software and data are centrally hosted and accessed by clients using a web browser and internet connection. In addition, Cloudiway’s SaaS benefits from Windows Azure’s certifications, ensuring security of the infrastructure, network and physical security layers of the Cloudiway cloud.
For total assurance, Cloudiway provides auditing tools, secure, authenticated data connections and a logging system. More specifically:
*For the delta pass mechanism, a reference ID of each data migration is stored in internal caches (SQL databases) with the date of modification. This ensures that no data is duplicated, and for efficiency, only the changes are propagated. We automatically delete inactive records after 90 days, or upon request.
In addition, because the Cloudiway platform needs credentials to connect to the source and the target, you define connectors to connect to them and enter credentials that will be used for the connection. These credentials are stored encrypted using AES 256.
For complete peace of mind, we recommend that you create a temporary migration account during your migration which you can delete at the completion of your project.
Cloudiway’s software platform has been designed and developed to support large migrations.
The on-demand migration engine is able to allocate the migration capacity that you need to migrate the volume of data of your choice in the time slot that you have allocated for your migration.
Please bear in mind that Office 365 can heavily throttle users. When you perform too many calls, Office 365 begins throttling and decreases the number of calls that can be performed each minute, thus reducing the migration throughput. Cloudiway constantly attempts to work at the maximum capacity allowed by Office 365 and is able to achieve excellent throughput.
4.1 What can be migrated?
When migrating from Google Sites to SharePoint, the following site items can be migrated:
4.2. Migration limitations
Google Sites and SharePoint site collections are set up differently, which makes it difficult for some elements to be migrated successfully.
Google Site pages are organized in a tree hierarchy where pages can contain sub-pages (such as http://www.mysite.com/mainpage/subpage. SharePoint stores each site’s pages in a flat library; to avoid page naming conflicts, Cloudiway migration platform renames Google Sites pages as ‘mainpage-subpage’.
Google Site menu depth is unlimited, whereas, by default, SharePoint is limited to two nodes. By default, Google Site menus with a depth of more than two nodes cannot be migrated.
The Google menu control can contain text. SharePoint menus cannot, so text content in the Google Site menu control is lost.
The site logo is not currently migrated, but a solution is being developed so that it can be in future. Please get in touch if you would like this functionality.
Google gadgets that do not have web part equivalents are not migrated.
Announcements are migrated to SharePoint discussion boards. However, discussion boards do not support attachments. To work around this, announcement attachments are migrated in a SharePoint library with the post title.
Automatically generated menus (created with the ‘Automatically organize my navigation’ option within the ‘Configure navigation’ pop-up of any menu) are not migrated. However, if these are constructed manually, they can be migrated.
Important note before migrating Googles Sites: Embedded Drives
Google Drives can be embedded in Google Sites making the migration of files, permissions and the assignment of an owner more complex than for standard migration.
By default, Cloudiway migration platform will not migrate the embedded Google Drives. However, there is a way to migrate embedded Google Drives by following this process:
Prior to the Google Site migration, it is mandatory to run a file audit of all the Google Drives. This is in order to build the list of Drive documents and respective owners.
Follow the below process:
1) Perform an audit of the Google Drives with the File migration tool (requires Cloudiway file migration licenses for each Google Drive)
2) Migrate the Google Sites
3) Migrate the Google Drives
Read more details about how to migrate Embedded Google Drives in this article.
We strongly recommend you use Cloudiway’s file migration tool to in conjunction with the site migration tool to achieve the best migration results possible. Please see our other documentation for more details about how these two products interact.
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 firstname.lastname@example.org. This will ensure a fast, cost-effective 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.||https://kb.cloudiway.com|
|G Suite API|
|Required to enable APIs and to download the G Suite private key.|
This can be accessed via your
Google Admin account.
|The Admin console is where|
administrators manage Google
services for people in an
admin role for
|Account with admin role that|
bypasses SSO and is able to
preferably with the format:
Used for migration of permissions
|We recommend you create an account|
with admin access, especially for migration.
After all, migrations are complete, simply
delete this admin account.
5.2. G Suite — Set permissions for the service account
https://apps-apis.google.com/a/feeds/calendar/resource/#readonly, https://apps-apis.google.com/a/feeds/user/#readonly, https://www.google.com/calendar/feeds/, https://www.googleapis.com/auth/calendar, https://www.googleapis.com/auth/drive.readonly, https://sites.google.com/feeds/
NOTE: 1. Each scope must be separated by a comma.
2. Some scopes require slashes (/) at the end and others don’t: please use the above strings. 3. If you add another scope later, existing scopes will be removed: you need to add the whole list at the same time.
7. Click on the Authorize button
8. You can check that the scopes were successfully registered by looking for the names next to the client ID you paste
9. Now, navigate to Security > API Reference > API Access and ensure that ‘Enable API Access’ is checked.
6.1. Create your G Suite source connector
For Cloudiway to migrate your sites, it 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. Follow the steps below to configure a G Suite source connector.
6.2. Create your SharePoint Online 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 an Office 365 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.
The tool will schedule a call to your domain to return a list of all visible Google Sites. Refreshing the screen will cycle through ‘Get sites scheduled’, ‘Get sites working’ and eventually,’Get sites done’, presuming your source connector is set up correctly.
Once the Get Sites tool has completed, it will return a list of all sites discovered via the source connector’s credentials. The list will appear in the Site List area of the Cloudiway platform. From this list, you can check what is due to be migrated prior to migration, edit the target site and collection, assign licenses and delete any sites that don’t need to be migrated. These actions are explained in the following sections.
You can also download the results in CSV format for your own records or to make editing changes, and then upload the updated CSV file to the Cloudiway platform as your final list of sites to be migrated.
Note: you cannot add new entries to the CSV file: they must exist on the Cloudiway platform already. If you need to add a new site, either re-run the Get Sites (which will add newly-available sites to the existing list) or add a site manually using the steps below.
6.4. Add target site collections
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 specifically target site details. Prior to migration, you will need to create a list of target site collections on the Cloudiway platform and associate them with each source site (and don’t forget to ensure you have created each site collection on your SharePoint remote system too).
6.5. Add a Google Site manually to Cloudiway
You can manually add the details of a Google 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 group you’ve set up especially for that purpose. In this case, adding the group 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 drop-down for Target site collection contains the list of collections you created in section Error! Reference source not found.).
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 email@example.com 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.
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 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. In the following steps, the individual assignment is explained in more detail.
6.7. Import or create a mapping table of user details
In order to migrate access rights for the list of users who have access to each Google Site, a mapping table of users must be defined. A list of mail users is used as a mapping table 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 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, you can upload the file to Cloudiway. The file must have the following fields in the header row:
A sample CSV file is available for download during the steps outlined below. If you perform more than one upload, any user data already uploaded will not be overwritten by following uploads. Therefore, duplicates can occur.
6.7.2. Option 2: Import Users tool
Cloudiway’s Import Users tool helps you to retrieve users from your source tenant. The functionality works via Identity Access Management. The tool requires you to specify any transformation rules you wish to apply. It will then add new users in the Site Migration User List view within the Cloudiway platform.
This is an advanced tool that is best used in partnership with Cloudiway consultants. If you are interested in using this option, please get in touch with your Cloudiway contact.
6.7.3. Option 3: Create a single user
Many of our first-time customers create a single user for testing purposes. This provides a means of watching the migration process without affecting all users. Single users 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. 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 entire knowledge base here (where you can search for keywords or read through topics): https://kb.cloudiway.com
The knowledge base also contains information on how you can ask for further support, should you require it.