DMARC Analyzer 2.0 - Migration Guide from DMARC Analyzer 1.0

Updated

This article contains information on preparing for migration from DMARC Analyzer 1.0 to DMARC Analyzer 2.0, including required DNS updates, administration setup, the migration workflow, post‑migration tasks, and key feature changes.

Overview

This guide has been created to help you prepare to migrate from the legacy DMARC Analyzer 1.0 to DMARC Analyzer 2.0 and includes additional steps for customers with only DMARC Analyzer 1.0.

DMARC Analyzer 2.0 provides hosting flexibility across all regions where Mimecast operates, is integrated with the Mimecast Administration Console, and includes advanced features. There are changes in key areas of functionality (Data residency, Application domain names (URLs), and Authentication) which require you complete the steps given in this guide, in order to complete the migration process.

Considerations

  • If you have more than one Mimecast product, your DMARC Analyzer 1.0 account should already be linked to your Mimecast Administration Console environment.
  • Customers with only DMARC Analyzer 1.0 will be supported to get access to the Mimecast Administration Console.

Prerequisites

  • You have an Administrator role that allows you access to the Mimecast Administration Console.
    Basic Administrator is recommended for general administrative duties.

A Basic Administrator will have full access permissions for DMARC Analyzer 2.0. See Role Types and RBAC Role Permission Change.

DMARC Analyzer 1.0 to DMARC Analyzer 2.0 migration process

Customers with only DMARC Analyzer 1.0

Customers with only DMARC Analyzer 1.0 must first complete the following:

  1. Get access to the Mimecast Administration Console.
    If you need help accessing the Mimecast Administration Console for the first time, call Mimecast Support and speak to the Triage team, who will help you obtain login credentials for the Mimecast Administration Console.
    The correct URL to use for the Mimecast Administration Console is: 
    https://login.mimecast.com/admin
  2. Once you have access to the Mimecast Administration Console, you need to add your main domain, and any of your other domains that you wish Administrators to log in with. See Directories - Managing Internal Domain & Subdomains or Email Security - API - Directories - Managing Internal Domain & Subdomains for setup information.

Pre-migration checklist

All DMARC Analyser 1.0 customers must complete the following:

  1. Ensure you are able to access and log in to the Mimecast Administration Console.
    If you have lost access to your Mimecast Administration Console environment (due to missing login information, or expired credentials), call Mimecast Support and speak to the Triage team, who are able to help if you're unable to access your Mimecast ID.
  2. Check which DMARC Analyzer 1.0 user accounts still need access to DMARC Analyzer 2.0, and create those users in the Mimecast Administration Console. 
    See Directories - Creating & Editing Users and Email Security - API - Directories - Creating & Editing Users.
  3. Set up Administrator roles in the Mimecast Administration Console. Administrators must be created with matching email addresses before migration, for full alert and user correlation.  
    Super / Full / Basic / Partner Administrator roles will have full access permissions to DMARC Analyzer 2.0. For users requiring limited access to DMARC Analyzer 2.0, you will need to create a custom role.
    See:  
  4. Adjust your DNS record TTL (Time to Live), for more convenient DNS updates of the DMARC and Delegated SPF record configuration. 
    See DMARC Analyzer -  General DNS Vendors Setup Guide.

Migration process

During the migration process, the following will happen:

  • Migration of all domain configurations, domain groups, users, and notifications.
  • Transfer of historical DMARC report data to regional infrastructure.
  • Migration of DMARC Analyzer RBAC settings.
  • Migration of SPF Delegation configurations.
  • Migration of PGP key (if configured).
  • Set up of regional access and authentication.
  • Your Account will be in read-only mode during migration. 
    During the migration process, your data will be moved from AWS Ireland to your respective contractual hosting jurisdiction (UK, Germany, US, etc.). 
    You'll be informed if attempting access relevant pages during this time.

Once migration is complete, you will receive a notification email to confirm that your migration is completed, and you will then be able to continue with the following post-migration steps.

In case of any issues during the migration process, contact your Customer Success Manager (CSM) or Mimecast Support.

Post-migration checklist

You should carry out the following post-migration checks:

  1. Log in to Mimecast Administration Console | DMARC Analyzer 2.0 and navigate to the Migration Dashboard. This displays:
    • What was migrated 
    • What couldn’t be migrated. 
    • What would require user intervention or change in configuration.  
      Take a look at any failed items that need resolving, and action accordingly.
    • Inline guidance on how to resolve issues, e.g., “Domain group has 15 domains, the limit is 10. Create two groups instead.”

      DMARC Migration Dashboard
  2. Update your DMARC and SPF / DNS records that point towards the DMARC Analyzer application, so that data can be sent to the new geographical destination. 
    See DMARC Analyzer -  General DNS Vendors Setup Guide. and DMARC Analyzer 2.0 - SPF Record Entries.
  3. Review the SPF Delegation configuration before changing to the migrated setup. For DMARC record changes, this is the perfect opportunity to configure DMARC Delegation for your domains. 
  4. Update your Mimecast login links to use the unified login for the Mimecast Administration Console.
    Previously: https://app.dmarcanalyzer.com/login DMARC Analyzer.
    Now: https://login.mimecast.com for the Mimecast Administration Console.

You may need to update DMARC Records and SPF Delegation configurations post-migration. Mimecast will send you an automated reminder, if this is required.
The Domain Management page in DMARC Analyzer 2.0 will give further details.

Post Migration

The system will send weekly reminders (post-migration) if domains still use the old DMARC Analyzer RUA and RUF addresses; it will specify the domains wherever possible.

Frequently asked questions

Q: How can I best structure Domain Groups?
A:

Groups with more than 10 domains, exclusion patterns, or domain exclude lists are not fully supported in DMARC Analyzer 2.0. You will need to restructure these by either:

  • Creating a Static Domain Group which contains explicitly mentioned domains (and can contain/include subdomains).
  • Switching over to Dynamic Domain Groups, which are simply configured with basic wild-card patterns

See DMARC Analyzer 2.0 - Domain Management.

Q: What do I need to know about SPF Delegation Records in DMARC Analyzer 2.0?
A: SPF Delegation Records are region-specific in DMARC Analyzer 2.0. Mimecast will generate a new SPF record, but will not auto-publish it. You must verify and publish these via the DMARC Analyzer 2.0 portal.
Q: What do I need to know about DNS Record Updates in DMARC Analyzer 2.0?
A: All DMARC and SPF DNS records pointing to Ireland must be updated to the new regional endpoint. You can do this manually, or use DNS delegation.
Q: Why do I need to create Administrators in the Mimecast Administration Console before migration?
A: If Administrators are not pre-created in the Mimecast Administration Console before migration, alert references will not correlate correctly and will require manual cleanup post-migration.
Q: What location will my data be moved to, post-migration?
A: Your data will be moved to your respective contractual hosting jurisdiction (UK, Germany, US, etc.).
Q: Where can I find out more about the Public API for the Mimecast DMARC Analyzer?
A:

See Also...

 

Related to

Was this article helpful?
0 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.