Home > Before You Begin
Export to PDFBefore You Begin
Refer to the sections below for important information on Fly.
Subscription and Licensing Information
If you are in the trial subscription, you can migrate up to 3 objects for your workloads. 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.
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:
For annual subscription, refer to the following table. There are some notes that require your attention:
| Tier | PODs | Comment |
|---|---|---|
| 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.
| ● Tier | ● PODs |
|---|---|
| ● 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:
| Case | Tier |
|---|---|
| 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: 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:
| ● Tier | ● PODs |
|---|---|
| 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.
| ● Tier | ● PODs |
|---|---|
| ● 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:
Aviator Capacity Tiers for Global Objects (AVE_MIG_FLY_AOS_GO):
| Tier | Objects Purchased | Aviator Capacity (TB) |
|---|---|---|
| 1 | 1 to 2,999 | 1 TB |
| 2 | 3,000 to 14,999 | 3 TB |
| 3 | 15,000 to 44,999 | 5 TB |
| 4 | 45,000 to 149,999 | 7 TB |
| 5 | 150,000 or more | 10 TB |
Aviator Capacity Tiers for Tenant to Tenant (AVE_MIG_FLY_AOS_T2T):
| Tier | Objects Purchased | Aviator Capacity (TB) |
|---|---|---|
| 1 | 1 to 999 | 1 TB |
| 2 | 1,000 to 4,999 | 3 TB |
| 3 | 5,000 to 14,999 | 5 TB |
| 4 | 15,000 to 49,999 | 7 TB |
| 5 | 50,000 or more | 10 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 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:
-
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 for details.
-
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.
-
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.
-
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 .
-
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 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.
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 . 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, the migration can be less throttled. However, there are specific objects/settings that cannot be migrated by this method. You can refer to 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.