FLY 3.9 Release Notes

New Features and Improvements

  1. Users can now configure the Control database and Migration database for FLY during installation.
        Figure 1: The database configuration page.
  1. When MS SQL is configured as the database type for installing FLY, users can change the Control database, and/or Migration database to another database or update the password for connecting to the databases using the FLY Manager Configuration Tool after the installation.
        Figure 2: The FLY Manager Configuration Tool.
  1. Users can now add a scan profile to automatically scan and register SharePoint site collections or OneDrive for Business as connections. Users can also configure a schedule for the scan.
        Figure 3: The Scan Profile page.
  1. If you select the Default Azure AD App type when creating an app profile, FLY will create an app for your tenant using the Global Administrator credentials you provide.
  2. FLY now supports performing Slack high speed migrations.
  3. FLY now supports performing actions on migration plans/jobs by executing the commands via FLY APIs.
  4. Users can now define the list, library, folder as the source/destination node when configuring the mapping file for SharePoint migrations using the import mode.
  5. Users can now configure if they want to migrate subsites in the source site collection by configuring the Migrate Subsites setting in the SharePoint Migration migration policy. If the setting is not selected, only the top-level site will be migrated to the destination.
  6. FLY now supports migrating the source e-mails that were received before a specific time to the archived mailbox/folder.
  7. FLY now supports migrating in-place archived mailboxes/folders in Exchange migrations.
  8. Users can now configure whether to migrate mailbox rules and whether to migrate recoverable item folders in Exchange migrations.
  9. FLY now supports migrating the owner and members of source distribution groups in Exchange migrations.
  10. Users can now configure if they want to only migrate the Documents library of the source objects in SharePoint/Group/Teams migrations.
  11. The following improvements are made when users rerun the SharePoint/file system/Google Drive migration:
  • For a failed migration, FLY will resume it from the failed point.
  • For a stopped migration, FLY will resume it.
  • For a Finished with Exception migration, users can choose to only migrate the failed objects from the last migration job, or migrate the failed, new, or modified objects. For a Finished with Exception Exchange migration, FLY will migrate the failed, new, or modified objects automatically.