Pause, cancel, or exit a migration

When you use the data migration service, you can pause, restart, cancel, or exit a migration.

You must be signed in as a super administrator for this task.

To access the Data migration tool in the Admin console:
  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in

  2. From the Admin console Home page, go to Data migration.

    To see Data migration, you might have to click More controls at the bottom.

Pause and restart a migration

To pause and restart a migration:

  1. Do one of the following actions:
    • To pause a migration for all users, leave the boxes next to all users unchecked and click Pause Pause.
    • To pause a migration for certain users, check the box next to the users you want to pause and click Pause Pause.
  2. Select the accounts you would like to resume and click Continue Continue. The data migration service resumes where it left off.

Note: After you stop a migration, the migration can continue for up to 10 minutes before the process stops.

Cancel the migration

If you want to change the migration settings during a migration, you must first cancel the migration.

To cancel a migration for all users, click Settings  More > Exit Migration > Exit.

If you cancel a migration that’s in progress and run the same migration again later, the data migration service starts over and migrates all of the data again. However, your new G Suite email account automatically identifies duplicate messages and eliminates them.

Exit a completed migration

To exit a completed migration, click Settings  More > Exit Migration.

When you exit a migration, a migration report is sent to all super administrators of the domain and the migration role account.

Information about a completed migration is displayed on the Data migration page for 15 days, or until you click Exit Migration. A migration exits automatically after 15 days and if it does, you won't receive a migration report. It’s important to keep track of a migration’s progress so that you don’t miss valuable reporting information.

We recommend that you check a migration's progress every few days and exit the migration if it has successfully completed.

Was this helpful?
How can we improve it?