#Run Migrations to Migrate Objects

When your public folder 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 public folders if you run migrations for the mappings the first time.

   In the Full migration panel, you can view whether your purchased user seats/mailboxes are sufficient for migrations. If the available user seats/capacity are sufficient, Sufficient subscription is displayed in the panel; if the available user seats/capacity 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 mapping migration starts, you can stop it at any time by selecting the mappings and clicking Stop. The selected mappings will be paused. If you run the migration again for the stopped mappings, it resumes and continues migrating data.

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.