Prompt
Should I use dbt if I only need to move data, not transform it?
Latest observation
Oct 8, 2026
OpenAI APIWeb search: off
Usually, no—if you only need to move data and don’t need SQL-based transformation, dbt is probably not the best fit.
Use dbt when you need:
- Transformations in SQL
- Model dependency management
- Testing and documentation
- Version-controlled analytics engineering workflows
- Building a warehouse transformation layer
Don’t use dbt when you only need:
- Simple extraction/loading
- Replication or syncing
- ETL/ELT orchestration without transformations
- Moving files/records between systems
Better tools for pure data movement:
- Fivetran / Airbyte / Stitch for connectors and syncing
- Kafka / Debezium / CDC tools for streaming or change-data capture
- Meltano for open-source extraction/loading
- Custom scripts / Airflow / Dagster if you need control over the pipeline
- Cloud-native services like AWS DMS, GCP Dataflow, Azure Data Factory
A practical rule:
- If your main work is SQL models and transformations in the warehouse → dbt
- If your main work is getting data from A to B → use an ingestion/movement tool
If you want, I can help you choose between dbt, Airbyte, Fivetran, Airflow, or a custom pipeline based on your exact setup.