Open Data Infrastructure Vendor Portability Tests

The worst time to test vendor portability is the week you need to leave.

Portability needs tests

Vendors can support open formats and still make practical portability painful. The data might be readable, while catalog metadata, policy rules, lineage, workload history, and cost controls stay trapped in product-specific structures.

A buyer portability test turns open claims into evidence. It should happen during evaluation, renewal, and major architecture changes, not after the relationship breaks.

What to test

Test table readability through an independent engine, catalog access through an open API, metadata export, policy translation, lineage export, workload replay, cost visibility, and contract language around exit support. Each test should have a pass, fail, or partial result with evidence.

Demand exit evidence early

Ask for a sample table export, catalog metadata export, policy model, lineage event export, workload migration walkthrough, and written exit obligations. If the vendor can demonstrate portability during procurement, the buyer keeps control before the contract becomes dependency.

For related buyer guidance, read ODI procurement scorecards, the ODI buyers guide, and data infrastructure exit strategy.

What breaks first

• The table format is open, but catalog metadata cannot leave cleanly.
• Lineage is visible in the UI but not exported in a usable structure.
• Policies depend on vendor-only identity objects.
• Workloads can be copied, but performance and cost behavior cannot be reproduced.

Buyer questions

Ask the vendor to prove table portability, catalog portability, policy portability, lineage portability, workload portability, and contractual portability. The strongest answer is a working demo with documentation and obligations attached.

Sources to start with

These primary sources anchor the technical claims in this guide.

• Apache Iceberg table specification
• Apache Iceberg REST Catalog specification
• OpenLineage object model documentation
• Apache Polaris documentation

A vendor is portable when the buyer can prove the exit before needing it.