What changes for you
Configure key selection and equality behavior for types where formatting, precision, or target representation require deliberate tolerance.
Omni Loader reads sorted source and target snapshots, writes durable added, changed, and deleted difference artifacts, and can apply inserts, updates, and deletes as a controlled repair step.
The job to be done
A large migration is not finished when the first rows arrive. Omni Loader keeps parallel work productive, adapts the loading path to the target, and records enough progress to recover the part that failed.
Readers sort by the selected key, stream both sides, and classify rows as additions, changes, or deletions while writing reviewable difference files.
Why this path matters
Readers sort by the selected key, stream both sides, and classify rows as additions, changes, or deletions while writing reviewable difference files.
What changes for you
Configure key selection and equality behavior for types where formatting, precision, or target representation require deliberate tolerance.
The outcome
Compare complete source and target views, review durable difference artifacts, and decide when repairs should be applied.
The payoff
Classify differences instead of reporting one opaque mismatch.
Review comparison output independently of the live readers.
Choose whether detected differences should modify the target.
Where the work happens
Read each capability as part of the operating path. The important question is not whether a feature exists, but what work it removes and what evidence it leaves behind.
At a glance
Repair is a separate, operator-visible stage. This is recurring snapshot reconciliation, not transaction-log CDC or a zero-downtime change stream.

Sorted snapshot comparison
Readers sort by the selected key, stream both sides, and classify rows as additions, changes, or deletions while writing reviewable difference files.
Equality controls
Configure key selection and equality behavior for types where formatting, precision, or target representation require deliberate tolerance.
Batch repair
Repair is a separate, operator-visible stage. This is recurring snapshot reconciliation, not transaction-log CDC or a zero-downtime change stream.
The path to confidence
The page keeps the product detail close to the decision it supports. Your team can see what the software handles automatically, what it changes for the target, and what the result leaves ready to operate.
Readers sort by the selected key, stream both sides, and classify rows as additions, changes, or deletions while writing reviewable difference files.
Configure key selection and equality behavior for types where formatting, precision, or target representation require deliberate tolerance.
Repair is a separate, operator-visible stage. This is recurring snapshot reconciliation, not transaction-log CDC or a zero-downtime change stream.
Keep the plan connected
A capability becomes easier to operate when the next decision follows from the constraint you just uncovered. Explore the related work that completes this part of the path.
Your working set
Take the next step
Compare complete source and target views, review durable difference artifacts, and decide when repairs should be applied.
Plan my migration