Migration software

CloudM Migrate

Suggested in 5 of our migration playbooks, mainly for Google Workspace. Here is what it handles, how it treats key settings, and other tools for the same jobs.

Third-party toolBy CloudM5 playbooks10 limits handled

What it handles

The limits of the built-in tools that CloudM Migrate gets around, as covered in our playbooks.

Google shared drives to SharePoint and Teams

  • Rebuild membership as groups before the first passMaps Google Workspace groups to Microsoft 365, where Google Groups can become Microsoft 365 Groups, and moves shared drives to SharePoint.
  • Migration Manager: permissions land correctly only when each Google group maps to a Microsoft 365 group with the same members.Maps Google groups to Microsoft 365, where they can become Microsoft 365 Groups, and moves shared drives to SharePoint.

Google Workspace to Google Workspace migration (mergers guide)

  • Know that the data import tool moves email onlyMoves mail, Drive, shared drives, Groups, Calendar, resource calendars, Chat and Spaces between Google Workspace tenants.
  • Budget servers and time for Google Workspace MigrateOffers a CloudM-hosted option for smaller projects, with self-hosted kept for larger migrations that need dedicated infrastructure.
  • Create groups before migrating group-shared contentLists Groups as a migration item between tenants and advises moving Groups before Drive data so group sharing resolves.
  • Google Workspace Migrate runs on Windows servers you build: a platform server, two database servers and at least one node server.Offers a CloudM-hosted option for smaller projects, with self-hosted kept for larger migrations.
  • Google Workspace Migrate does not create groups, so sharing to groups is lost if they do not exist yet.Lists Groups as a migration item and advises moving Groups before Drive data so group sharing resolves.
  • Data import moves email only, up to 1,000 users per import. Drive, shared drives and Calendar need another tool.Moves mail, Drive, shared drives, Groups, Calendar, resource calendars, Chat and Spaces between tenants.

Google Workspace to Microsoft 365 migration

  • Room bookings and shared calendars need their own planMoves users, groups and resources into Microsoft 365 as part of a planned migration, with Gmail, contacts and Google Calendar data going to Exchange Online.
  • Exchange Google migration: room bookings, shared calendars, event colours and vacation replies do not move, so room calendars arrive empty.Moves users, groups and resources into Microsoft 365, with Gmail, contacts and Google Calendar going to Exchange Online.

How it handles key settings

From the settings checklists in our playbooks: what CloudM Migrate carries across.

SettingHow it handles itPlaybook
File versions"Migrate previous document versions" offers 5, 10, 15, 25 or All, major versions only. Changing the number between delta runs replaces documents at the destination.Google Drive to OneDrive migration with Migration Manager
Created and modified dates and authorsNot stated in CloudM's documentation: test it in your pilot.Google Drive to OneDrive migration with Migration Manager
Top-up copies (delta passes)Not stated in CloudM's documentation: test it in your pilot.Google Drive to OneDrive migration with Migration Manager
Groups and membershipMaps Google groups to Microsoft 365, where they can become Microsoft 365 Groups, and moves shared drives to SharePoint.Google shared drives to SharePoint and Teams
File versions"Migrate previous document versions" covers My Drive and shared drives, with 5, 10, 15, 25 or All, major versions only.Google shared drives to SharePoint and Teams
Created and modified dates and authorsNot stated in CloudM's documentation: test it in your pilot.Google shared drives to SharePoint and Teams
Copy or Domain TransferCopies mail, Drive, shared drives, Groups, Calendar, resource calendars, Chat and Spaces between Google Workspace accounts.Google Workspace to Google Workspace migration (mergers guide)
Which tool moves whatOffers a CloudM-hosted option for smaller projects, with self-hosted kept for larger migrations.Google Workspace to Google Workspace migration (mergers guide)
File versions (revisions)Not stated in CloudM's documentation: test it in your pilot.Google Workspace to Google Workspace migration (mergers guide)
Sharing permissions and commentsAdvises moving Groups before Drive data so group sharing resolves.Google Workspace to Google Workspace migration (mergers guide)
Modified dates and authorsNot stated in CloudM's documentation: test it in your pilot.Google Workspace to Google Workspace migration (mergers guide)
What is not movedLists Chat and Spaces among the items it moves between accounts.Google Workspace to Google Workspace migration (mergers guide)
Calendars and roomsLists Calendar and resource calendars among the items it moves.Google Workspace to Google Workspace migration (mergers guide)
GroupsLists Groups as a migration item between accounts.Google Workspace to Google Workspace migration (mergers guide)
What mail content movesMoves users, groups and resources into Microsoft 365, with Gmail, contacts and Google Calendar going to Exchange Online.Google Workspace to Microsoft 365 migration
File versions"Migrate previous document versions" offers 5, 10, 15, 25 or All, major versions only. Changing the number between delta runs replaces documents at the destination.Google Workspace to Microsoft 365 migration
Permissions and user mapping for filesMaps Google groups to Microsoft 365, where they can become Microsoft 365 Groups.Google Workspace to Microsoft 365 migration
Created and modified dates and authorsNot stated in CloudM's documentation: test it in your pilot.Google Workspace to Microsoft 365 migration
Top-up copies (delta passes)Not stated in CloudM's documentation: test it in your pilot.Google Workspace to Microsoft 365 migration
File versionsNot stated in CloudM's documentation: test it in your pilot.Microsoft 365 to Google Workspace migration

Tools for the same jobs

Other tools our playbooks suggest for the same migrations.

We write these notes from the vendor documentation cited in each playbook. Tools cannot pay to be included or to change them. Check the vendor's current documentation and terms before you buy.