Load Data with SingleStore Flow
On this page
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 efficient transfer of large tables, and is resilient to network outages and restarts of Flow, the source, or the destination.
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 Flow
Key benefits of using 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 |
|
|
When to Use |
|
|
For more details on Flow on Helios, refer to Load Data with SingleStore Flow on Helios.
In this section
Last modified: October 6, 2025