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.