DOCUMENTATION / OVERVIEW
What is SyncCoordinator?
SyncCoordinator is a self-hosted platform for building and operating data synchronization across SQL Server, MySQL, and PostgreSQL without changing existing business applications or business tables.
FOUNDATION
Connect data without changing business systems.
Instead of adding integration code to each business application, configure database connections, table and column mappings, and synchronization rules in the management console. Existing business tables remain unchanged.
SyncCoordinator deploys helper tables and change-detection triggers beside the business tables. It does not modify existing business columns or application code.
CORE CAPABILITIES
Core capabilities
No business application changes
Build integrations through the management console without changing existing business code or business tables.
Map database differences
Define table, column, type, and code-value differences as mappings instead of writing system-specific integration code.
Handle bidirectional updates safely
Detect concurrent edits to the same data and route each field to automatic merge or manual resolution.
Notify and support operations
Monitor synchronization, conflicts, and events that need attention, then retry or pause processing from one console.
USE CASES
Use cases
Connect departmental systems
Synchronize selected order, inventory, or customer data while keeping the existing systems in place.
Run old and new systems in parallel
Keep operations running during migration by synchronizing the data required by both systems.
Support customer-specific schemas
Let system integrators and software vendors manage customer-specific database schemas and code sets as mappings.
When SynCo is not the right fit
SynCo continuously detects changes to database records and synchronizes them while resolving conflicts. It is not designed for the following cases.
- The target database does not permit change-detection triggersDeploying a change-detection trigger is currently a prerequisite for using SynCo.
- Every run must replace the full data setThe primary requirement is a full copy or bulk reload rather than continuous change synchronization.
- The event sequence must be reproducedThe integration must preserve workflow transitions or approval history, not only the current record state.
- Non-one-to-one record mapping or file integration is requiredSynchronization is one record to one record. One-to-many, many-to-one, and many-to-many transformations, as well as transferring files, reports, or video, are not supported.
- The schema changes frequentlyTables and columns are still undergoing frequent breaking changes, such as during early development.
MANAGEMENT CONSOLE
See synchronization status at a glance and in detail.
Review routes, processing state, and recent conflicts, then retry or pause work when necessary.
NEXT