Bring your data contracts with you.
AnomalyArmor speaks ODCS, the open data-contract standard, so your existing rules move without rewriting. Pick your current tool to see the exact import path.
From Soda
Soda does not emit ODCS today, so there is no one-command export. Translate your SodaCL checks into ODCS YAML, paste them into the migration tool to preview every rule, and they apply against your tables after signup.
From Great Expectations
The adapter walks your GE context and translates Expectation Suites into ODCS YAML. Common expectation types map one-to-one; anything it cannot convert is reported as a warning rather than dropped.
armor migrate-from great-expectations ./great_expectations/ > contracts/From dbt tests
The adapter walks the project root and parses every `schema.yml`. Common test types map one-to-one; unsupported tests surface as warnings rather than being silently skipped.
armor migrate-from dbt ./my-dbt-project/ > contracts/From Bigeye
List Bigeye monitors via their API, translate common types to ODCS YAML, and paste into the shared ODCS entry point. Best-effort against public API docs. Test on a handful of monitors first.
From Elementary
Elementary runs on dbt, so the migration path is the dbt one: the adapter translates your `schema.yml` tests into ODCS. Elementary anomaly monitors have no direct equivalent to convert, since AnomalyArmor generates its own baseline.
armor migrate-from dbt ./my-dbt-project/ > contracts/Not seeing your tool?
If your current tool exports any flavor of ODCS YAML, paste it into /migrate/soda. The form accepts any valid ODCS v3.1.0 contract, not just Soda output. For tools without ODCS export, email us and we will document the translation recipe.
Migration