Simply Migrate - Migration of EML Files via Mimecast API

The Simply Migrate Management UI simplifies the migration of EML files to the Mimecast API. This article provides steps on how to do this. 

Prerequisites 

• Determine where the EML files are located. These will be in a drive letter if it is a locally attached drive, or UNC path if it is not.
• Determine if the files are grouped as Per User or Non Per User.
• If the data is grouped as Non Per User, determine the format. (Journal Envelope Format or Standard Journal Format).

Migrating EML files 

From the UI, there are two ways to create jobs: 

1. Following the initial installation, the Wizard will prompt the administrator to select the Source. If the product has been set up and initialized, the administrator will need to start the Job Wizard from within the Batches and Jobs view.
2. Select the Green List icon on the Batch line that the administrator wants to create the jobs, then select Job Creation Wizard from the list.

3. The administrator will be presented with the Source selection. Select EML Files.
4. Enter the path gathered from the prerequisite steps listed above, and also the answer to the question about the files being zipped. 

In the example above, the EML files are local to the server, so drive letter has been used. Note the following for other scenarios:

• Should the data be in multiple sub folders we can scan subfolders for zip files.
• If the data consists of raw EML files under the folder, jobs can be created using the folder names.
• If the files are in EJF format then we would select the Extract EJF Message toggle.

5. Now click Next.
6. At this point, the administrator will be presented with the list of folders found. If data is grouped Per User an email address of the user being assigned to the folder will also be provided. The email address is calculated from the name of the folder or zip file, as shown below.
   

As shown above, EML Folders that have been discovered for which an SMTP address could not be determined, by default it would not be selected to be migrated. There are 2 ways to deal with these jobs:

• Add the SMTP address of a user to the Mailbox field, and select the checkbox to add the folder or zip file to the eligible selection. This will cause the contents of that folder or zip to be migrated into that users archive.
• Check the box without an SMTP address. This will cause the folder or zip contents to be migrated as Non Per User journal data.

Bad Address Resolution section in the top banner gives administrators the ability to download/upload a CSV file that will assign the correct SMTP address to each line item instead of doing it one at a time in the UI.

8. The administrator can add filters that apply to dates, job lists, and handle bad address resolution. These controls are seldom used, however, an administrator will be prompted about date filters once Create Jobs is selected. 

Filtering the jobs will only change the view the administrator has of the jobs. Simply Migrate will attempt to create jobs for ALL items ticked, not only those visible in the filter.

9. Clicking Create Jobs will prompt you with some information, and the option to select a date filter as shown here. At this point, confirm that the number of jobs being created is correct, and that the jobs do not require a date filter.
10. Click Create the jobs.

• The gears start turning and the jobs start getting created, you will notice a tick being shown in the job status next to all the source files that have been selected.

If the administrator attempts to create jobs for the same PST files (In the same batch), Mimecast has created safety measures to avoid duplication of jobs. The administrator will be shown the original job ID and a No Entry sign indicating that the job has not been created because it already exists. 

Congratulations, you have created your EML file source jobs.