AvePoint Learn
Request article
Contact support
Request article
Contact support
English

Home > Before You Begin

Export to PDF

Before You Begin

Subscription and Licensing Information

If you are in the trial subscription, you can migrate up to 3 objects per workload. Data migration limit is up to 15 GB for these 3 objects except for Power Platform migration.

To migrate additional data for your workloads, purchase user-based or object-based subscriptions according to your migration requirements.

  • For Exchange Online to Exchange Online / Microsoft 365 Groups to Microsoft 365 Groups / Microsoft Teams to Microsoft Teams / Microsoft Teams Chat to Microsoft Teams Chat / SharePoint Online to SharePoint Online / OneDrive to OneDrive migrations, you can purchase subscriptions of users. The Subscription and Licensing Information shows how AvePoint charges for users, and you can contact AvePoint Support to know more.

    If the number of your Microsoft 365 users with assigned licenses exceeds the number of your purchased user seats, Fly will convert to the object-based subscription to continue the migration. For example, all migrated Exchange Online mailboxes will be counted as consumed objects.

  • For Exchange Online Public Folder Migrations, you can purchase subscriptions of users or capacity (GB).

  • For Exchange On-Premises migrations, you can purchase subscriptions of objects (mailboxes).

  • For Power Platform migrations, you can purchase subscriptions of objects (Power Apps / Power Automate flows).

  • For Gmail / Google Drive migrations, you can purchase subscriptions of users. The Subscription and Licensing Information shows how AvePoint charges for users, and you can contact AvePoint Support to know more.

  • For Active Directory and Microsoft Entra ID migrations, you can purchase subscriptions of users.

  • You can purchase global object subscription to do migrations for all workloads.

    NOTE

    If you purchase the subscription of workloads and global objects, the migration will consume the subscription of workloads first.

    NOTE

    You can only purchase global object subscription for Microsoft 365 to Google workspace migrations:

    • Exchange Online to Gmail

    • Microsoft 365 Groups to Google Groups

    • Microsoft Teams to Google Chat Space

    • Microsoft Teams Chat to Google Chat Space

    • OneDrive to Google Drive

    • SharePoint Online to Google Drive

    Each mailbox / group / team / Teams chat user / OneDrive / SharePoint site collection will consume 1 object.

The number of mappings that can be run concurrently depends on your subscription type (annual subscription or non-annual subscription). Refer to the following instructions for details.

There are some notes that require your attention:

  • If a tenant has both non-annual and annual subscriptions, the annual takes precedence over the non-annual.

  • For workspaces of the User type in COP, Fly will count the PODs based on the workspace with the highest user count.

  • Active Directory/Microsoft Entra ID user license SKU purchases are assigned dedicated PODs, separate from those used for mailbox/content migrations. For details on Active Directory and Microsoft Entra ID migrations, refer to the For Active Directory and Microsoft Entra ID Migrations section.

For annual subscription, refer to the following table. There are some notes that require your attention:

  • Mailbox in the table below refers to the Exchange Online, Exchange On-Premises, and Gmail workspaces.

  • Content in the table below refers to the Microsoft Teams, Microsoft 365 Groups, SharePoint Online, OneDrive, Microsoft Teams Chat, and Power Platform workspaces.

  • Mailboxes that are associated with content workspaces (Microsoft Teams and Microsoft 365 Groups) will be consumed by the mailbox PODs quota.

  • Pool licenses are also considered as annual subscriptions. (If their licenses are still active, then they qualify for this scale based on the amount of licenses they assign to the customers tenant. Ignore the amount of time left before pool expiration.)

TierPODsComment
Tier 1 (0 - 999 users, or 0 - 2999 global objects)250 mailbox PODs
Tier 1 (0 - 999 users, or 0 - 2999 global objects)50 content PODs
Tier 2 (1000 - 4999 users, or 3000 - 14999 global objects)300 mailbox PODs
Tier 2 (1000 - 4999 users, or 3000 - 14999 global objects)65 content PODs
Tier 3 (5000 to 14999 users, or 15000 - 44999 global objects)350 mailbox PODs*Note: Errors may occur when running over 300 concurrent mappings that use Exchange PowerShell functions, as this exceeds the maximum number of concurrent requests allowed per tenant. For detailed information on specific circumstances that require the use of Exchange PowerShell, refer to Working with Exchange PowerShell.
Tier 3 (5000 to 14999 users, or 15000 - 44999 global objects)80 content PODs
Tier 4 (15000 - 49999 users, or 45000 - 149999 global objects)400 mailbox PODs*Note: Errors may occur when running over 300 concurrent mappings that use Exchange PowerShell functions, as this exceeds the maximum number of concurrent requests allowed per tenant. For detailed information on specific circumstances that require the use of Exchange PowerShell, refer to Working with Exchange PowerShell.
Tier 4 (15000 - 49999 users, or 45000 - 149999 global objects)95 content PODs
Tier 5 (50000 and above, 150000, or more global objects)450 mailbox PODs*Note: Errors may occur when running over 300 concurrent mappings that use Exchange PowerShell functions, as this exceeds the maximum number of concurrent requests allowed per tenant. For detailed information on specific circumstances that require the use of Exchange PowerShell, refer to Working with Exchange PowerShell.
Tier 5 (50000 and above, 150000, or more global objects)110 content PODs

For non-annual (less than 10 months) subscription, refer to the following table. Note that PODs for non-annual subscriptions applies to all workspaces.

TierPODs
Tier 1 (0 - 199 users, or 0 - 599 global objects)20 PODs
Tier 2 (200 - 499 users, 600 - 1499 global objects)30 PODs
Tier 3 (500 - 999 users, 1500 - 2999 global objects)40 PODs
Tier 4 (1000 users and above, 3000 or more global objects)50 PODs

Taking the following cases as examples:

CaseTier
A partner purchases a monthly distribution marketplace subscription for 15 users.Tier 1 of the non-annual subscription.
A partner purchases an annual distribution marketplace subscription for 150 global objects.Tier 1 of the annual subscription.
A partner purchases directly from AvePoint and does a nine-month co-term for 150 global objects.Tier 1 of the non-annual subscription.
A customer purchases 1000 annual user seats and 2999 annual global objects.Tier 2 of the annual subscription. Note that Fly takes the larger of the two subscriptions to determine the tier.
A partner purchases an annual pool of 500000 global objects.They assign out 500 global objects to Customer 1. (Customer 1: Tier 1 of the annual subscription.)They assign out 20000 global objects to Customer 2. (Customer 2: Tier 3 of the annual subscription.)

Active Directory and Microsoft Entra ID Migrations

You can purchase subscriptions of users for Active Directory and Microsoft Entra ID Migrations.

The number of mappings that can be run concurrently depends on your subscription type (annual subscription or non-annual subscription). Refer to the following instructions for details.

For annual subscription, refer to the following table:

TierPODs
Tier 1 (0 - 999 users)40 PODs
Tier 2 (1000 - 4999 users)60 PODs
Tier 3 (5000 to 14999 users)80 PODs
Tier 4 (15000 - 49999 users)100 PODs
Tier 5 (50000 and above)120 PODs

For non-annual (less than 10 months) subscription, refer to the following table.

TierPODs
Tier 1 (0 - 199 users)10 PODs
Tier 2 (200 - 499 users)20 PODs
Tier 3 (500 - 999 users)30 PODs
Tier 4 (1000 users and above)40 PODs

Aviator

Effective June 15, 2025, Aviator is included for free with all new purchases of the Fly Global Objects and Tenant to Tenant SKUs. This change applies to direct orders only (distribution marketplaces not included). The amount of free Aviator capacity given is determined on a tiered scale.

Included SKUs:

  • Fly Global Objects (AVE_MIG_FLY_AOS_GO)

  • Tenant to Tenant (AVE_MIG_FLY_AOS_T2T)

Aviator Capacity Tiers for Global Objects (AVE_MIG_FLY_AOS_GO):

TierObjects PurchasedAviator Capacity (TB)
11 to 2,9991 TB
23,000 to 14,9993 TB
315,000 to 44,9995 TB
445,000 to 149,9997 TB
5150,000 or more10 TB

Aviator Capacity Tiers for Tenant to Tenant (AVE_MIG_FLY_AOS_T2T):

TierObjects PurchasedAviator Capacity (TB)
11 to 9991 TB
21,000 to 4,9993 TB
35,000 to 14,9995 TB
415,000 to 49,9997 TB
550,000 or more10 TB

Stand-Alone Aviator SKU

In addition to being bundled with Fly migration SKUs, AvePoint Aviator can also be purchased as a stand-alone SKU. This option is ideal for organizations that are focused solely on content management and restructuring, without undertaking a migration project. This approach does not require the purchase of the Tenant to Tenant or Global Object SKUs.

Add Reserved IP Addresses to Your Trusted List

To ensure AvePoint Online Services and Fly can operate in your environment, the reserved IP addresses must be added to your Microsoft 365 firewall.

If your tenant has an enterprise subscription for Fly, the Tenant Owner and Service Administrators can download a list of reserved IP addresses from AvePoint Online Services. Refer to Download a List of Reserved IP Addresses for details.

NOTE

Apart from adding the IP addresses of Fly, make sure the IP addresses of AvePoint Online Services are also added to the trusted list in your environment.

Use the Quick Start Wizard

When you first log into Fly, the Quick start wizard appears with major migration steps displayed. You can also access the Quick start wizard from the left navigation.

Refer to the following details about the major migration steps:

  1. Tenant connection – To use Fly to perform migrations for your tenants, the Tenant Owner or Service Administrators must connect the tenant to AvePoint Online Services at first. Refer to Connect your tenant to AvePoint Online Services for details.

  2. Migration credentials – The credentials are used to connect to your Microsoft 365 tenant or Google workspace. Clicking Configure will take you to configure the app profile, service account, and/or Microsoft delegated app profile in AvePoint Online Services.

    Refer to Required Permissions to view the supported authentication methods and required permissions for your migration.

  3. Auto discovery – To use Tenant discovery, Auto map, and/or Aviator in Fly, you need to run an Auto discovery in AvePoint Online Services to scan objects to specific containers with the configured app profile or service account.

    Clicking Configure will take you to configure the scan profile in AvePoint Online Services. Refer to Scan Microsoft 365 or Google Objects for details.

  4. Tenant discovery – Tenant discovery can help you understand the object details in your source tenant before the migration. Clicking Run discovery will take you to the Tenant discovery page in Fly. Refer to Tenant Discovery for details.

    NOTE

    Tenant discovery needs to be run after the auto discovery finishes. To report the discovered data, contact your Microsoft 365 global administrator to deselect the Display concealed user, group, and site names in all reports option in Settings > Org Settings > Reports in Microsoft 365 admin center.

  5. Migration projects – The migration project allows you to better organize and migrate multiple objects all in one. Clicking Create migration project will take you to the Create projects page in Fly. Refer to the Fly Migration Process Guide for details about the involved migration processes and the user guide about how to create projects.

Scan Microsoft 365 or Google Objects

To use the following functions in Fly, you need to run an Auto Discovery in AvePoint Online Services to scan Microsoft 365 or Google objects to specific containers.

  • Tenant discovery – Scan and report the object count, object type, object size, and other details in each workspace of source Microsoft 365 or Google tenants.

  • Auto map – Automatically map source and destination objects based on names for the following migration types.

    • Exchange Online Migration

    • Microsoft 365 Groups Migration

    • Microsoft Teams Migration

    • Microsoft Teams Chat Migration

    • OneDrive Migration

    • Power Platform Migration

    • SharePoint Online Migration

    • Gmail Migration

    • Google Drive Migration

      NOTE

      If you use the Add or Import method to map source and destination objects when creating migration mappings, you can ignore this. The objects can be directly retrieved via the app profile or service account used in the source or destination connection.

    • Aviator – Copy or merge Microsoft 365 Groups, Teams, SharePoint site collections, or OneDrive sites across tenants.

To scan and add Microsoft 365 or Google objects, navigate to AvePoint Online Services > Auto Discovery > Scan profiles and configure scan profiles. For details, refer to Manage Auto Discovery. After the scan process is finished, the detected objects are available in Fly.

Required Permissions

Fly supports the service account profile and app profile authentication methods to retrieve objects from source or destination workspaces.

When using the app profile authentication method to connect to the Online workspaces, there are specific objects/settings that cannot be migrated by this method. You can refer to Fly Support Lists for each migration type to determine if using the app profile method will satisfy your data migration requirements.

To view the supported authentication methods of each migration type and permissions required by the authentication methods, refer to the corresponding section below.