DecisionManager
Start a trial

ODM Migration

Not a one-shot import. A full migration governance workflow.

The Migration Runs workspace handles real IBM ODM migrations: persistent runs, per-artifact review queues, scenario replay for behavioral equivalence proof, and migration certificates for risk reviewers. ODM keeps taking hotfixes mid-migration. The platform handles that without reopening already-reviewed artifacts.

Start free trial Migration overview

Six challenges. Six answers.

✗ODM keeps taking hotfixes mid-migration
Re-upload at any point. Only new/changed artifacts re-open for review.
✗No behavioral equivalence proof
Scenario replay: real decisions through both versions. Changed output keys reported per scenario.
✗Risk reviewer needs audit artifact
Migration certificate: source count, review dispositions, replay results, approver chain.
✗20,000 rules can't be reviewed at once
Per-artifact review queue. Filter by status, type, package, reviewer.
✗ODM rule inheritance chains
AI gap analysis identifies inheritance patterns in the analyze report before conversion.
✗Direct import loses governance trail
Migration runs are persistent objects. Every review action is timestamped and attributed.

Six-step migration lifecycle

01

Upload ODM export

Upload a .zip of the ODM project export. The analyzer reports artifact counts, structural patterns, and potential conversion challenges.

02

AI gap analysis

POST /odm/assist identifies inheritance chains, date arithmetic idioms, and XOM patterns that need attention. Grounded in the analyze report — no invented rules.

03

Per-artifact review queue

One review row per source artifact. Each artifact shows: source BAL, converted BAL, structural diff, and AI explanation. Reviewer accepts, modifies, or rejects.

04

Scenario replay

Run real recorded decisions through both ODM (original) and DecisionManager (converted). Changed outputs and rule churn reported per scenario.

05

Migration certificate

Source artifact count, review disposition per artifact, replay equivalence verdict, and the approver chain. The artifact the risk reviewer reads.

06

Promote to production

Publish the migrated versions through the standard governance lifecycle (draft → in_review → approved → published). The migration run stays as a permanent audit record.

ODM migration process comparison

DimensionIBM ODM MigrationDecisionManager Migration Runs
ScopeOne project, exported before migrationAll projects, live during migration
Hotfix handlingManual re-merge into migration branchRe-upload — only new/changed re-opens
Equivalence proofManual test comparison, no systematic reportScenario replay — deterministic, per-output-key
Governance trailEmail threads, Confluence pagesPer-artifact review records, timestamped, attributed
Risk reviewer artifactManual PDF, written by migration leadMigration certificate generated from live records

Ready to start your ODM migration?

Upload your ODM export and get a gap analysis within minutes. No infrastructure required. No commitment.

Start free trial Read the migration guide