Data Retention - Providing Legacy Data for Data Import Project

If you are preparing your legacy Archive Data Management data for a Data Import Project and it has been exported and collected, it can be sent to Mimecast for processing if you have an existing Data Import Project. This article covers the steps involved in uploading the data for it to then be imported.

Requesting Data Transfer Media

We need the information listed below to process the transfer media request. This information must be submitted in the CDR/RFI request for your Legacy Data Import Management project and case:

• Contact person's name and telephone number.
• The exact total bytes to be uploaded.

• Details on the submitted data as outlined in the table below:

  Data	Details
  Cut Off/Journaling Date	The date when we began archiving all your emails. No messages dated after this journal date will be imported.
  Data Size	Total amount of data ready to be sent to us
  Grouping	Whether the individual PSTs and / or EML zip files contain data PU and / or NPU
  File Format	The format of the journal data if relevant (e.g. SJF, EJF).
  File type(s)	The specified file type (e.g. PST, Zipped EML).
  Source	The email system(s) and version the data is exported from (e.g. Exchange, dedicated archive solutions, host environments).
  Export utility used	The type of export utility used (e.g. Ex- merge, Outlook 2003, third party tools/ conversion utilities).
  Test	We do not run test batches as a policy. Inquire with your Sales contact if testing is desired.

The primary option is uploading data to FTP using Mimecast's secure FTP site. For some Microsoft 365 and Google Workspace tenants, Mimecast may also use direct connector-based import methods depending on the data source. Your Mimecast contact will confirm the applicable transfer method for your project.

Transferring Media

The standard transfer method is Mimecast's secure FTP site, which is used to upload PST and Zipped EML files. Data is transferred using explicit FTP over TLS (FTPeS), ensuring that archive data is exported and uploaded over a highly secure channel.

Mimecast's FTP Site

We use our own secure FTP site as the preferred method for providing customer data whenever possible. This only accepts secure TLS connections. The FTP site is significantly quicker and simpler to use. Using the Mimecast FTP site requires the following:

• An account prepared by us for your data, restricted to the maximum amount that has been agreed to.
• The hostname, username and upload instructions are provided by the Data Import Project owner/ team via email. These details will include the secure FTPeS host and port information to use with your FTP client (for example, FileZilla).
• FTP account password will be sent via a Secure Email message from Mimecast which you will be required to sign in to retrieve. Reply to the Data Import Project owner/team email to confirm receipt.
• Your firewall must permit outbound FTP communication on the ports specified by Mimecast (typically port 21 for control, with additional high ports for data transfer) from the device uploading to the Mimecast FTP host.
• Data uploaded via FTP must not be encrypted, as the FTP communication itself is secured via TLS.

Transferring Data

The process for transferring your legacy data to the transfer media is using Mimecast's FTP site. Use a secure FTP client (such as FileZilla) configured for explicit FTP over TLS (FTPeS), connect using the credentials and host details provided by Mimecast, and then upload the PST and / or Zipped EML files as instructed by the Data Import Project owner / team.

Mimecast FTP Site

The Mimecast FTP site requires explicit FTP over TLS (FTPeS) that is supported by the recommended Filezilla FTP client. The Data Import Management team will provide the host, username and password via email. Additionally, data uploaded via FTP must not be encrypted as the FTP communication is highly secured by FTPes.

To transfer all data to be imported:

1. Ensure your firewall permits outbound FTP communication on:

• Port 21
  • It's inbound response from the device FTP uploading to the Mimecast FTP host.

2. Download and install the Mozilla Filezilla FTP client.
3. Enter the provided FTP details into the Quickconnect bar.
4. Click the Quickconnect button.
5. Click the OK button on the popup window that reports an unknown certificate.
6. Specify a destination folder.
7. Right click the source folder.
8. Select Upload.
9. Click the Process Queue on the Transfer menu, if not selected already, to begin processing the queue.
10. Reply via email to the Data Import Management team to confirm when the upload is complete.

See Also...

• Legacy Archive Data Management Processing