This article provides information on Mimecast account migration limitations, detailing what data and configurations cannot be migrated, including logs, stationery, hold queues, and synchronization engine data, along with key considerations for administrators.
Account Logs
Account Audit and Search Audit event logs cannot be migrated to your new Mimecast account. Your existing Mimecast account will still be accessible for 90 days after your migration.
Account Branding
- Account Branding
Archive
Your archive data will be migrated from your existing account to your new account, however the following specific items cannot be migrated:
- Archive Search History
- Archive Saved Searches
- Archive eDiscovery Cases
- Archive Smart Tags
- Archive | Retention Periods
You will be able to create these manually in your new Mimecast your account. Mimecast support staff are unable to migrate these on your behalf because they need to be created by an Administrator with content access to your organization's archive.
Attachment Link on Size
Links to attachments that were subject to an Attachment Link on Size policy will expire 90 days after your migration has been signed off when your existing Mimecast account is disabled. Consequently these attachments will not be accessible using the link in the message in the user's Exchange mailbox or by any external recipients of such a message. If your organization archives with Mimecast your internal users will be able to access the original attachment in the archive using Mimecast applications.
Targeted Threat Protection
Any old Targeted Threat Protection re-written URLs will expire 90 days after your Mimecast Migration. The URLs will continue to work and redirect to the original URLs however Mimecast will not perform any further security checks. Any managed URLs can be manually copied from your existing account to your new one. This has a potential impact on the following:
- Targeted Threat Protection Dashboard Statistics
- Recent Security Alerts
- Managed URLs
- Targeted Threat Protection reporting
Stationery
Existing Stationery Layouts will not be migrated. The Mimecast support team will assist you with reconfiguring stationery on your new Mimecast account during the migration. During migration it is important to consider the following Stationery features:
- Stationery Layouts
- Stationery Actions (Click Actions)
- Stationery Images
- Stationery Reports
- Stationery Micro Sites
Logs
All the monitoring logs will not be migrated from your existing Mimecast account to your new one. Your existing Mimecast account will still be accessible for 90 days after you sign off on your migration, allowing access to this data during that time period. Below is a summary of the logs that need to be considered:
- Message Center | Bounced Messages
- Message Center | Message Delivery
- Message Center | Held Messages
- Message Center | Processing Queues
- Message Center | Rejected & Deferred Messages
- Email Security | URL Protection Logs
Hold Queue
The following Hold Queues will not be migrated to your new Mimecast account. Your existing Mimecast account will still be accessible for 90 days after you sign off your migration, allowing access to this data during that time period. Below is a summary of hold queues that need to be considered:
- Attachment Management
- Content Examination
- Spam Scanning
- Suspected Malware
- Archive Limit Exceeded
- Suspicious Message Structure
Large File Send
We are unable to migrate Large File Send and Large File Receive files.
Delegate Access
Mimecast employees do not have the ability to grant delegate mailbox access. Mimecast administrators that have protected permissions have the ability to view delegate access on the source account, export to excel and also import delegate access on the destination Mimecast account.
Setting up delegate access requires protected permissions, and must be configured by a Mimecast administrator with protected permissions. For more information about protected permissions, see Understanding Administrator Roles.
Mimecast Synchronization Engine
Mimecast Synchronization Engine replicated data cannot be migrated old account to new for example, from your Mimecast UK to Mimecast Australia. Customers must rebind the Mimecast Synchronization Engine instance and run a full synchronization to rebuild the replicated data. Mimecast's technical teams can assist with migrating the schedules, tasks, and definitions, but customers are responsible for rebinding the Mimecast Synchronization Engine application. Mimecast Synchronization Engine tasks include:
- Mailbox Folder Replication
- Managed Folders
- Calendar Replication
- Mailbox Storage Management
- User Initiated Stubbing
- Mailbox Permission Sync
Comments
Please sign in to leave a comment.