Migrating to Mimecast Australia

Document created by user.oxriBaJeN4 Employee on Nov 6, 2015Last modified by user.oxriBaJeN4 Employee on Apr 10, 2017
Version 2Show Document
  • View in full screen mode

When migrating your Mimecast account to the Australian Data Center, there are certain steps that need to be followed to ensure a successful migration. Depending on what service you have with Mimecast will determine the process and steps. Please select from the option that best suits your subscription to get started:

There may be some variations or add-ons to your account that will need to be taken into consideration. Your migration will be carefully planned with Mimecast support engineers to ensure that 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 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

 

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. Existing data on the UK grid is exgested and prepped for ingestion into new Australian account
  6. Migration of customer’s account configuration and policies
  7. Account review and testing
  8. Migration dates scheduled
  9. Journaling amended to single journal to Australian account
  10. Data ingestion to Australian account completed
  11. Customer Sign off
  12. 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. Existing data on the UK grid is exgested and prepped for ingestion into new Australian account
  6. Migration of customer’s account configuration and policies
  7. Account review and testing
  8. Migration dates scheduled
  9. Update Outbound Send Connectors
  10. Update Inbound MX Records
  11. Customer Sign off
  12. Post Migration Tasks

 

Migration Steps Explained

 

Once you have formally requested to migrate to the Mimecast Australia 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 in order 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 is provided for each step in the process to assist you to make the required configuration changes. Below are the specific steps required for the migration. Your Mimecast subscription will determine which steps are required.

 

Step 1: 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.

 

Step 2: Account Creation

 

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

 

Step 3: Review and amend Firewall Rules

 

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

 

NetworkIP Address RangeNetmaskInbound Connections *External Delivery **
103.13.69.0/24103.13.69.1to103.13.69.254255.255.255.0Archived Message.gifArchived Message.gif
124.47.150.0/24124.47.150.1to124.47.150.254255.255.255.0Archived Message.gifArchived Message.gif
FeatureProtocolPortDirection
Active Directory Sync and LDAP Domain AuthenticationLDAP/S389 / 636Inbound
Outbound emailSMTP25Outbound
Journal email (archiving only)SMTP25Outbound
Inbound emailSMTP25Inbound
Mimecast Applications and Administration ConsoleHTTPS443Outbound
EWS / ADFS Domain Authentication HTTPS443Inbound
Integrated authentication for Mimecast for OutlookHTTPS443Inbound

Step 4: Recipient Validation and Dual Journaling

 

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

 

  • To ensure Administrators and users have access to 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 here.

 

Step 5: Export Mimecast UK data & Ingest into Mimecast AU

 

If you are an archiving customer, you will be assigned a Legacy Data Management engineer to assist with exporting your legacy data from your existing Mimecast account to your new one. This task will be completely managed by our Legacy Data Management team and you will be kept up to date with the data transfer progress at each step of the way. Mimecast will transfer your data through a combination of encrypted magnetic disks, and secure FTP from between the Mimecast Data Centers.

 

Please see this article for more information regarding our Legacy Data Management processes.

 

Step 6: Migration of Customers Account Configuration and Policies

 

Mimecast implementation engineers will migrate your policies and account configuration to your Mimecast Australia account. Please note there are some things that cannot be migrated.

 

For more information please review the migration limitations article.

 

Step 7: Review, Testing & Sign Off

 

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

 

Step 9: Update Outbound Send Connectors

 

You will need to modify your existing SMTP send connectors to send outbound  and journal email (archiving only) to the Mimecast Australia Gateway.

 

The hostname(s) for the Mimecast Australia Gateway can be found in the routing outbound article.

 

Step 10: Update Inbound MX Records

 

You will need to modify your existing MX records to route inbound email to the Mimecast Australia Gateway.

 

The hostname(s) for the Mimecast Australia Gateway can be found in the routing outbound article.

 

Step 11: 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 of the migration support case.

 

Step 12: 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 AU DC.

 

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

Attachments

    Outcomes