Migration software
AvePoint Fly
Suggested in 9 of our migration playbooks, mainly for Microsoft 365 and Files and collaboration. Here is what it handles, how it treats key settings, and other tools for the same jobs.
What does AvePoint Fly handle?
The limits of the built-in tools that AvePoint Fly gets around, as covered in our playbooks.
Microsoft 365 Groups and Planner tenant-to-tenant migration
- Decide about group conversations and calendars per groupLists Microsoft 365 Group mailboxes among the mailbox types it migrates across tenants.
- Microsoft documents no way to move group conversations or the group calendar.Lists Microsoft 365 Group mailboxes among the mailbox types it migrates across tenants.
Microsoft 365 tenant-to-tenant migration
- Confirm you can buy the migration licences before you set a dateMoves SharePoint, Exchange, OneDrive, Teams and Groups across Microsoft 365 tenants, keeping permissions and versions.
- Set expectations on what users loseMoves Teams, including Teams chat, along with SharePoint, OneDrive and Groups across Microsoft 365 tenants.
- Built-in moves fail without their add-on licence. Mailbox and OneDrive moves need Cross Tenant User Data Migration, one per user, which resellers sell. Microsoft's built-in site move needs Cross-Tenant Shared Data Migration, sold only under an Enterprise Agreement.Moves SharePoint, Exchange, OneDrive, Teams and Groups across tenants, keeping permissions and versions.
- Microsoft's built-in tools do not move Teams channel conversations, Planner or Forms.Moves Teams, including Teams chat, with SharePoint, OneDrive and Groups.
Power Apps and Power Automate tenant-to-tenant migration
- The default environment cannot use the environment moveMigrates Power Apps and Power Automate flows between environments and tenants, with an inventory scan and automatic mapping before the migration.
- Environment move: default, developer, trial and Teams environments cannot use it.Migrates Power Apps and Power Automate flows between environments and tenants, with an inventory scan and automatic mapping. Confirm default environment support with a pilot.
Cross-tenant SharePoint migration
- Treat Teams sites as two jobsMoves Teams, including Teams chat, along with SharePoint, OneDrive and Groups across Microsoft 365 tenants.
- Built-in move: Teams sites move files only. Channels, conversations and the team itself must be rebuilt.Moves Teams, including Teams chat, with SharePoint, OneDrive and Groups.
SharePoint Server to SharePoint Online migration guide
- Check how your source version is supported by SPMTLists Microsoft SharePoint Server 2010, 2013, 2016, 2019 and SE as supported migration sources.
- Microsoft's SPMT pages do not list Subscription Edition as a source.Lists SharePoint Server 2010, 2013, 2016, 2019 and SE as supported sources.
Slack to Microsoft Teams migration
- Tell people that DMs and group chats stay in SlackLists Slack, including Slack direct messages, as a supported migration source.
- Microsoft's tool does not move direct messages or group chats on any plan.Lists Slack, including Slack direct messages, as a supported migration source.
How does AvePoint Fly handle key settings?
From the settings checklists in our playbooks: what AvePoint Fly carries across.
| Setting | How it handles it | Playbook |
|---|---|---|
| File versions | AvePoint says Fly preserves versions and lists Box and Dropbox as sources. Whether that covers versions from Box and Dropbox: not stated in AvePoint's documentation: test it in your pilot. | Dropbox, Box and Egnyte to SharePoint and OneDrive migration |
| Permissions and role mapping | AvePoint says Fly preserves permissions with mapping. | Dropbox, Box and Egnyte to SharePoint and OneDrive migration |
| Created and modified dates and authors | AvePoint says Fly migrates metadata. Which date and author fields: not stated in AvePoint's documentation: test it in your pilot. | Dropbox, Box and Egnyte to SharePoint and OneDrive migration |
| Permissions (NTFS) | AvePoint says Fly preserves permissions with mapping, and lists file shares as a source. | File server to SharePoint migration |
| Created and modified dates and authors | AvePoint says Fly migrates metadata. Which date and author fields: not stated in AvePoint's documentation: test it in your pilot. | File server to SharePoint migration |
| Group conversations and calendar | Lists Microsoft 365 group mailboxes among the mailbox types it migrates across tenants. | Microsoft 365 Groups and Planner tenant-to-tenant migration |
| User mapping | AvePoint says Fly preserves permissions, with mapping of users and groups. | Microsoft 365 tenant-to-tenant migration |
| Top-up copies (delta passes) | AvePoint says Fly keeps both tenants online and migrates incrementally. | Microsoft 365 tenant-to-tenant migration |
| File versions | AvePoint says Fly preserves versions. Whether you can limit how many: not stated in AvePoint's documentation: test it in your pilot. | Microsoft 365 tenant-to-tenant migration |
| Teams channels, chats and meetings | AvePoint says Fly moves Teams, including Teams chat, across Microsoft 365 tenants. | Microsoft 365 tenant-to-tenant migration |
| File versions | AvePoint says Fly preserves versions. Whether you can limit how many: not stated in AvePoint's documentation: test it in your pilot. | Cross-tenant OneDrive migration |
| Permissions and user mapping | AvePoint says Fly preserves permissions, with mapping of users and groups. | Cross-tenant OneDrive migration |
| Created and modified dates and authors | AvePoint says Fly migrates metadata. Whether that includes original dates and authors: not stated in AvePoint's documentation: test it in your pilot. | Cross-tenant OneDrive migration |
| Recycle bin | Not stated in AvePoint's documentation: test it in your pilot. | Cross-tenant OneDrive migration |
| Which environments can use the environment move | Migrates Power Apps and Power Automate flows between environments and tenants. Default environment support: not stated in AvePoint's documentation: test it in your pilot. | Power Apps and Power Automate tenant-to-tenant migration |
| Canvas apps, custom pages and component libraries | Canvas and model-driven apps: AvePoint's page does not say which app types: test it in your pilot. | Power Apps and Power Automate tenant-to-tenant migration |
| File versions | AvePoint says Fly preserves versions. Whether you can limit how many: not stated in AvePoint's documentation: test it in your pilot. | Cross-tenant SharePoint migration |
| Recycle bin content | Not stated in AvePoint's documentation: test it in your pilot. | Cross-tenant SharePoint migration |
| Created and modified dates and authors | AvePoint says Fly migrates metadata. Whether that includes original dates and authors: not stated in AvePoint's documentation: test it in your pilot. | Cross-tenant SharePoint migration |
| Permissions and user mapping | AvePoint says Fly preserves permissions, with mapping of users and groups. | Cross-tenant SharePoint migration |
| Sharing links | Not stated in AvePoint's documentation: test it in your pilot. | Cross-tenant SharePoint migration |
| Checked-out files | Not stated in AvePoint's documentation: test it in your pilot. | Cross-tenant SharePoint migration |
| Site size and path length | Not stated in AvePoint's documentation: test it in your pilot. | Cross-tenant SharePoint migration |
| Top-up copies (delta passes) | AvePoint says Fly keeps both tenants online and migrates incrementally. | Cross-tenant SharePoint migration |
| Teams channels and conversations | AvePoint says Fly moves Teams, including Teams chat, across Microsoft 365 tenants. | Cross-tenant SharePoint migration |
| Sensitivity labels | AvePoint says Fly preserves sensitivity labels, with mapping. | Cross-tenant SharePoint migration |
| Scheduling and throttling | AvePoint says Fly uses bulk APIs, Azure storage and app tokens to reduce throttling. | Cross-tenant SharePoint migration |
| Source version support | Lists SharePoint Server 2010, 2013, 2016, 2019 and SE as supported sources. | SharePoint Server to SharePoint Online migration guide |
| File versions | AvePoint says Fly preserves versions. Whether you can limit how many: not stated in AvePoint's documentation: test it in your pilot. | SharePoint Server to SharePoint Online migration guide |
| Permissions and inheritance | AvePoint says Fly preserves permissions with mapping. | SharePoint Server to SharePoint Online migration guide |
| Created and modified dates and authors | AvePoint says Fly migrates metadata. Which date and author fields: not stated in AvePoint's documentation: test it in your pilot. | SharePoint Server to SharePoint Online migration guide |
| Checked-out files | Not stated in AvePoint's documentation: test it in your pilot. | SharePoint Server to SharePoint Online migration guide |
| Top-up copies (delta passes) | AvePoint says Fly keeps both environments online and migrates incrementally. | SharePoint Server to SharePoint Online migration guide |
| Throughput and throttling | AvePoint says Fly uses bulk APIs, Azure storage and app tokens to reduce throttling. | SharePoint Server to SharePoint Online migration guide |
| What your Slack plan can export | What it can read on each Slack plan: not stated in AvePoint's documentation: test it in your pilot. | Slack to Microsoft Teams migration |
| Direct messages and group chats | Lists Slack, including Slack direct messages, as a supported migration source. | Slack to Microsoft Teams migration |
Which tools do the same jobs as AvePoint Fly?
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.