Cloud and On-Prem Data Sync: Hybrid Environment
How do you set up synchronization when data lives both on premises and in the cloud? Direction, latency, conflicts and security for hybrid setups.

In many small and mid-sized businesses the ERP runs on a company server (on-prem), while reports are wanted from somewhere else, from another network. A hybrid setup means moving data between two worlds and keeping it consistent.
Four basic questions
- Direction: does data flow only from source to target, or both ways? Two-way synchronization needs conflict management and is much harder.
- Latency: how old can the data at the target be at most? A nightly batch transfer is enough for most reports.
- Conflict: if the same record changes in two places, which one wins? Define a single source of truth.
- Security and network: an outbound connection from the inside is far less risky than a port opened to the inside; you still need authentication, signing and an encrypted connection.
Common mistakes
- Building two-way synchronization when it is not needed.
- Not thinking about what happens when the network drops: you need a transfer that can be retried and re-run.
- Not comparing numbers on both sides: after the transfer, totals should match the source.
- Writing credentials into files.
Where Floemdata stands
Floemdata Analytics reads from SAP B1 as an installation running on the customer's site and writes the result to a local database; the flow is one-way (source to warehouse). To see the data of several installations in one panel, the documentation describes two ways: a shared data folder pointing at the same network share, or installations posting to another installation's address over signed HTTP (a center address and a shared secret; the data sent is compressed and uploaded with a sha256 digest and an HMAC signature). For outside access to machines on different networks a Cloudflare tunnel can be used; the documentation warns that the administrator password must be changed first. A cloud-hosted managed service and two-way synchronization are not verified features (not verified).
To get started, write in a table which data moves in which direction, how often, and which side counts as correct. Questions: info@floemdata.com.