Pause, cancel, or exit a migration

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

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

Pause, restart, or cancel a migration

Before you begin

To access the Data migration tool in the Google Admin console:

  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  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 Moreand thenPause all migrations.  
    • To pause a migration for certain users, check the box next to the users and click Pause user migration.  
  2. Select the accounts you would like to resume and click Resume user migration. The data migration service resumes where it left off.

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

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 Moreand thenExit migration

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 Moreand thenExit migration

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

Information about a completed migration is displayed on the Data migration page for 15 days, or until you exit the migration. A migration exits automatically after 15 day. If it does, you won't get a migration report.

It’s important to keep track of a migration’s progress so that you don’t miss reporting information. Check a migration's progress every few days and exit the migration if it's successful.

Was this helpful?
How can we improve it?