Overview
- The Open Store of Vaultastic Version 4 is where you can upload data files.
- These files can remain on the Open/Deep Store till you download them or copy the data to Active Store for discovery.
- There are multiple ways you can upload data files to the Open/Deep Store. These methods are highlighted in the topic here.
- This topic discusses the method of using LegacyFlo to upload data from mailboxes using LegacyFlo.
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 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.
- If the source server is hosted at your own premises, you have provisioned sufficient Internet bandwidth to transfer the mailbox data.
- 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.
Additional prerequisites
Google Workspace - GMail
LegacyFlo can access GMail mailboxes using 3 methods
- Accessing mailboxes using API (recommended)
- Accessing mailboxes using domain-wide delegated access via IMAP
- 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 |
|
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:
- Delegated API access (recommended)
- Delegated IMAP access
The steps to prepare for the access is as given below
Step | Instructions |
---|---|
| 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. |
Register the S3 bucket on which Open/Deep Store is hosted with LegacyFlo
The S3 bucket on which the Vaultastic Open Store is hosted has to be registered with LegacyFlo (this is a one time activity). For the steps on registration, refer to this article.
Note: For the Open/Deep Store, the first step of bucket creation, policies and permissions is to be mentioned in the article is to be skipped.
Migrate data to the Open/Deep Store
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 table below gives the details of the preparation and request parameters for different source types:
Source: O365/M365
M365API-S3-ZIP |
|
M365API-S3-PST |
|
O365-S3-ZIP |
|
O365-S3-PST |
|
Source: GMail
GMAILAPI-S3-ZIP |
|
GMAILAPI-S3-PST |
|
GMAIL-S3-ZIP |
|
GMAILOAUTH-S3-ZIP |
|
GMAILOAUTH-S3-PST |
|
Other Sources
MITHI-S3-ZIP |
|
YAHOO-S3-ZIP |
|
Retrieve data from S3
You can retrieve the data by accessing the Vaultastic V4 Open store.