For migrators (consultants/SIs), the pitch is MAAP: Migration as a Product. Instead of delivering a one-time migration, they deliver a compounding governance asset. ARCXA makes the Day 2 audit deliverable nearly automatic, which is both a risk reducer and an upsell — recurring catalog maintenance powered by the same triple store.
For integrators, NNX is a composable middleware layer. Position it as a lineage sidecar that works alongside whatever orchestration they already use — Airflow, dbt, Fivetran. The open exchange format means they're not locked into a vendor graph, and they can sell clients on owning their own migration intelligence.
For developers, the triple-store angle is the unlock. Every migration event becomes a queryable graph node — subject (source schema), predicate (relationship/transform type), object (target schema). This means lineage isn't a report you write afterward — it's a queryable artifact your pipeline produces automatically. Lead with the REST/SPARQL API and the "knowledge compounds" angle: the more migrations ARCXA processes, the smarter your next one starts.
No comments:
Post a Comment