Google Apps Migration for Microsoft Exchange Administration Guide - Manual (Page 28)

28 Google Apps Migration for Microsoft ® Exchange Administration Guide
PST Migration
You can use the utility to migrate PST files. If you want to migrate PST files, you need to set up
a folder structure to accommodate those files.
Note: Google Apps Migration for Microsoft Exchange cannot migrate password-protected
PST files. Disable password protection for PST files before you attempt to migrate, or
migration will fail.
You need one top-level folder. Within that top-level folder, you need an individual folder for
each user whose PST files you want to migrate. Within each individual folder, you place the
PST files.
PST (top-level folder)
• [email protected] (individual folder)
• archive.pst (PST file to migrate)
• MyPst.pst (PST file to migrate)
Name the individual folders’ names based on the primary e-mail address as configured in the
source mail system. (see
“Create lists of the users you want to migrate” on page 26).
For example, if your file of user names takes the form:
• [email protected]
• [email protected]
then name your individual folders:
• [email protected]
• [email protected]
Allow Read and Write permissions on each individual PST file so that the utility can write
migration-related metadata to those files.
Note: If you are using an exported or archived PST file, it is not possible to identify the
primary root folder for Calendar and Contacts. Therefore, all calendars are migrated
as “additional calendars” into Google Apps Calendar, instead of any default calendar.
You can avoid this by using PST migration for mails only, and use Exchange server
migration for migrating calendars.