Migrate from Matillion to DLH.io
Move ingestion to DLH.io and turn Matillion transformation jobs into version-controlled dbt models. Our team rebuilds the pipelines, runs both side by side until the numbers match, then helps you cut over.
Today
After
Same tables in your warehouse. One predictable bill.
Why teams leave Matillion
Credits are hard to forecast
Consumption-based credits rise with job runtime and frequency, so the bill moves every time you add a source or run more often.
Logic is locked in visual jobs
Transformation logic lives in drag-and-drop jobs that are hard to diff, review, and test the way the rest of your code is.
A platform move is coming anyway
If you are on Matillion ETL and facing a move to its newer cloud platform, that is the moment to compare all your options.
How we move you off Matillion
Five steps, led by our team. Nothing is switched off until the new pipelines are proven.
- 01
Assess
We inventory your Matillion pipelines: sources, synced tables, schedules, destinations, and the models and reports that read from them.
- 02
Map
Each pipeline is matched to a DLH.io connector or agent, with table and column mapping written down before anything is built.
- 03
Rebuild
Our team configures the DLH.io pipelines and destination schemas, and loads history from your sources.
- 04
Run in parallel
Matillion keeps running while DLH.io loads the same data. We reconcile row counts and key totals until they match.
- 05
Cut over
Point your models and reports at the DLH.io tables, then retire Matillion. No downtime, and you switch only when you're sure.
What moves, and who does the work
We rebuild for you
- Ingestion jobs as DLH.io connectors, including CDC from SQL Server and Oracle
- Destination schemas and table structures
- Job schedules and run frequency
- Historical loads from each source
We finish with your team
- Converting transformation jobs into dbt models, managed in DbDeux if you choose
- Source and warehouse credentials, IP allowlisting, or SSH tunnels
- Orchestration steps such as API calls or notifications inside jobs
- Sign-off on the reconciliation before cutover
DLH.io vs Matillion at a glance
| DLH.io | Matillion | |
|---|---|---|
| Pricing model | Flat $2,499/month on DLH Enterprise | Consumption-based credits |
| Data volume | Unlimited, with no row counting | Cost rises with job runtime and frequency |
| Transformations | dbt models in Git, managed through DbDeux | Visual transformation jobs |
| Connectors | 200+, with deep POS, payroll, HR, and ERP coverage | Prebuilt connectors plus custom API builders |
See every plan on the pricing page.
Get a free migration assessment
Share an export of your Matillion jobs and a recent bill. We send back a migration plan: what we rebuild, what your team touches, a timeline, and your cost on DLH.io side by side with what you pay today. No commitment.
Matillion migration FAQ
Ready to move off Matillion?
Keep your warehouse and your reports. Get transformation logic into code you can review.