Two-way sync
Changes in Dynamics 365 Business Central or OpenSearch instantly reflect in both systems. No stale data, no manual imports.
Keep Dynamics 365 Business Central and OpenSearch in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
ERP data sits behind interfaces built for the ERP's own modules, not for your internal systems. Teams that need those records, for reporting services, internal tools, or automations, end up writing integration code against a strict API and maintaining it through every upgrade.
Stacksync mirrors Purchase Orders, General Ledger Entries, Journals, Dimensions from Dynamics 365 Business Central into OpenSearch and keeps both sides consistent in real time. Whatever Dynamics 365 Business Central is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in OpenSearch sync back into Dynamics 365 Business Central with its validations respected.
Updates in Dynamics 365 Business Central arrive as row changes in OpenSearch, so jobs and triggers can respond as the business record changes.
Worker and org records stay current in OpenSearch for provisioning, access, and reporting systems that read from the database.
Choose exactly which tables and fields may flow from OpenSearch back into Dynamics 365 Business Central, keeping the ERP authoritative.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Dynamics 365 Business Central objects | OpenSearch objects | How this pairing syncs | |
|---|---|---|---|
| Vendors Supplier master data synced with procurement and AP automation tools. | Snapshots Backup artifacts, relevant when reseeding an index from a repository | Vendors is specific to Dynamics 365 Business Central and Snapshots to OpenSearch — each maps to any object or custom field on the other side. | |
| Items Product and inventory records aligned with e-commerce and warehouse systems. | Indexes The core container; synced records land in indexes with defined mappings | Items is specific to Dynamics 365 Business Central and Indexes to OpenSearch — each maps to any object or custom field on the other side. | |
| Sales Orders Order headers and lines created from external channels and read back for fulfillment status. | Documents JSON records written via the index and bulk APIs and read via search queries | Sales Orders is specific to Dynamics 365 Business Central and Documents to OpenSearch — each maps to any object or custom field on the other side. | |
| Sales Invoices Billing documents synced to CRMs and payment platforms. | Index aliases Stable names over rotating indexes, used for zero-downtime reindex during backfills | Sales Invoices is specific to Dynamics 365 Business Central and Index aliases to OpenSearch — each maps to any object or custom field on the other side. | |
| Purchase Orders Procurement documents exchanged with supplier-facing systems. | Index templates Mapping and settings presets applied to new indexes a sync creates | Purchase Orders is specific to Dynamics 365 Business Central and Index templates to OpenSearch — each maps to any object or custom field on the other side. | |
| General Ledger Entries Posted financial transactions read for reporting; posted entries are immutable. | Ingest pipelines Server-side processors that transform documents as they are written | General Ledger Entries is specific to Dynamics 365 Business Central and Ingest pipelines to OpenSearch — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionDynamics 365 Business Central notifies Stacksync of record changes through webhook events. API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime.
DeliveryEach detected change is written to OpenSearch through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls OpenSearch for changes on an incremental schedule, reading only records changed since the previous pass. No native change feed.
DeliveryEach detected change is written to Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 Business Central–OpenSearch connection.
Changes in Dynamics 365 Business Central or OpenSearch instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Dynamics 365 Business Central or OpenSearch data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Dynamics 365 Business Central or OpenSearch record.
Track your Dynamics 365 Business Central ⇄ OpenSearch sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Dynamics 365 Business Central and OpenSearch.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate Dynamics 365 Business Central and OpenSearch with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Dynamics 365 Business Central and OpenSearch objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Dynamics 365 Business Central and OpenSearch: authenticate both systems, choose the objects to sync (such as Dynamics 365 Business Central's Vendors and Items), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Dynamics 365 Business Central: API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime. On OpenSearch: No native change feed; reads rely on queries with scroll or point-in-time polling. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the OpenSearch side: Ingest pipelines, Data streams, Snapshots, Indexes, plus custom fields where OpenSearch exposes them. On the Dynamics 365 Business Central side: Purchase Orders, General Ledger Entries, Journals, Dimensions. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Dynamics 365 Business Central and OpenSearch: React to ERP changes; Where Dynamics 365 Business Central is the HR system of record: people data for internal systems; Controlled write-back. Updates in Dynamics 365 Business Central arrive as row changes in OpenSearch, so jobs and triggers can respond as the business record changes.
Dynamics 365 Business Central: REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL. Authentication: OAuth 2.0 via Microsoft Entra ID. OpenSearch: REST API over HTTP(S) with JSON payloads. Authentication: Basic authentication with the security plugin, or AWS IAM request signing on Amazon OpenSearch Service. Stacksync manages authentication, retries, and rate limits on both sides.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 427 integrations available for Dynamics 365 Business Central and OpenSearch.