Coming from Soda? Paste your ODCS YAML here.

Same rules, same alerts, zero rewrite. AnomalyArmor speaks the same ODCS dialect Soda exports, so your migration is a paste, a preview, and a sign-up.

1

Translate your checks to ODCS

Soda has no ODCS export command, so this step is manual: rewrite your SodaCL checks as an ODCS v3.1.0 contract. Most check types have direct equivalents. If you also run dbt or Great Expectations, those have real adapters: armor migrate-from dbt and armor migrate-from great-expectations.

2

Paste the YAML here

Drop the file or paste the contents below. We run a structural preview in the browser. Your contract never leaves your machine until you sign up.

3

Sign up to apply

Create your AnomalyArmor account and the same YAML lands in an apply review with plan preview, diff, and prune controls inherited from the in-product import flow.

Paste ODCS YAML, or drag a file

What happens on sign-up

The same YAML is carried to your in-product import view. There, AnomalyArmor runs full ODCS JSON Schema validation, shows a per-asset plan preview, and applies transactionally with rollback on any domain failure. No half-applied contracts. If you leave, your export is portable back out: the YAML in, the YAML out.

Frequently Asked Questions

The paste-and-apply half takes under 30 minutes. The work before it is translating your SodaCL checks into ODCS YAML, because Soda does not ship an ODCS export. Once you have the YAML, paste it into the migration tool on this page and sign up; the authenticated import flow applies every rule against your tables automatically.