Get Started with DBConvert Streams

Choose the path that matches your job: explore first, run a load workflow, or evaluate CDC with Initial Load + CDC when supported.

Desktop Install Docker Install

Starting Paths

Pick the first path that matches the work

The product setup is shared, but the first useful step depends on whether you want hands-on validation, a one-time migration test, or a CDC trial.

Explore first

Best starting point if you want hands-on product context before you commit to migration or CDC.

Install DBConvert Streams and stay in the built-in explorer workflow
Create connections and inspect schemas, rows, and queries
Use this path before any stream configuration

Open desktop install

Run a migration test

Use this when the goal is one-time migration, schema conversion, and pre-cutover validation.

Connect source and target systems
Validate structure and data in the explorer first
Create a Load stream and use Resumable Load when the path is eligible

Open Load setup

Start CDC evaluation

Use this when the goal is ongoing MySQL or PostgreSQL replication after initial validation, with CDC-only or Initial Load + CDC depending on the rollout.

Connect source and target systems
Confirm initial target state before streaming changes
Create a CDC stream and choose CDC-only or Initial Load + CDC when supported

Open CDC setup

Install

Choose how you want to install

The product workflow is the same after install. Pick the deployment method that fits your environment, then continue with the shared onboarding flow.

Desktop Install

Use local installers for Windows, macOS, or Linux.

Fastest path for individual setup
Local app with the same product workflow
Good fit for evaluation and first-run validation

Docker Install

Run the product in your own server or team environment.

Install with the Docker setup script
Use the same UI and onboarding flow after install
Good fit for shared and production-adjacent environments

Shared Flow

Shared onboarding after you pick the path

Install, connect, and validate are common to every workflow. The difference comes when you move into explorer-only work, Load, or CDC.

Step 1

Install

Choose Desktop installers or Docker deployment
Finish setup and open the app UI
Continue with the same onboarding flow after install

Step 2

Create connections

Add source and target connections
Test and save each connection
Reuse them later in Explorer and streams

Step 3

Explore data

Browse objects in the tree view
Open rows and inspect table structure
Edit data or run SQL when needed

Step 4

Create streams

Open stream configuration
Choose Load or CDC
For CDC, decide between CDC-only and Initial Load + CDC when the target is empty
Set scope and start the workload

Step 2

Create connections

Add the source and target connections you will use for Data Explorer, migration, and CDC. This step is the same in the desktop app and the Docker deployment.

Add PostgreSQL, MySQL, files, or S3 connections from one setup flow
Test and save reusable source and target connections before stream setup
Use those saved connections later in Data Explorer and stream configuration

Step 3

Explore and validate data

Use Data Explorer to browse objects in the tree, open table data, inspect structure, edit rows when needed, and run SQL when you want deeper validation.

Browse schemas, tables, views, and other objects in the left tree
Open table data and structure without writing SQL first
Use editing and SQL workflows only when you need deeper validation

Explore Data Explorer Workflows

Optional: bring your AI. The connections you just created are instantly readable by Claude, Cursor, or Copilot — open the ✨ AI Assistants panel and click Connect. AI assistants via MCP →

Step 4

Create your first stream

After your connections and validation are ready, open stream configuration and choose the mode that fits the job: Load for one-time migration or CDC for ongoing replication.