Seamlessly migrate email data between platforms

Overview

• Using LegacyFlo you can migrate user's live email data between mail platforms.
• LegacyFlo allows to migrate data from Gmail, O365, Exchange, Other IMAP server

Preparation

Preparation for source server

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 credentials to access the mailboxes to be migrated. 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. 
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

Google Workspace - GMail

LegacyFlo can access GMail mailboxes using 3 methods

1. Accessing mailboxes using API (recommended)
2. Accessing mailboxes using domain-wide delegated access via IMAP
3. Accessing mailboxes configured to allow Less Secure IMAP Access

For each of these, the Google Workspace / GMail settings required are different and are given below

Migration method	Instruction
Migration using the GMail API (recommended)	Follow the instructions given here.
Migration using domain-wide delegation for IMAP	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.
Migration using Less Secure IMAP access	For less secure access via IMAP, follow the instructions given here.

M365/O365

On M365. mailboxes hosted on Outlook can be accessed in two different ways:

1. Delegated API access (recommended)
2. Delegated IMAP access

The steps to prepare for the access is as given below

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.

Preparation for destination server

Before using LegacyFlo to access email data from destination servers using the IMAP protocol, confirm the following

1. Your email service provider supports IMAP access to mailboxes.
2. You should have the rights and the capability to reset the passwords on the destination server in order to access the mailboxes.
3. If the destination 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 destination email service provider should allow large email upload via IMAP without any throttling. 
5. You have configured your email server to allow IMAP access as mentioned in the sections below.
6. For Gmail Servers,

• 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.

7. For O365 servers,

• Need confirmation from the O365 support team that there is no throttling on accessing mail from mailboxes on O365 using the IMAP protocol.
• O365 servers need the following configurations to be done

Provide delegated access to mailboxes on O365	Follow the instructions given here.
Suppress read receipts	Run the following cmdlet Set-ImapSettings -SuppressReadReceipt $false cmdlet
Enable IMAP access for O365 mailboxes	Follow the instructions given here.

 

Migrate data between mail platforms

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

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

REQUEST TYPE	DESCRIPTION
O365-GMAIL-IMAP	Use this request type to import data from a O365 account to GMAIL account (with Less Secure App Access). Click here for the details of the request parameters.
GMAIL-O365-IMAP	Use this request type to import data from a GMAIL account (with Less Secure App Access) to O365 account. Click here for the details of the request parameters.
YAHOO-O365-IMAP	Use this request type to import data from a YAHOO account to O365 account. Click here for the details of the request parameters.
YAHOO-GMAIL-IMAP	Use this request type to import data from a YAHOO account to GMAIL account (with Less Secure App Access). Click here for the details of the request parameters.
YAHOO-OTHER-IMAP	Use this request type to import data from a YAHOO account to OTHER IMAP account. Click here for the details of the request parameters.
O365-O365-IMAP	Use this request type to migrate data from one mailbox to another on O365 using IMAP Click here for the details of the request parameters.