Explaining briefly, users can migrate their email, calendar and other data to Google Apps in three easy steps:
1. Prepare the Google Apps Domain
The first step is making settings changes in the Google Apps Admin console that will allow mail migration. These settings/requirements are:
Google Apps: In the Google Apps Admin console the user has to enable the provisioning API, the OAuth consumer key and then specify the API scopes. It is important to remember that Google Apps for Business accounts are necessary before the user gets the Google Admin console.
Original (Traditional/Legacy) Server: Your Company must be running Microsoft Exchange Server (2000/2003/2007 or 2010) or an IMAP server (for example RFC 3501-compliant IMAP server including Novell Groupwise, Cyrus, Courier, Microsoft Exchange, Zimbra, Dovercot or Gmail/SunMail). Secondly, an administrative account on the server is required that has the permission to read each user’s mailbox. In Microsoft Exchange, the “Receive As” permission will also suffice.
GAMME SYSTEM REQUIREMENTS: You can run the Google Apps Migration for Microsoft Exchange on any number of computers (to speed up large migrations.) Windows is required for each of the computers on which the user installs the utility - for example XP SP3, Windows 7, Vista Xp3 or Windows Server 2003/2008. Another requirement is to have Microsoft Outlook 2003/2007 or 2010.
2. Create a File of Users to Migrate to Google Apps
The second step is to create a CSV file of all the users an IT administrator wants to migrate mails of. CSV is a comma-separated value file which is needed if the IT admin wants to use multiple client machines. The lists of all the users will be separated and each list will contain a unique set of users. For an optimized migration to Google Apps It is recommended to not exceed more than 1000 users in one CSV. Creating a CSV is easy as it can be done in any Excel or spreadsheet software. The final file can be copied or saved in Notepad as CSV so that the IT admin can review the syntax for consistency.
Since some spreadsheet editors add quotation marks to the cells, the IT admin needs to ensure that those are deleted in Notepad before going ahead with migration. GAMME runs extensive tests before a migration and added quotes is the most common failure/error. In order to ensure that migration is successfully run, the correct formatting of CSV is crucial. If the IT admin is migrating from Microsoft Exchange Server then he can use the identical usernames in Google Apps as used in current mail server. This will streamline the process and will also allow the IT admin to create user lists with one SMTP address per line. It is important to note that the IT admin will not have to enter the users’ passwords in CSV as authentication will be done through Exchange server administrator account stated in the requirements before.
3. Install and Run the Google Apps Migration for Microsoft Exchange Tool.
Once the first two steps are done, the third step requires the user only to download the GAMME tool. The tool can be downloaded from Google and the latest version 3.0.1365.453 is available. After the installation is complete, the IT admin will only run it to begin mail migration.
These steps are explained as an introduction to explain the overview of the migration process in GAMME. There are a lot of benefits of using Google Apps Migration for Microsoft Exchange - GAMME - and banking on these advantages, Google has been able to add more users to its base from Microsoft.