What changes for you
Keep validation inside the operational workflow.
Validation is a planned post-load stage alongside index, sequence, and foreign-key work rather than an unrelated manual exercise.
Correctness · Validation
Finish the load with evidence, not assumption.
Omni Loader can run count, table-hash, or record-level validation after loading so the migration result is reviewed through explicit checks.
Migration proof Read · calculate · compare
Checks running
Inputs
Source snapshotREADY
Validation policyREADY
Target snapshotREADY
Validation engine Read · calculate · compare
Outputs
Row countsREADY
Table hashesREADY
Record comparisonREADY
Why this path matters
Match evidence to risk and target capability.
Select no validation, count comparison, table hashing, or record comparison per project and table according to the migration’s assurance needs.
The payoff
See what the capability changes.
Count
Coverage check
Compare the number of source and target records.
Hash
Table-level evidence
Use target-supported hash comparison for a stronger signal.
Record
Detailed comparison
Inspect value-level differences where supported.
Where the work happens
The details that make the result usable.
At a glance
A visual summary of the work.
Reviewable outcomes
Bring differences back to the operator.
Run history, table status, warnings, errors, and comparison views keep validation results attached to the migration run.
Take the next step
Define the proof before the migration starts.
Choose count, hash, or record-level validation by table and target capability.
Plan my migration