Use CSV files with the data migration service

To make sure legacy information is correctly mapped to your new G Suite account using the data migration service, use a comma-separated values (CSV) file so that you don't have to manually enter usernames and calendar resources every time you migrate data. A CSV file also allows you to migrate multiple users and resources at the same time.

What CSV files are required

If you’re migrating multiple users or contacts, you’ll need only one file—the migration CSV file. 

If you’re migrating calendar events for multiple users, you might need 2 CSV files—one to map the users and resources and one to specify what users and resources you want to migrate. It’s easiest if you use only one file (the identity mapping) and upload it twice. However, if you have a large migration, you might want to make the second file different so that only a group of users migrate at that time.

Use an identity mapping CSV file

An identity mapping CSV file is used to ensure that your legacy usernames and calendar resources map correctly to their new G Suite usernames and calendar resources. Map all users on your account in this file even if they aren’t being migrated at this point, because they could be participants in other users’ meetings. 

Tip: You can download a list of your users from your Google Admin console. For details, see Download a list of users.

When creating the CSV file, make sure that you:

  • Use the following format for usernames: G-Suite-email-address,Legacy-email-address
  • For calendar resources use: G-Suite-calendar-resource,Legacy-calendar-resource 
  • Use the full email address (including domain).
  • Don't include headers or use commas to separate the fields. Put each entry on a separate row. 

Examples

joe@gsuitedomain.com,joe@olddomain.com

gsuitedomain.com_37r2903631.resource.calendar.google.com,boardroom-1@olddomain.com

Use a migration CSV file

A migration CSV file specifies which calendar resources or users’ data you want to migrate in this migration. When creating the CSV file, make sure that you:

  • Use the following format for usernames: G Suite-email-address,Legacy-email-address.

    Note: If you’re migrating from Microsoft® Exchange or Office 365™ you don’t need to include the password field.

  • For calendar resources, use: G-Suite-calendar-resource,Legacy-calendar-resource.
  • Use the full email address (including domain).
  • Only include the legacy email address if it differs from the G Suite email address.
  • Don't include headers or use commas to separate the fields. Put each entry on a separate row. 

Examples

  • Migrating email from an IMAP server to G Suite—joe@gsuitedomain.com,joe@olddomain.com,password
  • Migrating calendar resources from Exchange Web Services (EWS)—gsuitedomain.com_37r2903631.resource.calendar.google.com,boardroom-1@olddomain.com
  • Migrating email from EWS to G Suite (same domain name)—raj@yourdomain.com

Where do I find the G Suite calendar resource email address?

  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 Apps.
  3. Click G Suiteand thenCalendarand thenResources.
  4. Click the resource name.

    The email address is listed under Resource email.

Was this helpful?
How can we improve it?