Skip to main content

How is CloudM Migrate licensed? How are licenses consumed?

This document provides the reference for CloudM Migrate licensing, detailing consumption rules, volume-based calculations for shared data, and technical behaviors for specific migration scenarios.


Licensing Fundamentals

CloudM Migrate licensing binds to the destination domain and the specific source-destination platform combination. A license is required for every unique destination entity (user, group, or shared repository). Licenses typically expire one year from issuance.

License Classes

License ClassBest ForConsumption Rule
Google WorkspaceUsers, Shared Drives, and Spaces1 license per user. 1 license per 10GB for Shared Drives.
Microsoft: Mail OnlyEmail-only projects1 license per mailbox.
Microsoft: Unlimited Single UserStandard user migrations1 license per user (Mail, Drive, Calendar, Contacts).
Shared DataSharePoint or Teams1 license per 100GB.

How Licenses are Consumed

A license is consumed when a migration process starts for a specific destination entity. Once bound, unlimited delta passes can be performed at no additional cost.

Identity Tracking

  • User Renames / Domain Switches: If a user is renamed in the destination during a delta phase (e.g., user@domain1.com to user@domain2.com), no additional license is consumed. CloudM tracks the entity via its Backend Object ID.
  • Manual Typos: Running a migration with an incorrect Import Name consumes a license. Correcting the address and running the migration again consumes a second license, as the system identifies a new unique entity.
  • Failed Provisioning: If a migration fails because the destination user does not exist, creating the user and retrying with the same Import Name does not consume an additional license.

Shared Data Licensing

Google Shared Drives

Google Shared Drives utilize a strict volume-based consumption model:

  • Base Consumption: 1 license per Shared Drive (covers up to 10GB of data).
  • Volume Increment: Drives exceeding 10GB consume 1 license per 10GB. For example, migrating a 100GB Shared Drive requires 10 licenses.

Microsoft SharePoint & Teams

SharePoint sites and document libraries are licensed per 100GB increment per destination site. This is a hard cap with no grace buffer.

  • Volume Increment: 1 license per 100GB. Migrating 101GB to a single site consumes 2 licenses.
  • Consolidation Example: Migrating 10 Google Shared Drives (450GB total) into a single SharePoint Site requires 5 licenses (450GB / 100GB, rounded up).
  • Separation Example: Migrating 10 Google Shared Drives into ten separate SharePoint Sites requires a minimum of 10 licenses, regardless of data volume.

Specific Scenarios & Unlicensed Entities

User Consolidation

When merging multiple source accounts into a single destination account, the license follows the destination identity. Consolidating 100 source users into one destination mailbox consumes one license.

Technical Constraint: Consolidating multiple sources to one destination triggers a SQL-level lock to prevent data corruption, causing items to process sequentially. To automate the queue, enable Advanced Settings > Allow Multiple Sources.

Microsoft 365 Exchange Online Archive

Migrating a Primary Mailbox and an Exchange Online Archive (EOA) requires two licenses. Because the primary mailbox and the archive contain separate datasets and require different migration configurations, they act as distinct source platforms.

Unlicensed Entities

The following entities do not consume a license:

  • Google Groups (Source): Exporting the member list does not require a license. Message content extraction is not supported.
  • Resource Calendars: Room and resource calendars migrate free of charge across all platform combinations.
Was this article helpful?
1 out of 2 found this helpful