FAQs LegacyFlo

FAQS LegacyFlo

What can I do with the LegacyFlo application?

Using the LegacyFlo application, you can upload historical email data from live mail boxes or available in files such as PST/EML/MBOX into Vaultastic or SkyConnect mailboxes. 

For a overview of the process of uploading historical email data to Vaultastic, refer to www.vaultastic.com/migration.

How do I get an account on the application?

An account on the LegacyFlo application will be automatically created for you when you sign up for Vaultastic. The credentials will be shared by email on the email id used to sign up for Vaultastic.

What are the different request types supported?

The different job types supported as are per the table below:

PST To migrate data stored in PST files
EML To migrate data stored in EML files
MBOX To migrate data from MBOX files
IMAP To migrate data using IMAP protocol
O365IMAP To migrate data using the O365 IMAP protocol
GMAILIMAP To migrate data using the GSuite IMAP protocol
EXCHANGEIMAP To migrate data using the MS Exchange IMAP protocol

Can I perform Bulk operations?

Yes. You can perform the following Bulk operations:
1. Add jobs
2. Verify Jobs
3. Start Jobs
4. Delete Jobs

What are the request parameters?

The parameters for a job depend on the job type.
For example, for jobs which migrate from data files having PST, EML or MBOX data, you have to specify the file co-ordinates and the details of the account to which the data has to be migrated.
For jobs which collect data from IMAP servers, the job details will include the access credentials of the IMAP account and the account to which the data has to be migrated.

How do I create a CSV for defining multiple requests?

The input parameters depend on the Job type. Refer to the table below for the details of the CSV for your job

Can I import historical data after I have started live email archiving?

Yes. In fact, this is a highly recommended approach in which we suggest that you start archiving the moment you are on-boarded so all mail from that moment on are safely secured. After that you can work out a migration strategy, which includes what data to migrate, which users to target first, what methods to use and so on. You may also have to create a team to plan, supervise and execute on this. Importing historical data does not interfere with the live archiving.

Is there any limit on the amount of historical data I can upload?

Upload of historical data is available only the users who have subscribed to the HOLD plan of Vaultastic.

The HOLD plan is billed as per the storage consumed, which means that you can upload any amount of historical mail data belonging to that user's vault. You will be billed for holding the data at the rate per GB of the HOLD plan.

How do I know when a request is complete?

When a job is complete, either successfully or it fails, a mail will be sent to you with the details.

What are the different stages in the upload process and how long will it take in each stage?

The table below shows the different stages of the process. These stages are highlighted in the Status column.

The meaning and the estimated time in each stage is given in the table below:

Pending A newly created job is in the Pending stage. It will move from this Stage to the submitted, only when the admin clicks the Start or Start All button.
Verifying A job moves into this stage when the admin clicks on Verify or Start. In this stage the job parameters are validated.
Invalid A job with invalid parameters is moved to the Invalid stage after the Verifying stage

A verified job moves to the the Submitted stage. Here the job enters a queue of jobs that are to be scheduled. A job will remain in the submitted phase until it can be scheduled for processing which in turn depends on the number of jobs in the submitted, scheduled or processing stage.

The number of jobs than can be scheduled concurrently, is controlled by a threshold value. For example, if the threshold is 5, only 5 simultaneous jobs can be running. Therefore, the time to move to the next stage will depend on the number of jobs being currently executed. If the number of running jobs have reached the threshold, then your job will be submitted once the running jobs and the jobs in the queue before yours have completed.


A job in the Scheduled phase is just waiting on the resources to start processing and will start in 1 - 15 minutes. 

When a job moves to the processing state, an email notification is sent to the email id specified in the job definition.


A job in the Processing stage is processing the input data and converting it into Vaultastic data. The time the job will remain in this stage depends on the size of the job and the method of migration.

Typically, an IMAP job will migrate 3 GB / hr, migrating from a PST/EML or MBOX file from a S3 bucket will have a rate of 600 MB/ hr.



A job in the processing state may get suspended and be automatically re-submitted for processing. 

This happens when the resources allocated for the job are re-allocated to another higher priority job. 

Once the job is re-submitted, it will have to wait for resources similar to a submitted job. 

Once the resources are available, the job will move to the scheduled state and then the processing state. 

In the processing state, the job will resume from where it was suspended.

This whole flow is automatic and no intervention required from you.

Processed A job which has completed successfully will be in the Processed stage. A mail with the details will be sent.
Failed A job which terminated with failures. Details of the failure will be sent by email. Such a job can be resubmitted.

Can I cancel a running request?

No, a job once started cannot be canceled.

Can one organization have more than one account on the application?

A single account is created for each organization. Using this account, the administrator can submit multiple upload jobs. Only the jobs submitted by the user will be visible on subsequent logs. It is therefore not advisable to have more than one account as the jobs will be split across the accounts and it will be difficult to monitor the overall status.

My request on the LegacyFlo portal failed. How do I recover?

If your request fails, then the error message can be seen by hovering over the "i" icon next to the status.
The table below gives the error messages and descriptions, including the steps to be taken to re-submit the the job.

  • The authentication to the source server failed.
  • This error occurs if the username, domain name or password provided to connect to the source is incorrect.
  • To retry, correct the job parameters using the LegacyFlo app and resubmit the job.
  • The application could not connect to the source server.
  • This error occurs if the source server IP or DNS name provided is incorrect or unreachable.
  • To retry, correct the job parameters using the LegacyFlo app and resubmit the job. If problem persists, try after some time or contact Mithi customer support at support@mithi.com.
  • The authentication to the destination server (either a Vaultastic or SkyConnect server) failed.
  • This error occurs if the username, domain name or password provided to connect to the destination is incorrect.
  • To retry, correct the job parameters using the LegacyFlo app and resubmit the job.
  • The application could not connect to the destination server.
  • This error occurs if the destination server IP or DNS name provided is incorrect or unreachable.
  • To retry, correct the job parameters using the LegacyFlo app and resubmit the job. If problem persists, try after some time or contact Mithi customer support at support@mithi.com.
Internal server error

One possible cause of this error is that the source or destination password of the account contains a double quote character("). Change the password and re-execute the job.

If the problem persists, contact Mithi customer care at support@mithi.com.

How do I use LegacyFlo with internal servers with restricted IMAP access?

LegacyFlo is used to migrate email data from other mail systems to SkyConnect or Vaultastic.

There are two ways to do this. One is to extract data from the source mail systems in EML or PST format, which is then given as input to LegacyFlo.

The second way is to access the accounts on the source mail system using IMAP.

However the IMAP ports of source mail server may not be accessible to world. In which case Mithi will set up a secure NATing server to NAT a public IP to the internal mail server. The public IP of this NAT server can be used to securely access the IMAP accounts on the internal mail server

This document describes the steps and responsibilities of the setup.

Step 1: Share the details of the internal mail server with Mithi to setup the NAT.

Step 2: The Mithi team will configure the NAT server. The configuration depends on whether you will be accessing the Mithi services over VPN or over the Internet. Typically the configuration will take about 3-5 working days, after which the team will share the IP address of the NAT server.  For connectivity over the Internet, this will be a Public IP. For connectivity over the VPN, this will be the private IP.

Step 3: The corporate firewall will have to be updated by you to allow access from this Public/Private IP address to the internal mail server on the IMAP and IMAPS ports.

Step 4: Mail migration using LegacyFlo.
In the IMAP requests submitted to the LegacyFlo system, the Server in the Source Information has to be the Public IP address of the NAT server.

FAQs Documentation

How can i get a offline copy of the user/admin guide?

Mithi docs allows you to export a specific article to a PDF file. 

Navigate to the required article in the list and click the PDF icon in the top pane. PDF file will be displayed on the screen. Download to save and print the file on your machine.

Please note, internal/external hyper links embedded in the article will be visible in the exported PDF file but the videos will be excluded.