Migrate from Legacy ETL tools

Informatica, SSIS and Talend to Databricks

Informatica, SSIS, Talend

Cover illustration: Informatica, SSIS and Talend to Databricks
Short answer

Moving from Informatica, SSIS or Talend to Databricks turns GUI mappings into pipelines as code, with version control, tests and lineage in Unity Catalog, and removes a separate ETL licence.

What we move

Mappings, workflows, schedules and transformation logic

Value after the move

  • Fewer tools and licences to manage
  • Pipelines as code with version control and tests
  • Lineage from source to report in Unity Catalog

How Legacy ETL tools maps to Databricks

Each component has a clear target on the Databricks Data Intelligence Platform.

Legacy ETL toolsDatabricks
Informatica PowerCenter mappingsLakeflow Declarative Pipelines
Informatica workflowsLakeflow Jobs
SSIS packagesPipelines and Jobs
Talend jobsPipelines and Jobs
ETL connectorsLakeflow Connect
ETL lineageUnity Catalog lineage

How we run the migration

  1. Assess

    Inventory every table, job, report and user. Map dependencies, find what is unused, and estimate effort and cost.

    Output: Migration assessment and business case
  2. Plan

    Design the target lakehouse, governance and security. Group workloads into waves by value and risk.

    Output: Target architecture and wave plan
  3. Convert

    Convert SQL and ETL with LakeBridge and our accelerators, then review and test the output.

    Output: Converted, tested code per wave
  4. Reconcile

    Run old and new side by side and compare results table by table until they match.

    Output: Signed-off reconciliation reports
  5. Cut over and optimize

    Move users in waves, retire the old system, then tune cost and performance.

    Output: Decommission plan and FinOps baseline

We use Databricks LakeBridge for profiling, code conversion and reconciliation, alongside our own accelerators and engineer review of every critical path.

Go deeper

FAQ

Informatica, SSIS and Talend to Databricks: FAQ

Do we lose visual design when moving away from an ETL tool?

Pipelines become code, which is easier to test and version. Lakeflow Designer also offers a visual way to build pipelines for analysts.

Other migration paths