#Preparation

#1. Identify the object types for migration

Before the migration, you need to identify the scope of objects to be migrated. Currently Fly supports Users and Security groups (with email disabled). Refer to Supported and Unsupported List for details.

#2. Create source and destination connections

Refer to Create a Connection to connect Fly to your source and destination Microsoft Entra ID.

App profile authentication methods are supported to connect to your Entra ID, you can choose to use Fly for Entra ID app profile or custom app profile as the authentication method. Ensure all required permissions are granted, refer to Required Permissions for Entra ID Migration for details.

#3. Design the migration policy

A Microsoft Entra ID migration policy allows you to configure the attribute mappings, conflict resolution for properties only (overwrite or skip), and other options for Microsoft Entra ID migration. Refer to Create a Migration Policy for details.

Note the following:

• Migration policies apply only to full migration jobs.

• Post-migration jobs are not controlled by the policy.

• Conflict resolution settings (overwrite and skip) affect only user and group property fields (such as DisplayName, Department, etc.).

• By default, all types of data (roles, licenses, managers, sponsors, and group memberships) will be merged into the destination. This means Fly will preserve existing values in the destination and add new entries from the source without removing or overwriting any data.