Two-way sync
Changes in Dynamics 365 Business Central or Supabase instantly reflect in both systems. No stale data, no manual imports.
Keep Dynamics 365 Business Central and Supabase 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 Supabase 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 Supabase sync back into Dynamics 365 Business Central with its validations respected.
Updates in Dynamics 365 Business Central arrive as row changes in Supabase, so jobs and triggers can respond as the business record changes.
Worker and org records stay current in Supabase for provisioning, access, and reporting systems that read from the database.
Choose exactly which tables and fields may flow from Supabase 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 | Supabase objects | |
|---|---|---|
| Sales Orders Order headers and lines created from external channels and read back for fulfillment status. | auth.users Managed authentication users, often mirrored into CRM or support systems. | |
| Sales Invoices Billing documents synced to CRMs and payment platforms. | Row Level Security Policies Row-level access rules that govern what the REST layer exposes. | |
| Purchase Orders Procurement documents exchanged with supplier-facing systems. | JSONB Columns Semi-structured payloads such as event properties or nested objects. | |
| General Ledger Entries Posted financial transactions read for reporting; posted entries are immutable. | Database Functions Postgres functions that can transform or validate synced rows. | |
| Journals Staging records for financial postings created by integrations before posting. | Storage Object Metadata File metadata rows that can be joined to synced application data. | |
| Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. | Tables Standard Postgres tables; the primary two-way sync target. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 Business Central–Supabase connection.
Changes in Dynamics 365 Business Central or Supabase instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Dynamics 365 Business Central or Supabase 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 Supabase record.
Track your Dynamics 365 Business Central ⇄ Supabase 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 Supabase.
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 Supabase 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 Supabase 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 Supabase: authenticate both systems, choose the objects to sync (such as Dynamics 365 Business Central's Sales Orders and Sales Invoices), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Supabase: 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 Supabase, 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. Supabase: Direct PostgreSQL wire protocol connection, plus an auto-generated REST API (PostgREST). Authentication: Database credentials (connection string) for SQL access; API keys (anon / service role) for the REST layer. Stacksync manages authentication, retries, and rate limits on both sides.
Supabase: PostgREST auto-generates a REST endpoint per table, with Row Level Security policies gating access at the row level. Dynamics 365 Business Central: Custom API pages written in AL extend the same OData surface, letting partner-specific tables participate in syncs like standard entities. Stacksync's field mapping accounts for these differences between Dynamics 365 Business Central and Supabase without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Dynamics 365 Business Central and Supabase records are not retained after a sync operation.
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 386 integrations available for Dynamics 365 Business Central and Supabase.