#Migration Execution

Based on your source tenant discovery report, you need to prepare a final mapping file to list the mappings of source data and destination location. As you may have a heavy load of content to migrate, we recommend you separate your mappings into multiple waves according to your departments for easy management. Keep communicating with users about the migration status.

#1. Configure projects and mappings in Fly

To configure projects and mappings, refer to Create a Project and Create Migration Mappings for details. Use the mapping file of data to be migrated to configure the migration project.

#2. Perform regular full migrations

Before running the job, we recommend you verify the mappings to ensure that the mappings are available for migration. Refer to Pre-analyze Mappings for details.

Then you can run a full migration job to migrate the objects based on your configured migration policy. Refer to Run Migrations to Migrate Objects for details.

#3. Perform regular incremental migrations

Handle new, updated, and failed data. Refer to Run Migrations to Migrate Objects about how to perform regular incremental migrations.

#4. Validate migration results

After the regular full or incremental migrations, note the following:

• Check the mapping report. If the mapping fails or finishes with exceptions, you can check the error code and comment for the mapping in the Migration error section. You can click the error code to view the details and recommendations of the code in the Troubleshooting Guide, which can assist you in resolving or avoiding the error.

• Check the item count in the destination.

• Check the permission in the destination. If permissions failed to be migrated, you can run a Migrate permissions only migration job.

• New data can be created in the destination.

#5. Set the source site to read only

Before executing the final delta/incremental migration, make sure that no data will be changed or created in the source during the migration to enforce the data consistency.

• To set OneDrive as read only, run the following script using PowerShell:

  #Set Parameters
  
  $AdminCenterURL="https://contoso-admin.sharepoint.com"
  
  $SiteURL = "https://contoso-my.sharepoint.com/personal/admin_contoso_onmicrosoft_com"
  
  #Connect to SharePoint Online
  
  Connect-SPOService -Url $AdminCenterURL -Credential (Get-Credential)
  
  #PowerShell to set onedrive for business site to read only
  
  Set-SPOSite -Identity $SiteURL -LockState ReadOnly

• To unlock the OneDrive, run the following script using PowerShell:

  #Unlock site from read only mode
  
  Set-SPOSite -Identity $SiteURL -LockState Unlock

#6. Perform the final incremental migration for current wave

At the end of the migration project, we recommend you run a final incremental job to ensure all source data are migrated to the destination.

#7. Run migrations for all other waves (optional)

This step is only needed if you have separated the migration projects into multiple waves.