#Migration Execution

#1. Create a migration project

Navigate to Fly > Projects and create a new Microsoft Entra ID migration project. Refer to Create a Project for details.

#2. Configure migration mappings

There are different ways to create migration mappings:

• Use the Auto map method to generate mappings automatically based on the selected domain.

• Import mappings in bulk via Excel template.

• Manually create mappings.

#3. Perform regular full migrations

You can run a full migration job to migrate the objects based on your configured migration policy. Full migration jobs support the migration of properties, group memberships, roles, and license assignments. Refer to Run Migrations to Migrate Objects for details.

#4. Perform post-migration actions

After the migrations, you can also perform the following action:

• Migrate object managers – To migrate the managers/sponsors of the selected objects. This action is only available in post-migration jobs and is not part of full migration jobs.

• Migrate group membership – To migrate the membership of the selected groups based on the attribute mapping rules defined in the migration policy.

  NOTE

  This action will be partially included in a full migration job if Add membership to the destination Microsoft Entra ID groups option is enabled in the migration policy.

• Assign Microsoft license – To assign the Microsoft licenses to the destination users based on the source user’s license assignments. Ensure that the licenses exist and are not fully consumed in the destination.

  NOTE

  This action will be partially included in a full migration job if Assign Microsoft licenses to the destination users option is enabled in the migration policy.

• Unblock user sign-in – To unblock sign-in for all mapped users.

Note that jobs for post-migration actions can be run independently on the Project Mappings page in Fly, and these jobs are not affected by the migration policy.

#5. Validate migration results

• Check the migration reports for each mapping’s result and validate the migrated properties, roles, memberships, and licenses.

• The job report includes the following:

  • Details of property updates

  • User metadata (manager and sponsor)

  • Role assignments

  • License assignments

  • Group membership

• If the mapping failed or finished with exceptions, you can check the comment for the mapping in the mapping report.

• The following are some common errors you may encounter during migration:

  • Error: Objects cannot be found.

  • Reason: The source and destination objects in the mappings configured in the project do not exist.

  • Solution: Check the source and destination data to ensure the objects exist, or update the mappings.

  • Error: The Microsoft license cannot be found in the destination/no Microsoft license is available in the destination.

  • Reason: The assigned license is not available in the destination, or the license assigned to the source cannot be found in the destination.

  • Solution:

    • If license is not required for migration, you can ignore the error or disable the Assign Microsoft licenses to the destination users option in the migration policy.

    • If license is required for migration, ensure the same license exists in the destination based on the source user’s license assignments, and the sufficient licenses are available.

  NOTE

  Additional errors may occur depending on the migration. You can navigate to Fly > Projects > Projects mappings to view the mapping reports and refer to the error comment column for details. Or you can generate and download a migration report for the mapping to check the error details.

  The migration report includes user attributes, group attributes, and mapping summary. You can use the filter on the Project Mapping page to filter for failed jobs, allowing you to re-run the jobs or perform further analysis.

#6. Finalize and clean up

• Export the final reports and archive the mappings.

• (Optional) Remove completed mappings