AvePoint Docs
Graph API
My support tickets
Graph API
My support tickets
English

    Home > Perform Exchange On-Premises Migrations > Run Migrations to Migrate Objects

    Export to PDF

    Run Migrations to Migrate Objects

    When your Exchange On-Premises mappings within a migration project are ready for migrations, you can run migrations for the mappings to migrate objects.

    Refer to the following steps to run migrations for mappings:

    1. Click Projects in the left pane to access the Projects page, and click the project name of the project you want to run.

    2. On the Project mappings page, select one or multiple mappings for which you want to run migrations.

    3. Click Migration, and select Full migration to migrate all objects of the source mailboxes if you run migrations for the mappings the first time.

      In the Full migration panel, you can view whether your purchased mailbox licenses are sufficient for migrations. If the available mailbox licenses are sufficient, Sufficient subscription is displayed in the panel; if the available mailbox licenses are insufficient, there is an Insufficient subscription warning in the panel.

      You can also configure a migration schedule in the panel to run the migration at a specific time.

    4. Click Run to run the migration. If you have configured a migration schedule, the migration will run based on your configured time; if you do not configure a migration schedule, the migration will run immediately.

    If you have run a full migration for the mappings before, you can also select to run an incremental migration or retry error objects for the mappings.

    - **Incremental migration** – Migrate newly created or modified source objects since the last migration, and error and warning objects in previous migrations to the destination. - **Retry** **error** **objects** – Only migrate the error objects in previous migrations to the destination. - > ***Note**: You can run this job for a migration job that is finished with exceptions to retry the error objects. If the migration job is failed, you need to rerun a full or incremental migration job.

    After the migration of mappings starts, if you want to stop the migration, you can select the mappings and click Stop, then the migration of the selected mappings will be stopped. If you run another migration for the stopped mappings, the migration will start from the beginning.

    You can also change the migration schedule of a mapping by clicking the run at [time] link in the Stage column of the mapping; Or change the migration schedule of mappings in bulk by selecting the mappings that have migration schedules, clicking Migration, and clicking Change schedule. In the right panel, select a new schedule to run the mapping based on the new schedule, or select No schedule to stop the migration of the mapping. Click Save to save your updates.

    During the whole migration process, we do not recommend you change the mailbox folder structure. For example, rename, delete, or move source mailbox folders. If you want to change the mailbox folder structure, there are some notes that need your attention:

    - Before you run an additional full migration job for the project that has run a full migration job, note the following issues: - If you rename or move source mailbox folders, Fly will create new mailbox folders in the destination, and all data in the source mailbox folders will be migrated to the new mailbox folders. The previously migrated mailbox folders in the destination will not be deleted. This will cause duplicate data in the destination. - If you delete source mailbox folders, the previously migrated mailbox folders in the destination will not be deleted synchronously. - Before you run incremental migration jobs, note the following issues: - If you rename or move mailbox folders, Fly will create new mailbox folders in the destination, and only the newly created or modified data in the source mailbox folders will be migrated to the new mailbox folders. - If you delete source mailbox folders, the previously migrated mailbox folders in the destination will not be deleted synchronously.