DirectSync | Desktop App and CLI for Data Sync

See it in action

Watch a short walkthrough of DirectSync configuring a sync and running it end-to-end.

Or watch it on YouTube.

How it works

Pick source, set target, define mapping — run in the app or deploy with the CLI.

1

Configure source

Choose source type: database (SQL Server, PostgreSQL, MySQL, Oracle, etc.) or file (CSV, Excel, JSON, XML, Parquet). Connection and format options are validated.

2

Configure target

Set the target — database or file. Configure table, insert/merge behavior, or output path and format.

3

Mapping & transformation

Map source columns to target columns, rename and adjust types. Use options like distinct, merge strategies, and transformations.

4

Run or export

Execute in the app or export configuration as JSON. Run the same pipeline with etlrun directsync --config <path> on Windows, Linux, in containers, or in the cloud.

Impressions

See how DirectSync looks in action.

Features

Simple to configure, powerful to run — database and file sync, streaming engine, and a CLI that runs anywhere.

Database & file sync

Sync between databases, database to file, or file to database. Staging to warehouse, CSV/Excel/JSON into tables, or export from DB to files.

Streaming engine

ETLBox processes in stream: large datasets without full memory load, with pipeline-based throughput.

Mapping & transformation

Map columns, rename, adjust types. Distinct, merge options, and extensible transformation rules.

Error handling

Configurable error destination: redirect faulty rows to file or table; rest of the run continues.

CLI & automation

Export as JSON and run with etlrun directsync --config <path> on Windows, Linux, in containers, or in the cloud.

Data preview

View first rows of the source in the app, sort and filter — verify connection and parsing before running.

Manual vs. DirectSync

One configuration in the app — deploy the same pipeline anywhere with the CLI.

Manual / scripts

Without DirectSync

Script maintenance: Custom ETL scripts per source/target, hard to reuse.
No single model: UI and batch often separate, double configuration effort.
Memory load: Large datasets can push custom solutions to their limits.
Error handling: Often all-or-nothing — one bad row stops the run.

ETLBox DirectSync

With DirectSync

One configuration: Configure in the desktop app — same config for the CLI and automation.
Streaming engine: ETLBox processes in stream — no memory issues even with large data.
Error destination: Redirect bad rows; rest of the pipeline keeps running.
Deploy anywhere: Run etlrun directsync on Windows, Linux, containers, Azure.

FAQ

Answers about DirectSync, data sources, and automation.

What data sources and targets are supported?

DirectSync uses the ETLBox engine: databases (SQL Server, PostgreSQL, MySQL/MariaDB, Oracle, DB2, Snowflake, SQLite, SAP ASE, and more) plus files (CSV, Excel, JSON, XML, Parquet). Source and target can be combined freely.

What are the technical requirements?

The desktop app runs on Windows. The CLI (etlrun directsync) is .NET-based and runs on Windows, Linux, in containers, and in the cloud — use it for CI/CD, scheduled tasks, or Azure.

How are large datasets handled?

ETLBox works in a streaming way: data is not fully loaded into memory but read, transformed, and written in pipelines. That allows reliable processing of very large datasets.

Can I reuse configurations?

Yes. Configure once in the desktop app and export as JSON. Run the same pipeline with etlrun directsync --config anywhere — ideal for repeated or automated runs.

What happens when errors occur during execution?

You can enable an error-destination option: problematic rows are redirected to a file or target of your choice without failing the whole run.

Powered by ETLBox

The surface for the library you already trust

DirectSync is the Windows desktop and CLI front end for ETLBox. Configure visually, then run the same pipeline anywhere .NET runs.

Visit ETLBox

Get started for free

Download DirectSync

Get the free version for Windows. Use the desktop app for migrations, testing, and development — then deploy with the CLI anywhere.

Windows (MSIX)

Version 1.X