Browse databases, local files, and object storage in one tree. Inspect schemas, run SQL, compare targets, and edit rows inline before you change production workflows.
DBConvert Streams includes free IDE workflows. Add paid migration or CDC runs only when you need them.
Databases, local files, and S3 buckets appear side-by-side in one navigation tree.

Core Feature
Browse, filter, and edit records from connected sources with the same grid workflow.

Only in DBConvert Streams
Run a single SQL query across databases and files — no ETL, no staging.

No ETL pipelines. No staging tables. Query live data across sources in real time. Learn more about Cross-Database SQL →
Inspect columns, keys, indexes, and DDL definitions. Visualize relationships with interactive ER diagrams.


View detailed column information including data types, nullability, defaults, and constraints.
Examine table relationships, key constraints, and referential integrity rules.
Review table indexes, their types, and configurations for performance analysis.
View the complete DDL definition of any database object — tables, views, and more.
Full interactive ER diagrams. Explore relationships with crow's foot notation, force-directed layout, and export to SVG, PNG, or PDF. Learn more about the ER Diagram Tool →
Query CSV, JSON, Parquet, and S3 objects directly as tables.
Powered by DuckDB. Vectorized execution engine for fast analytical queries — even on large Parquet datasets across local files and S3.
Open two data sources side by side to compare schemas, data, and structures visually.
Transition from analysis to migration — create a stream directly from the explorer.

Related workflows
Use the surrounding pages when exploration turns into cross-source SQL, migration planning, or CDC cutover work.
Use the SQL page when the main job is joining multiple databases, files, or S3-backed data in one query.
Use the migration page when exploration turns into snapshot transfer, schema conversion, and cutover planning.
Use the CDC page when the target needs to stay current after the initial load and validation work is done.
Start with the built-in IDE workflows to browse schemas, run validation queries, compare environments, and review targets before you plan migration or CDC.
Add paid stream execution only when the workflow moves into migration or replication.
Read the Database Explorer docs