X hits on this document

199 views

0 shares

0 downloads

0 comments

23 / 75

8.

Click Authorize. You should see the API scopes listed on the page. For example:

With this configuration, you can migrate data to all your domains using the consumer key for just your primary domain.

Create user lists

Create a CSV (comma-separated value) file for each group of users you want to migrate. If you plan to use multiple client machines, you need a separate list for each client, and each list must contain a unique set of users. We recommend you don’t exceed 1000 users in a single CSV.

You can use Excel or any spreadsheet software to create the CSV. We recommend you copy the final file and save it in Notepad as a CSV so that you can review the syntax for consistency. Some spreadsheet editors add quotation marks to cells, which you need to delete in Notepad before running the migration. Please spend extra time on this step to make sure your CSV is correctly formatted, or else the migration won’t run successfully.

The general structure of the CSV should be:

sourceuser, destinationuser

And destinationuser can be removed if it's identical to sourceuser. Adding a space after the comma is optional. Depending on the type of server you’re migrating from, there are some variations on this format. See below for details.

Microsoft® Exchange Server

If you are migrating from a Microsoft® Exchange Server, we recommend you use the same usernames in Google Apps as you do in your current mail server. This streamlines the process and allows you to create user lists with just one name or SMTP address per line. You don’t need to enter your users’ passwords in the CSV because authentication is through your Exchange server administrator account.

Preparing for Your Migration

23

Document info
Document views199
Page views199
Page last viewedMon Dec 05 17:05:27 UTC 2016
Pages75
Paragraphs1452
Words14930

Comments