Backup data from a mailbox to a data file on your own S3 bucket

Overview

Using LegacyFlo you can backup email data from a mailbox to a data file in your own AWS S3 bucket.

Preparation

Before creating migration requests in LegacyFlo, ensure the following:

1. S3 bucket has been created 
2. The S3 registered with LegacyFlo 
3. The source mail server has to be configured to allow mailbox access. 

A. Create an S3 bucket on AWS

Create your S3 bucket in a supported region and allow list and write access to LegacyFlo. The steps for the same are given in the links below:

1. Get an AWS account.
2. Create an S3 bucket in a region supported by Mithi. 
3. Give necessary permissions. 
   1. When the S3 bucket is used as a source, give list and read access to the objects on the bucket
   2. When the S3 bucket is used as a destination, allow list and write access to LegacyFlo.

B. Register your S3 bucket as a source/destination S3 bucket on LegacyFlo

For LegacyFlo to upload data to your S3 bucket, it needs to be added to as a destination S3 bucket in LegacyFlo. The steps for doing the same are as given below:

1. Login to LegacyFlo
2. Click on the Initials icon on the top of the left-most pane.
3. Select Register S3 bucket
4. Click on Add S3 bucket button. A dialog box will pop-up
5. On the Prepare Bucket page, you will be shown the list of steps to be completed to create and grant access to the S3 bucket. Confirm that you have done as instructed and click on I confirm that the above configuration is complete.
6. Click Continue
7. On the Configure, Verify & Save page,  give the Bucket Name and select the Bucket Region.
8. Click Verify. LegacyFlo will check the access to the bucket.
9. If LegacyFlo cannot access the bucket, you will be shown an error message similar to All access to this object has been disabled. Check S3 access rights and name and retry.
10. If the connection is successful then click on Save. LegacyFlo will remember this S3 for further requests.

C. Prepare the SOURCE SERVER to allow access to LegacyFlo

Before using LegacyFlo to access email data from source servers using the IMAP protocol or via the mail server API, confirm the following

Prerequisites for all mail servers

1. The emails to be migrated are available in the mailboxes hosted on the source server. Emails that have been downloaded using the POP protocol and deleted from the server, cannot be migrated using this option.
2. You should have the rights and the capability to reset the passwords on the source in order to access the mailboxes OR should be able to delegate the access.
3. If the source server is hosted at your own premises, you have provisioned sufficient Internet bandwidth to transfer the mailbox data. (This will not apply to SkyConnect, Vaultastic, O365, Yahoo, or GSuite.)
4. The source email service provider should allow large emails downloaded via IMAP/API without any throttling. 
5. Your email service provider supports IMAP or API access to mailboxes. You have configured your email server to allow IMAP or API  access as mentioned in the sections below.

Additional prerequisites

GMail

Migration method	Instruction
Migration using Less Secure IMAP access	For less secure access via IMAP, follow the instructions given here.
Migration using domain-wide delegation for IMAP or API access	For domain-wide delegated access, follow the instructions given here. If using domain-wide delegation for IMAP access (request types GMAILOAUTH-S3-ZIP, GMAILOAUTH-S3-PST, etc), follow the steps given here to enable IMAP access for all the mailboxes to be migrated.

M365/O365

Step	Instructions
Generating  M365 Graph API access credentials for accessing the mailbox data using IMAP or API	Follow the instructions given here. NOTE: For IMAP access,  get confirmation from the O365 support team that there is no throttling on accessing mail from mailboxes on O365 using the IMAP protocol.
Suppress read receipts	Run the following cmdlet if using IMAP access Set-ImapSettings -SuppressReadReceipt $false cmdlet
Delegate access for O365 mailboxes (to be done for all mailboxes to be migrated)	Follow the instructions given here.

Migrate data to your own S3

Once the preparation is done, you can start the migration by submitting migration requests to LegacyFlo. 

Note: This step has to be executed for each mailbox to be migrated.

The request type used to submit a LegacyFlo request will depend on the source type. The tables below gives the details of the preparation and request parameters for different source types:

Source: O365/M365

O365-S3-ZIP	Use this request type to backup data from an O365 mailbox to S3 using IMAP access. The destination file will have EML files in a zipped file. Click here for the details of the request parameters.
O365-S3-PST	Use this request type to backup data from an O365 mailbox to S3 using IMAP access. The destination file will be a PST file. Click here for the details of the request parameters.
M365API-S3-ZIP	Use this request type to backup data from an O365 mailbox to S3 using the API access. The destination file will have EML files in a zipped file. Click here for the details of the request parameters.
M365API-S3-PST	Use this request type to backup data from an O365 mailbox to S3 using the API access. The destination file will be a PST file. Click here for the details of the request parameters.

Source:GMail

GMAIL-S3-ZIP	Use this request type to backup data from a GMail mailbox accessed using Less Secure Access method. Click here to know the parameters to be specified in the Source and Destination information
GMAILOAUTH-S3-ZIP	Use this request type to backup data from a GMail mailbox accessed using domain-wide delegation and IMAP access. The destination file will be a compressed file. Click here to know the parameters to be specified in the Source and Destination information
GMAILOAUTH-S3-PST	Use this request type to backup data from a GMail mailbox accessed using domain-wide delegation and IMAP access. The destination file will be a PST file. Click here to know the parameters to be specified in the Source and Destination information
GMAILAPI-S3-ZIP	Use this request type to backup data from a GMail mailbox accessed using domain-wide delegation and API access. The destination file will be a compressed file. Click here to know the parameters to be specified in the Source and Destination information
GMAILAPI-S3-PST	Use this request type to backup data from a GMail mailbox accessed using domain-wide delegation and API access. The destination file will be a PST file. Click here to know the parameters to be specified in the Source and Destination information

Other Sources

MITHI-S3-ZIP	Use this request type to backup data from a SkyConnect account to S3. Click here for the details of the request parameters.
YAHOO-S3-ZIP	Use this request type to backup data from an Yahoo mailbox to S3. Click here for the details of the request parameters.

Retrieve data from S3

You can retrieve the data by 

1. Downloading the zip file, either using the AWS console or a tool such as S3 browser.
2. Migrating the data to a SkyConnect or Vaultastic account.