BC v25 Synchronization – Offline/Online Remote Sites

Business Central/NAV
1

Hi everyone,

I’m looking for a technical solution to to synchronize two Business Central v25 on-premises instances:

Main site: Full BC installation with all master data (items, etc.)

Remote site: Local BC used for CMMS and inventory, with an unstable VSAT connection

One-way sync: Send master data (e.g., items) from the main site to the remote site

Two-way sync: Exchange transactional data like purchase receipts, transfers, stock adjustments, and production orders

The remote site must work autonomously, even offline, and sync reliably with the main site when the connection is available.

What technical solutions do you recommend for this setup?
APIs, data replication, middleware, or other?

Thanks in advance for your help and experience sharing!

1 Like
2

Hi Med,

Totally get the challenge syncing two BC on-prem systems with an unstable connection at one site can be tough, but it’s definitely doable. We’ve supported similar setups where the remote site had to function offline and still stay in sync with the main system.

  • One-way sync of master data (like items) can work well using scheduled jobs or lightweight APIs.

  • For two-way transactional sync, a background service that holds local data and syncs once the connection is up can keep things smooth.

We’ve seen this kind of setup work reliably using native BC capabilities plus some smart customization. If it helps, I’d be glad to chat more or share how we’ve approached it in the past. Always happy to support the community where we can!

For your convenience you can reach out to me at hardik.gupta@allgrowtech.com

Hardik
Allgrow Technologies

3

Thanks Hardik,
Very helpful I’ll reach out if needed

1 Like
4

Hi @Med_Boussetta ,
Based on your requirements, we can develop a custom integration solution within Microsoft Dynamics 365 Business Central (v25) to handle the synchronization between your main and remote on-premises instances.

:white_check_mark: Proposed Architecture:

1. Platform:
We recommend developing this solution within Business Central using AL extensions and deploying it on both environments (main and remote).

2. Sync Mechanism:

  • One-way sync for master data (Items, Vendors, etc.):
    Use custom APIs or job queues in Business Central to push changes from the main site to the remote site.

  • Two-way sync for transactional data (e.g., purchase receipts, stock adjustments):
    Use intermediate staging tables and scheduled background sync routines. This ensures transactions can be queued and reconciled asynchronously, even with intermittent connectivity.

3. Offline Capability:

  • The remote site can operate fully offline/autonomously using local BC functionality.

  • When the VSAT connection is available, the sync jobs will auto-resume using stored queues or logs, ensuring data consistency without user intervention.

4. Integration Strategy:

  • A lightweight middleware service (e.g., a small C# app or Azure Function) can act as a buffer/relay between the two instances, minimizing the impact of unstable network connectivity.

  • Alternatively, direct BC-to-BC communication via web services/APIs can be used where feasible.

:wrench: Technical Comments:

  • Custom conflict resolution rules should be implemented to handle sync conflicts, especially in transactional data.

  • All sync processes should be logged and auditable, with retry and alert mechanisms in case of failure.

  • Security and authentication (OAuth or token-based) between the two systems must be tightly controlled.

We have hands-on experience building similar architectures and can implement and deploy this tailored to your infrastructure.
If you’d like to explore this further, feel free to reach out to me at sajjad@newiztech.com.

Best regards,
Sajjad
NewizTech | Business Central Solutions Architect

5

Hi Sajjad,
Thanks for all the detailed information, very helpful. I’ll reach out if needed.
Best,
Med