ETL & ELT
ETL and ELT describe the two dominant patterns for moving data from source systems into a destination for analysis.
ETL stands for Extract, Transform, Load. Data is pulled from source systems, transformed in a dedicated processing layer, and then loaded into its final destination — often a data warehouse. This pattern has been the default approach for decades.
ELT stands for Extract, Load, Transform. Data is extracted and loaded into the destination first, in a mostly raw form, and transformation happens afterward using the destination's own processing power. This pattern has grown popular alongside modern cloud data warehouses.
Neither pattern is universally 'better' — the right choice depends on your data volume, the power of your destination system, compliance requirements, and how quickly you need transformed data available.
When to Use Each Pattern
Practical guidance for choosing between ETL and ELT.
Choose ETL When...
You need strict validation before data lands, or your destination has limited compute.
Choose ELT When...
You use a modern cloud warehouse with strong compute and want raw data preserved.
Hybrid Approaches
Many teams blend both, loading raw data first then applying staged transformations.
Common ETL/ELT Building Blocks
Most implementations share the same conceptual components.
- Extraction connectors for APIs, databases, and files
- A staging area for raw or semi-processed data
- Transformation logic written in SQL or Python
- A scheduler or orchestrator to run jobs reliably
- Monitoring and alerting for failed or delayed loads
ETL & ELT — Common Questions
Quick answers to frequent questions on this topic.
Related Guides
Continue building context around this topic.
Data Engineering
Understand the broader discipline behind ETL and ELT pipelines.
Data Pipelines
See how ETL/ELT steps fit into a full pipeline architecture.
Data Warehousing
Learn how transformed data is modeled once it reaches the warehouse.