Skip to content

Data synchronisation

Data synchronisation repeatedly reconciles agreed data between systems. Direction, delay, conflicts and safe retries need explicit rules.

Also known asData synchronization
APIs & Integration

Data synchronisation keeps agreed data between systems aligned by repeatedly applying changes. It can be one-way or bidirectional. Direction is defined for the data concerned; not every field has to be editable in both systems.

In a fictional example, the CRM is authoritative for the project contact for customer C-72. The integration sends version 12 to the portal. If a delayed message with version 11 arrives afterwards, the agreed rule must prevent it from overwriting the newer contact. The version numbers are an original design for this example.

Define direction, conflicts and delay

Set stable record mappings, permitted write directions and deletion handling. Changes in both systems require a conflict rule. A later device-clock time alone does not determine which value is correct for the business.

A scheduled run does not guarantee an immediate match. Monitor pending and failed changes and prevent duplicate effects on retries. A migration may temporarily use the same mechanism; ongoing synchronisation instead maintains the agreed alignment during normal operation.

Sources

Related terms

Articles on this topic

Insights · APIs & Integration2 minClarify an interface’s job before replacing itAn outdated connection may still carry important workflows. Its replacement needs clarity about effects, exceptions and open operations.Tobias KrügerNov 13, 2026
Insights · APIs & Integration2 minIntegrations need accountable owners after launchAn operating connection needs decisions about changes and incidents. Technical setup alone does not assign that responsibility.Daniel HartmannNov 13, 2026
Insights · APIs & Integration2 minIntegration effort depends on the data path you needTwo tools with APIs can require different preparation. The deciding factors are the required data, operations and permissions.Tobias KrügerNov 13, 2026
Insights · APIs & Integration2 minA shared data model needs agreed meaningThe same field can mean different things in a CRM and an ERP. The teams need to agree its meaning before defining a shared structure.Tobias KrügerNov 13, 2026
Insights · APIs & Integration2 minWebhook integrations need rules for repeat deliveriesControl the business effects of repeated webhooks. A missing acknowledgement must not trigger another order without checking.Tobias KrügerNov 13, 2026
Insights · APIs & Integration3 minUnclear customer mappings need a defined resolution pathResending does not resolve an unclear customer mapping. An integration needs a documented path from clarification to a confirmed target outcome.Tobias KrügerNov 13, 2026
Insights · APIs & Integration2 minTwo-way synchronisation needs explicit write rulesIf CRM and ERP can write, each shared field needs a conflict rule. The last message to arrive is not automatically the latest business decision.Tobias KrügerNov 13, 2026
Insights · APIs & Integration2 minAn accepted request needs a visible outcomeFor background work, the portal must show what was accepted and how it ends. A successful status query can report a failed job.Tobias KrügerNov 13, 2026

APIs & Integration with ASES

ERP, CRM and shop cleanly connected

Request a quoteMore on APIs & Integration