Turn your legacy Informatica, DataStage, and SSIS estate into a platform-agnostic blueprint you own forever. Analyze it. Extract end-to-end column-level lineage. Emit to any modern target — on your timeline, with the partner of your choice.
# Canonical IR — derived from m_CUSTOMER_LTV.xml pipeline: customer_ltv version: "0.1" source: kind: relational ref: conn://oracle_crm/CUSTOMERS transforms: - id: filter_active op: Filter predicate: (status == "ACTIVE") - id: compute_ltv op: Project expressions: ltv: Sum(order.total) * Coalesce(segment.mult, 1.0) types: ltv: Decimal(18,4) lineage: out.ltv: ← order.total, segment.mult via: [Sum, Coalesce, Multiply]
Every major ETL migration vendor sells you hours, code, and a one-way door. We sell you a specification-grade representation of your estate that you own forever — and a choice, renewable every year, about what to do with it.
Documentation is stale. Original developers left years ago. Platform-native catalogs capture only surface metadata. No migration decision is defensible without a complete, trustworthy inventory of logic and lineage — and that inventory does not exist today.
Choosing between dbt, Databricks, Airflow, or ADF is a bet that is difficult to reverse. Customers either commit prematurely and regret it, or stall indefinitely and bleed license fees. Both failure modes are expensive.
Column-level lineage lives inside Informatica. Inside Unity Catalog. Inside Purview. Inside Collibra. It does not exist across them. The estate's true lineage spans the whole stack — and nothing owns that span natively.
Source artifacts parse into a lossless Raw IR. A normalizer lowers them into Canonical IR — typed, specified, platform-agnostic. Intelligence runs over C-IR. Emitters produce target artifacts. Everything in between is versioned, diffable, and yours.
You can buy ETLIR for the blueprint alone. Or for the intelligence. Or for the emitters. Most customers start with one and grow into all three. The layers compose — they do not lock in.
A lossless, versioned, neutral Canonical IR repository of your entire ETL estate, living in your own git. Diffable. Reviewable. Portable. The product is valuable even if you never migrate.
Analytics and lineage computed from C-IR expression trees — not scraped from platform metadata. Column-level, cross-platform, pre-migration. Regulator-defensible by construction.
Reference emitters for modern targets plus a stable SDK so your team or your partners can build custom emitters. A certified marketplace for the long tail. You choose the target — and the moment.
The durable value is not the migration. It is a neutral, platform-agnostic representation of your ETL estate — queryable, version-controlled, and enriched with the end-to-end lineage that no platform-bound tool can give you.
Every output column traces back through every transform to its source columns, with the operators applied along the way made explicit. Works across platforms you haven't migrated to yet. Works across parsers. Exports as OpenLineage events or a native graph you can query.
First-party reference emitters ship under an open license. The SDK and conformance harness are open. Commercial and partner emitters extend the catalogue — certified against the same equivalence tests as our own.
| Capability | Services-led migration | Target-sponsored tools | Catalog & lineage platforms | ETLIR |
|---|---|---|---|---|
| Platform neutrality | Delivery-dependent | Biased toward one target | Platform-aware surface only | Neutral by construction |
| Customer-owned asset | Target-specific code | Target-specific code | Metadata inside their platform | Git-native C-IR, yours forever |
| Pre-migration lineage | Manual, partial | Not available | Limited to scraped metadata | Column-level, expression-derived |
| Optionality across targets | Lost on day one | Lost on day one | N/A | Preserved indefinitely |
| Engineering verifiability | Opaque | Closed | Black-box lineage | Equivalence-tested, conformance-suite |
No. ETLIR produces the neutral intermediate representation that migrations are built on top of. You can migrate with it, with a partner, or never at all. The C-IR and the intelligence over it are valuable on their own — most customers buy us long before they commit to a target platform.
Every release ships round-trip and cross-emitter equivalence tests. The conformance suite is public. If a second emitter produces a semantically inequivalent pipeline from the same C-IR, that's a bug we can see. Neutrality is a test, not a claim.
C-IR lives in your git repository as versioned YAML artifacts. You own them. If you stop paying us tomorrow, you still have the blueprint, the specification is open, and reference parsers and emitters are open source. The asset survives the vendor.
Catalogs and OpenLineage operate above the platform layer on metadata surfaces. ETLIR operates below — at the level of transforms and expression trees. We export to OpenLineage, so we complement existing investments. We do not replace them.
Informatica PowerCenter first — mappings, parameter files, connections, sessions, workflows, reusable transformations, and mapplets. IICS, SSIS, and DataStage follow. Community and partner parsers for the long tail are supported by the SDK.
Enterprises with one thousand or more production ETL mappings on a legacy platform, a mandate or intent to modernize, and a regulated or governance-sensitive profile. Financial services, insurance, healthcare, life sciences, utilities, and public sector are the early ideal customers.
We are selecting three to five design partners for the first wave. Regulated industry, serious Informatica footprint, data leadership committed to a modernization answer within twelve months. If that's you, we should talk.