Using LegacyFlo you can backup email data from an IMAP account to a zipped EML 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 IMAP 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.
- Allow list and write access to LegacyFlo.
B. Register your S3 bucket as a 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
- Select Add Request
- On the left pane,
- Give a dummy title
- Select MITHI-S3-ZIP as the Request Type
- In the section on Destination Information,
- Click the [+] icon next to S3 Bucket Name
- 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 IMAP access from LegacyFlo
- 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.
- Your email service provider supports IMAP access to mailboxes.
- You should have the rights and the capability to reset the passwords on the source in order to access the mail boxes OR should be able to delegate the access to a user whose credentials are known.
- 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 allows large email downloaded via IMAP without any throttling.
- You have configured your email server to allow IMAP access as mentioned in the sections below.
- In addition to the above, GMail servers need additional configuration depending on whether you are using less secure or OAuth access. Follow the instructions given in the table below:
|GMail with less secure app access||Follow the instructions given here.|
|GMail with OAuth access||Follow the instructions given here.|
- In addition to the above steps, to provide delegated access to mailboxes on O365, follow the instructions given below:
|Delegate access to mailboxes on O365||Follow the instructions given here.|
Migrate data to your own S3