#Prepare for Migrations

Before performing OneDrive Migrations in Fly, follow the instructions below to prepare for the migration:

1. Build the inventory on your source OneDrive.

   • Number of user accounts

   • Size and structure

   • Other file storage locations

   • Application and workflows

2. Set up Microsoft 365 services and configure your Microsoft 365 subscription.

   • Add and verify the domain

   • Configure application settings

   Refer to for details.

3. Fly does not automatically provision new users in Microsoft 365. Make sure the destination users already exist before the migration.

   There are different ways to add new Microsoft 365 users:

   • Adding users individually. See instructions .

   • Adding users in bulk. See instructions .

   • Adding users via PowerShell. See instructions .

   • Synchronizing users from local Active Directory to Microsoft 365 via Microsoft Entra Sync or Microsoft Entra connect. Refer to for details.

4. Fly can remove source sensitivity labels and apply destination ones to your SharePoint files/sites with a corresponding option selected in the migration policy. Before using this feature, make sure to review the necessary requirements and additional information. Refer to Information about Managing Sensitivity Labels for details.

5. (Optional) Custom script

6. In Microsoft 365, the custom script is not allowed on OneDrive, sites users create themselves, modern team and communication sites, and the root site for your organization. The migration of pages and files will be affected. Refer to for details and to see how to allow custom scripts on these sites.

7. (Optional) Nintex Workflow

   If you want to migrate Nintex workflows to Microsoft 365, make sure the Nintex workflow app has been installed and trusted in a site of your destination tenant. Then when you migrate Nintex workflows to this tenant, Fly can automatically install the Nintex workflow app to other destination sites.

8. Fly does not support creating OneDrive sites in multi-geo tenants. If the destination is a multi-geo tenant, we recommend that you pre-provision all OneDrive sites using the PowerShell: before the migration. An alternative approach is for each user to log into OneDrive to initiate the site collection creation.