After initially choosing to use Google Workspace in your work environment, you’ve now decided to switch to Microsoft 365. This article explains how to migrate from Google to Microsoft 365 using a combination of Cloudiway products.
Features of the Cloudiway tools
Cloudiway provides a single solution for all the steps of your migration:
- user and group provisioning;
- Google Drive to OneDrive migration;
- Google Site to SharePoint Online migration; and,
- mail migration including contacts and calendars performed over the IMAP protocol: free IMAP solutions are subject to Google throttling limitations and cannot migrate contacts and calendars; and,
- coexistence solutions (mail routing, calendar free/busy, address book synchronization).
Benefits of the Cloudiway tools
- no storage of your mail, files, or site data, so no security risk (migration takes place in memory only: we store only a unique ID per mail, file, or site to ensure its migration status can be monitored);
- secure, encrypted data transfer with no loss;
- fast data throughput: Cloudiway deals with source and target throttling automatically;
- no interruption to the day-to-day running of your business; and,
- migration monitoring tools and logs are available throughout the migration.
Label migration: Labels are converted to folders. This article explains how Cloudiway does the conversion.
Delta passes: You can perform several passes. This allows you, for example, to migrate all your data during a few days or a few weeks and perform a final delta pass over the last weekend.
Migration between dates: You can also migrate mails created after a given date (for instance, the last 6 months) or mails between two dates. This allows you to migrate the x last months of mails from your users and then migrate older mails after you go live.
Archives: Cloudiway supports the migration to Office 365 archives: this allows you to migrate mails older than xx months to the Office 365 archives to prevent downloading the entire mailbox to the Outlook OST files.
Room and equipment migration: The platform includes a tool to recreate and migrate Google rooms and equipment to Office 365 resources.
Coexistence during calendar migration, rooms reservation, and calendar migration: During the calendar migration, the links between users and rooms calendars are preserved. Therefore, an organizer who has created an appointment and reserved a room can still cancel or update the appointment after the migration (see below for more information).
Batch migration: You can create a batch of users to arrange your migration into batches (VIPs, weekly, etc.)
- Google Drives are migrated to OneDrive
- Permissions are preserved
- The “Shared with me” view in OneDrive is updated: users can see the list of docs shared with them
- The platform provides an online tool that creates an administrator account that has access to all your users’ OneDrive accounts.
- No need to collect the passwords of your users
- Delta passes supported
- Batch migration: You can create a batch of users to arrange your migration into batches (VIPs, weekly, etc.)
Performance and scalability Cloudiway supports large cloud migrations and on-premises migrations. The on-demand migration engine is able to allocate the capacity of migration that you need to migrate the volume of data of your choice in the time slot that you have allocated for your migration. For instance, during a recent large migration, we migrated 15 Tb in three weeks, with an average migration of 600 GB/day. If our partner had needed to perform the migration in eight days instead of 20, we would have doubled the capacity of migration that we had allocated.
There are several limitations that you must be aware of when you’re performing a migration from G Suite to Office 365. Google Limitation: Google limits the amount of data that you can read in each user’s mailbox to between 2.5 and 3.5 GB every 18-24 hours. Cloudiway is aware of this limitation and automatically stops migrating mailboxes after it has migrated up to the limit. The migration automatically restarts 18 hours later, picking up where it left off. If you have large mailboxes (more than 25 GB), you should be aware of this limitation. 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 (500 GB to 1TB per day).
Cutover (‘one-shot’ or ‘big bang’) migration vs coexistence
A cutover migration is a strategy where all users are switched over at the same time. For example, all users are migrated over a weekend in a single migration pass. This strategy is the simplest and fastest to implement. If you have a lot of users, your migration might take more than a couple of days, so coexistence might be an option. Coexistence is where both systems will be live for some time. You will use a mechanism based on forwarders to ensure that migrated and non-migrated users will be able to communicate with each other throughout the migration process (learn more about coexistence).
Imagine that you have 50% of your users already migrated to Microsoft 365 and 50% still in Google Workspace. A collaborator, Bob, sets up a physical meeting or an online meeting. Some problems arise:
- Which collaborative solution will Bob use for sharing his screen? Lync for migrated users or Google + for non-migrated users?
- What booking system will Bob use to book a room?
- Where will Bob store the meeting minutes? In Google Drive or in OneDrive?
To avoid having to find solutions to these questions, it’s better to switch all users over at the same time.