# Load Data with SingleStore Flow on Helios

> **📝 Note**: This is a Preview feature.

## Overview

SingleStore Flow (or, "Flow") is SingleStore's data migration and change data capture (CDC) solution which is comprised of two primary components:

* **SingleStore Ingest**, also referred to as "Ingest," transfers the schema for all tables, moves table data for tables up to 10GB in size, and handles ongoing CDC for all tables into SingleStore.
* **SingleStore XL Ingest**, also referred to as "XL Ingest," handles the initial transfer of large tables by breaking them into smaller logical partitions. It then copies multiple partitions from the source to the target in parallel. This helps transfer large tables efficiently, and is resilient to network outages and restarts of Flow, the source, or the destination.

Flow is integrated into the [Cloud Portal](http://portal.singlestore.com/) under **Ingestion** > **Load Data**. This service enables loading and synchronizing data from supported databases into SingleStore, without the need to install or manage any infrastructure.

Flow supports the following source databases for transfer to SingleStore:

* Oracle
* Oracle RAC
* Microsoft SQL Server
* MySQL
* PostgreSQL
* Snowflake
* Any JDBC-compliant database (non-production preview, available for testing)
* MongoDB® (private preview)

## Why Use SingleStore Flow

Key benefits of using SingleStore Flow:

* **No-code setup**: Configure end-to-end migration via the Flow UI.
* **Automatic schema handling**: Analyze the source database and automatically create the required schema in the target SingleStore database.
* **Real-time visibility**: Monitor progress, view live logs, and troubleshoot quickly.
* **High throughput**: Use XL Ingest to parallelize large table loads by chunking source data, significantly reducing migration time.

## Choose the Right Flow Deployment

Flow is available in two deployment options:

* A Self-Managed Flow Application
* Flow on Helios

Both provide the same data migration and CDC features, but differ in how they are deployed and used.

The following table outlines these two options:

| Deployment Option | Self-Managed Flow Application                                                                                                                                                                                                                                                                 | Flow on Helios                                                                                                                                                                                                                                                                              |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Description**   | <ul> <li>Installed and operated in your own environment.</li> </ul><ul> <li>Self-managed, installation required.</li> </ul><ul> <li>Provides control over where the application runs and how it integrates with your system.</li> </ul>                                                       | <ul> <li>Runs in the SingleStore Helios cloud deployment.</li> <li>Fully managed by SingleStore, no installation required.</li> <li>A Flow instance is provisioned directly from the UI, and usage is billed only while the instance is running.</li> </ul>                                 |
| **When to Use**   | <ul> <li>When deployment placement or control over environment matters the most, such as replicating large volumes of data from an on-premises source to SingleStore. This is because Flow performs best for high-volume transfers when its services run close to the data source.</li> </ul> | <ul> <li>When your data sources and destinations are in the same cloud region, along with your Flow on Helios instance, ensuring excellent performance along with convenience and robustness.</li> <li>When convenience and low operational overhead matter more than placement.</li> </ul> |

For more details on the Self-Managed Flow application, refer to [Load Data with SingleStore Flow](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow.md).

## In this section

* [Flow on Helios Sizing Guidelines](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/flow-on-helios-sizing-guidelines.md)
* [Use Flow on Helios](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/use-flow-on-helios.md)
* [Scale a Flow Instance](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/scale-a-flow-instance.md)
* [SingleStore Ingest](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/singlestore-ingest.md)
* [SingleStore XL Ingest](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/singlestore-xl-ingest.md)
* [Data Type Mapping in SingleStore Flow](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/data-type-mapping-in-singlestore-flow.md)
* [Flow on Helios API](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/flow-on-helios-api.md)
* [Flow on Helios FAQ](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/flow-on-helios-faq.md)

***

Modified at: May 11, 2026

Source: [/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/](https://docs.singlestore.com/db/v9.1/load-data/load-data-with-singlestore-flow-on-helios/)

(An index of the documentation is available at /llms.txt)