Let both systems accept writes. Choose the winner table by table.
Set a default winning database, override it for any table, and start. Omni Loader handles origin tracking, loop prevention, and consistent conflict resolution for you.
Run both directions as one coordinated topology.
Select which database wins conflicting changes.
Replicated writes are never sent back endlessly.
Both directions, one setup
Omni Loader handles the replication mechanics.
Create the bidirectional sync as one topology. Omni Loader tracks where changes began, prevents echoes, and keeps both directions operating together.
One simple choice per table
Choose which database wins a conflicting change.
Set one default for the pipeline, then override the tables owned by the other system. Omni Loader applies those choices consistently and records every resolution.
Keep exploring
See the connected parts of the platform.
Choose the conflict winner table by table.
Set the default winning database, override any tables owned by the other system, and let Omni Loader handle the rest.