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 you don't have to manually specify 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 calendar events for multiple users, you might need 2 CSV files:

  • one to correctly map the users and calendar resources between systems (an identity mapping CSV file)
  • one to specify the users and calendar resources you want to migrate (a migration CSV file)

To migrate everything at once, it’s easiest if you use only one CSV file (the identity mapping) and upload it twice.

However, if you have a large calendar migration, but you don't want to migrate all calendars at once, upload an identity mapping CSV file with all entities that have calendar events. Then, create a migration CSV file so only a subset of users migrate.

Use an identity mapping CSV file

An identity mapping CSV file is used to make sure 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 currently being migrated as they could be participants in other users’ meetings.

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

When creating this CSV file, make sure 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 header rows or use commas to separate the fields. Put each entry on a separate row.

Examples

  • Migrate email—joe@gsuitedomain.com,joe@olddomain.com
  • Migrate calendar resources—gsuitedomain.com_37r2903631.resource.calendar.google.com,boardroom-1@olddomain.com
Use a migration CSV file

A migration CSV file specifies which user data and calendar resources you want to migrate. The migration CSV file actually migrates the information for the entities it describes.

When creating this CSV file, make sure you:

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

    Note: If you’re migrating from Microsoft® Exchange or Exchange Online (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 header rows or use commas to separate the fields. Put each entry on a separate row.

Examples

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

Where do I find a 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. On the Resources page, click a calendar resource name (for example, NYC-14-12-Boardroom-15) to view its details.

    The G Suite calendar resource email address is listed under Resource email. For example, solarmora.com_37r2903631@resource.calendar.google.com.

Was this helpful?
How can we improve it?