Simply Migrate - Migrating Between Mimecast Regions

Once you have formally requested to migrate to the Mimecast Data Center, our migration team will be in contact to begin the planning. The migration is broken down into several steps to keep it as simple as possible. Your existing Mimecast account will be used as a template; however, as part of the migration, you will be required to re-configure certain aspects of your Mimecast integration. For example:

• Directory Connectors
• Journal Connectors
• Firewall Rules

Each step of the migration will be managed by a dedicated migration team, and detailed information is provided to the Technical Point of Contact (TPOC) of your organization to complete each step in the process. Our support team members will not have access or permission to make changes to your infrastructure. Guidelines and documentation are provided for each step in the process to assist you in making the required configuration changes. Below are the specific steps required for the migration. Your Mimecast subscription will determine which steps are required.

There may be some variations or add-ons to your account that will need to be taken into consideration. Your migration will be planned with Mimecast support engineers to ensure the process runs smoothly.

Mimecast Security

The following steps will form the high-level plan for the migration of customers subscribing to Mimecast Security:

1. Authorization to Migrate
2. Account Creation
3. Review and Amend Firewall Rules
4. Recipient Validation Configuration
5. Migration of Customer’s Configuration and Policies
6. Account Review and Testing
7. Migration Dates Scheduled
8. Update Outbound Send Connectors
9. Update Inbound MX Records
10. Customer Sign-Off
11. Post Migration Tasks

Mimecast Express

The following steps will form the high-level plan for the migration of customers subscribing to Mimecast Express:

1. Authorization to Migrate
2. Account Creation
3. Review and Amend Firewall Rules
4. Recipient Validation and Dual Journaling Configuration
5. Migration of Customer’s Configuration and Policies
6. Account Review and Testing
7. Migration Dates Scheduled
8. Update Outbound Send Connectors
9. Update Inbound MX Records
10. Customer Sign-Off
11. Post Migration Tasks

Mimecast Archive

The following steps will form the high-level plan for the migration of customers subscribing to Mimecast Archiving:

1. Authorization to Migrate
2. Account Creation
3. Review and amend Firewall Rules
4. Recipient Validation and Dual Journaling Configuration
5. Migration of Customer’s Account Configuration and Policies
6. Account Review and Testing
7. Migration Dates Scheduled
8. Customer Sign-Off
9. Post Migration Tasks

Mimecast Enterprise

The following steps will form the high-level plan for the migration of customers subscribing to Mimecast Enterprise:

1. Authorization to Migrate
2. Account Creation
3. Review and Amend Firewall Rules
4. Recipient Validation and Dual Journaling Configuration
5. Migration of Customer’s Account Configuration and Policies
6. Account Review and Testing
7. Migration Dates Scheduled
8. Update Outbound Send Connectors
9. Update Inbound MX Records
10. Customer Sign-Off
11. Post Migration Tasks

Authorization to Migrate

Your Mimecast account manager will call to discuss the options and timeframes to migrate your Mimecast account. Your Mimecast Account manager will assist with scheduling your migration and assigning a Mimecast implementation engineer to assist you with the migration.

Account Creation

Once your new Mimecast account has been created, you will be provided with new login credentials.

Review and Amend Firewall Rules

Ensure that your firewall is configured to allow inbound and outbound connections to these IP ranges:

Network IP	Address Range	Netmask
103.13.69.0/24	103.13.69.1 to 103.13.69.254	255.255.255.0
124.47.150.0/24	124.47.150.1 to 124.47.150.254	255.255.255.0

Recipient Validation and Dual Journaling Configuration

On your Mimecast account, you will need to configure recipient validation and dual journaling (archiving only). Configuring recipient validation will synchronize a list of internal email users, groups, and user attributes to Mimecast platform using either Directory Sync or a spreadsheet import. Dual Journaling will allow all email communication to be captured on your existing Mimecast account and your new account hosted in the specific region during the migration. Dual journaling is required:

• Ensure administrators and users access your organization's internal messages via your existing and new Mimecast accounts.
• To allow for the exgestion of data from your existing Mimecast account and then ingestion of this data into your new Account while maintaining a complete and compliant archive in the existing account.

Once the data is ingested, the dual journaling can be removed, and you should continue journaling to your new account only. More details on this step can be found on the Legacy Archive Data Management page.

Migration of Customer's Account Configuration and Policies

Mimecast implementation engineers will migrate your policies and account configuration to your Mimecast account. Please note there are some things that cannot be migrated. For more information, please review the Mimecast Account Migration Limitations article.

Review, Testing & Sign Off

Mimecast’s implementation engineer will review your new Mimecast account with your primary implementation contact. Together you will review your old and new Mimecast accounts and run some tests to ensure your firewall is configured correctly.

Migration Dates Scheduled

This are the dates scheduled for migration.Your Mimecast Account manager will assist with scheduling your migration and assigning a Mimecast implementation engineer to assist you with the migration.

Update Outbound Send Connectors

You must modify your existing SMTP connectors to send outbound and journal emails (archiving only) to the Mimecast Gateway. The hostname(s) for the Mimecast Gateway can be found in the Connect Process: Setting up Your Outbound Email article.

Update Inbound MX Records

You must modify your existing MX records to route inbound emails to the Mimecast Gateway. The hostname(s) for the Mimecast Gateway can be found in the Connect Process: Setting up Your Outbound Email article.

Customer Sign Off

You will need to run some tests and ensure everything is working as expected. Once we have final confirmation, your implementation engineer will close the migration support case.

Post Migration Tasks

Once the migration has been completed and tested, you can start to update the following configurations on your old account.

• Journal connections
• Update end-user tools to point towards the regions Data Center.

Your old Mimecast account will be disabled 90 days after you have signed off your migration.