3,979 templates already exist
Most pipelines are common patterns — Salesforce to Snowflake, Stripe to BigQuery, Postgres to S3. Pick the template instead of rebuilding.
Migrate to Etlworks
Switch from SnapLogic, Fivetran, or Informatica without rebuilding everything.
Most of what you’re moving — Salesforce to Snowflake, Postgres to BigQuery, Stripe to your warehouse — already exists as a template. The rest, Simba can translate. Run both tools side by side until you trust the new one. Cut over when you’re ready.
The hard part
It’s not the new tool. It’s the cutover.
Most migrations stall in the middle. Pipelines partially moved. Two tools running. Nobody trusts the new outputs. Engineering wants to roll back; finance wants to stop paying both.
What makes it faster
Six things that mean you’re not starting from scratch.
Simba translates your old logic
Paste in your existing SQL, JS, or Python — Simba converts it. Or describe what the pipeline does in plain English; Simba builds it.
Schemas are mapped automatically
Point Etlworks at source and destination. Schemas are inferred. Field-by-field mapping that took 3 days takes minutes.
Run both tools side by side
Keep your old platform running while Etlworks runs the same flows in parallel. Compare outputs. Cut over when you’re ready. Roll back any time.
An engineer helps when you need it
For larger migrations or regulated environments, an Etlworks engineer works with your team — full-time if you need it. Bundled into the contract, not a separate bill.
No lock-in on the way out
Flows export as definitions. If you ever need to leave, the cost out matches the cost in. We don’t trap your work.
How a migration works
Five steps. Same shape every time. The whole point is that your old tool keeps running until you choose to turn it off.
Step 1
Assessment
We look at your current pipelines, find the complex ones, and write up a plan. Free, no commitment. You get an honest estimate of effort and risk.
Step 2
Pilot
Move 3–5 pipelines first. Test the edge cases — odd transformations, custom auth, fragile schedules. Make sure Etlworks handles your stack.
Step 3
Parallel run
First wave goes to production. Both tools run side by side. We compare outputs continuously. You cut over when confidence is full — and you can roll back any time.
Step 4
Migrate the rest
Move remaining pipelines in waves. Group by criticality, by source, or by team — your call. Each wave runs in parallel before cutover.
Step 5
Turn off the old tool
When you’re confident, decommission. Cancel the contract. Etlworks runs your full stack.
It can be fast. The public-sector platform from the top of this page moved thousands of pipelines off SnapLogic in two months. Possible because most of their pipelines mapped to existing templates.
From your current tool
Different starting points, different timelines. Honest estimates below.
From SnapLogic
1–2 monthsPipeline definitions translate via Simba. Snaps map to Etlworks connectors and flow types. We’ve moved thousands of pipelines off SnapLogic in production.
Why teams switch: cost · simpler architecture · real-time CDC built-in
From Fivetran
2–4 weeksConnector parity is high — most Fivetran sources have direct Etlworks equivalents. Main work is recreating schedules and replacing transformations.
Why teams switch: escape consumption pricing · gain on-prem option · real-time CDC
From Airbyte
2–3 weeksMost Airbyte connectors map directly. Custom connectors port via Etlworks’s custom API framework. Schedules and schemas translate cleanly.
Why teams switch: production reliability · enterprise support · real CDC engine
From Informatica
6–12 weeksThe hardest case. Heavy proprietary transformation logic, complex orchestration, often hundreds of pipelines. Engineer-led migrations are the norm.
Why teams switch: cost · modern tooling · cloud-native deployment
From Talend
1–2 monthsTalend Studio jobs translate to Composer flows. Talend’s metadata catalog maps to Etlworks’s connections. Stitch integrations port faster than Studio jobs.
Why teams switch: Qlik acquisition uncertainty · simpler licensing · CDC built-in
From Matillion
3–5 weeksIf you’re on Matillion for Snowflake-native ETL, Etlworks’s pushdown ELT covers the same ground. Transformation jobs port via Simba.
Why teams switch: multi-warehouse support · API depth · pricing predictability
From Workato or Boomi
3–6 weeksRecipes or atoms map to Composer flows. Most SaaS-to-SaaS integrations have direct template equivalents. App connectors widely covered.
Why teams switch: data engineering depth · CDC support · self-host option
From custom pipelines
variesAirflow DAGs, cron-driven scripts, custom Python. Simba converts most pipeline logic from natural language description; complex DAGs map to Composer’s nested workflows.
Why teams switch: stop maintaining plumbing · monitoring + audit included
Migrating from something else? Email us — we’ve handled most major iPaaS tools, custom Airflow setups, and legacy ETL stacks.
Get a free assessment
Tell us about your current setup. We’ll send back an honest plan — effort estimate, risk areas, timeline. No commitment.
FAQ
What if Etlworks doesn’t have a connector for my source?
If it has an API, you can build a custom connector in under a day. Etlworks supports REST, SOAP, GraphQL, and OData with all major auth methods. For unusual sources, we’ll build the connector for you as part of migration support.
Can I migrate gradually or do I have to cut over all at once?
Gradually. Most migrations move in waves — pilot first, then production wave one (running parallel with your old tool), then more waves. Big-bang cutovers work for ~20 pipelines or fewer.
How long is the contract?
Monthly or annual — your choice. No multi-year minimums. If you’re switching tools, you don’t want to trade one lock-in for another.
What happens to old data in my current tool?
Etlworks doesn’t need it. New pipelines run on Etlworks; old data stays where you already loaded it. If you need to archive anything from your old tool’s storage before turning it off, we’ll help.
Is there a migration cost?
The assessment is free. Standard migrations (under 50 pipelines) are usually covered by the support hours included in higher tiers. Larger migrations include an engineer who works with you — bundled into the contract.
What if it doesn’t work?
Both tools run side by side throughout the migration. If something doesn’t work in Etlworks, your old tool keeps running that pipeline until it does. You don’t turn the old tool off until you’ve confirmed Etlworks handles your stack.
Can I talk to a customer who already migrated?
Where customer permission allows, yes. We’ll connect you with reference customers who moved from your specific tool. Ask during your assessment.
Ready when you are.
Free assessment. No commitment. We’ll tell you honestly whether Etlworks is the right fit and how long it would actually take.