The table below outlines the main configuration objects requiring evaluation when migrating from Google Postini to Mimecast. It is important to note that there may case by case variations for individual customers.
For more information on Google Apps migration, view the last topic in this article.
|Organization Policy Management||Your Mimecast Account Settings for the organization, and Application Settings for user apps|
|Delegate Administration and Restrict searches||Understanding Administrator Roles|
|Directory Sync||Directory Synchronization|
|N/A||Service failure alerts for Administrators through The Service Monitor|
|Password Policies||Your Mimecast Account Settings|
|Log Search||Administration Console: Auditing Logs Files|
|General Settings||Your Mimecast Account Settings|
Archived email search
Advanced Boolean search
Detailed Message display
Identity lookup and search
Transfer ownership of saved searches or investigations
|eDiscovery Cases and Mimecast Personal Portal: Smart Tags|
|Investigation summary pages||Archive Administration 'Search and 'View Logs', and eDiscovery Cases Logs|
|User Holds, Place a hold on saved search results||Litigation Holds|
|Personal Archive||Available through multiple Applications|
|Export saved results||Export and Collect Data|
|OU based retention||Configuring Content Preservation (Days / Minutes) Policies , Configuring Metadata Preservation (Days / Minutes) Policies|
Mimecast provides dedicated hosts for Inbound, Outbound and Journal communication, which will support Google Apps. Google Apps does not have a Journaling feature, but all messages exchanged internally are delivered via the mail gateway / smart host that has been set up automatically.
See the Using a Google App with Mimecast page for further details.
For continuity, Mimecast Mobile or Mimecast Personal Portal will have to be used. Mimecast Synchronization Engine is not supported.