Using LegacyFlo you can backup email data from a mailbox to a data file in your own AWS S3 bucket.
Before creating migration requests in LegacyFlo, ensure the following:
- S3 bucket has been created
- The S3 registered with LegacyFlo
- 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:
- Get an AWS account.
- Create an S3 bucket in a region supported by Mithi.
- Give necessary permissions.
- When the S3 bucket is used as a source, give list and read access to the objects on the bucket
- 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:
- Login to LegacyFlo
- Click on the Initials icon on the top of the left-most pane.
- Select Register S3 bucket
- Click on Add S3 bucket button. A dialog box will pop-up
- 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.
- Click Continue
- On the Configure, Verify & Save page, give the Bucket Name and select the Bucket Region.
- Click Verify. LegacyFlo will check the access to the bucket.
- 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.
- 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
- 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.
- 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.
- 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.)
- The source email service provider should allow large emails downloaded via IMAP/API without any throttling.
- 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.
|Migration using Less Secure IMAP access|
|Migration using domain-wide delegation for IMAP or API access|
|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.
Run the following cmdlet if using IMAP access
Set-ImapSettings -SuppressReadReceipt $false cmdlet
|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:
Retrieve data from S3
You can retrieve the data by
- Downloading the zip file, either using the AWS console or a tool such as S3 browser.
- Migrating the data to a SkyConnect or Vaultastic account.