Create a mapping CSV file

G Suite Migration for Microsoft Exchange

When migrating data using G Suite Migration for Microsoft Exchange (GSMME), you might need a mapping CSV file.

A mapping CSV file is used to transfer identities (such as users or calendar resources) on your Exchange source domain environment to your G Suite target domain environment. It ensures metadata and usernames are correctly transferred.

Note: GSMME uses 2 files: a control CSV file and a mapping CSV file. This article is about creating and using a mapping CSV file. For details about creating and using a control CSV file, see Create a control CSV file for user accounts.

When to use a mapping CSV file

You might need a mapping CSV file, in addition to a control CSV file, if:

  1. You're migrating calendar data; and
  2. Any addresses for your organization's users in your Exchange source domain environment are different from the addresses in your G Suite target domain environment; and

    Example: jsmith@solarmora.com, jensmith@solarmora.com

    Note: When migrating calendar resources, source domain and target domain addresses are always different.

  3. When the differing domain addresses are attendees in calendar events in other people's calendars you're migrating. Use the mapping CSV file to list all user accounts and calendar resources—even if some of the users aren’t migrated at this time.

How to create the mapping CSV file

  • Create the mapping CSV file in a spreadsheet program with one entry per line.
  • Headers are not required.
  • Make sure your CSV file is correctly formatted, or the migration won't run successfully.
  • We recommend you make a copy of the final file and save it in a text editor as a CSV file so you can review the syntax for consistency. Some spreadsheet editors add quotation marks to cells, which you need to delete before running the migration. Adding a space after the comma is optional.
  • You only need to include user accounts in the mapping CSV file if they have a different address in G Suite than their legacy address.

    Example: jsmith@solarmora.com, jensmith@solarmora.com

Format of the mapping CSV file

Mapping users

The general structure of the mapping CSV file is sourceuser, targetuser. If the email addresses in your Exchange source domain environment are different from the addresses in your G Suite target domain environment, you need 2 addresses per line in the CSV file—the source user address followed by the target user address.

Example: jsmith@solarmora.com, jensmith@solarmora.com

If the the sourceuser is identical to the targetuser, you can exclude the targetuser.

Example: djones@solarmora.com

GSMME control CSV file - email and contacts

Mapping calendar resources

The general structure for adding calendar resources to the mapping CSV file is source-resource-email, gsuite-target-resource-email.

Example: board-room-1@solarmora.com, solarmora.com_37r2903631@resource.calendar.google.com

GSMME control CSV file - email, contacts, and calendar resources

To find the G Suite calendar resource email:

  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 Appsand thenG Suiteand thenCalendar.
  3. Click Resources.
  4. On the Resources page, click a calendar resource name (for example, NYC-14-12-Boardroom-15) to view its details.

    For more information on calendar resource naming conventions, see Resource naming recommendations.

  5. Next to Resource email, copy the G Suite calendar resource email.

    For example, solarmora.com_37r2903631@resource.calendar.google.com.

Google, G Suite, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.
Was this helpful?
How can we improve it?