Why Classic ETL Often Falls Short for AI Agents — and Why ELT Is Gaining Ground (Data Integration 2026)
In late March 2026, a Hacker News post about Grafeo — a new embeddable graph database — sparked a discussion about what modern data infrastructures need to fulfill for AI systems.
Traditional relational databases alone don't fully cover many agentic requirements — especially for unstructured data, semantic search, and complex relationship models. Graph structures, vector databases, semantic layers: these are no longer hype technologies but relevant building blocks for many AI deployments.
DACH enterprises building their AI strategy while their data pipelines are stuck in the ETL paradigm often lack the optimal foundation for scalable AI applications.
Where Classic ETL Reaches Its Limits with AI Agents
Five areas where the ETL paradigm is often less suited for agentic AI requirements:
- Schema-first vs. schema-flexible — ETL requires a defined schema. AI agents need schema flexibility for unstructured documents, variable JSON, email text. Rigid ETL pipelines often react poorly to unexpected field structures or schema changes.
- Batch vs. real-time — ETL was designed for nightly batch runs. An AI agent responding in real time to a customer inquiry needs data from now, not last night.
- Pre-transformation vs. on-demand query — ETL pre-transforms all data according to predefined rules. AI agents ask ad-hoc questions no one foresaw — combinations that are harder to pre-transform for many agentic use cases.
- Centralized logic vs. agent-native data access — In ETL, transformation logic lives in the pipeline. In agentic architecture, logic lives in the agent — making direct, flexible data access more important than pre-built reports.
- Monolithic pipelines vs. modular-composable layers — ETL pipelines are often tightly coupled. Agentic AI architectures benefit from modular, independent data layers that can evolve without cascading dependencies.
A Practical Data Stack for AI Agents
A practical approach combines four layers:
- Data Lakehouse (Snowflake, Databricks) — A suitable foundation for many modern AI-adjacent data architectures. Both providers offer EU regions and residency options; specific compliance and governance requirements should still be verified case by case.
- ELT transformation (dbt + Airbyte) — Airbyte offers a broad connector landscape for raw data ingestion. dbt transforms data on-demand with versioned SQL models and automated tests.
- Vector and semantic layer — Enables similarity search and business-metric accessibility for AI agents without SQL knowledge.
- Graph layer (optional) — Graph databases can be particularly useful when relationships, dependencies, and knowledge structures are central to the use case.
Migration Path: From Legacy ETL to Modern ELT
Phase 1: Parallel operation (3–6 months) — New ELT for new use cases while legacy ETL continues for existing reports.
Phase 2: Incremental migration (6–18 months) — Migrate ETL pipelines to dbt models one by one, starting with least critical, securing each with tests before decommissioning the legacy pipeline.
Phase 3: Build agentic layer (parallel) — Vector layer and semantic layer for AI agents can be built during migration. First agents can already access new ELT data before full legacy migration.
Ai11's Data Integration Framework
We guide DACH enterprises on this path — from current-state assessment to production agentic data architecture.
Learn more about our Data Integration service
Is your data stack still heavily ETL-centric? Let's assess this together.