Skip to content
ERP ⇄ Database

Dynamics 365 Business Central to Supabase integration — real-time, two-way sync

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.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Dynamics 365 Business Central and Supabase

Give your engineers Dynamics 365 Business Central's data in Supabase: read it with normal queries, write back through the sync, and skip the ERP API entirely.

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.

Common use cases

  • 01 Mirror billing and subscription records into Supabase tables the application can join directly
  • 02 Reflect auth.users state into support and CRM systems so teams see account status without querying the database
  • 03 Replicate GL entries and dimensions into a SQL database for financial reporting without giving analysts ERP logins.
  • 04 Sync vendor and purchase order data with procurement or AP automation tools.

Common sync patterns

React to ERP changes

Updates in Dynamics 365 Business Central arrive as row changes in Supabase, so jobs and triggers can respond as the business record changes.

Where Dynamics 365 Business Central is the HR system of record: people data for internal systems

Worker and org records stay current in Supabase for provisioning, access, and reporting systems that read from the database.

Controlled write-back

Choose exactly which tables and fields may flow from Supabase back into Dynamics 365 Business Central, keeping the ERP authoritative.

What you can sync between Dynamics 365 Business Central and Supabase

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 How this pairing syncs
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 Orders is specific to Dynamics 365 Business Central and auth.users to Supabase — each maps to any object or custom field on the other side.
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. Sales Invoices is specific to Dynamics 365 Business Central and Row Level Security Policies to Supabase — each maps to any object or custom field on the other side.
Purchase Orders Procurement documents exchanged with supplier-facing systems. JSONB Columns Semi-structured payloads such as event properties or nested objects. Purchase Orders is specific to Dynamics 365 Business Central and JSONB Columns to Supabase — 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. Database Functions Postgres functions that can transform or validate synced rows. General Ledger Entries is specific to Dynamics 365 Business Central and Database Functions to Supabase — each maps to any object or custom field on the other side.
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. Journals is specific to Dynamics 365 Business Central and Storage Object Metadata to Supabase — each maps to any object or custom field on the other side.
Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. Tables Standard Postgres tables; the primary two-way sync target. Dimensions is specific to Dynamics 365 Business Central and Tables to Supabase — each maps to any object or custom field on the other side.

How changes propagate between Dynamics 365 Business Central and Supabase

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.

Dynamics 365 Business Central Supabase Sub-second propagation

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 applied to Supabase as a row-level write, with types converted between the two schemas.

Supabase Dynamics 365 Business Central Sub-second propagation

DetectionSupabase pushes changes as they happen — webhook events backed by change data capture. Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime.

DeliveryEach detected change is written to Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Supabase: SQL access is bounded by connection limits (pooled connections are provided); the REST layer is subject to the platform's limits.
What ships with Dynamics 365 Business Central ⇄ Supabase

Connect Dynamics 365 Business Central and Supabase for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 Business Central–Supabase connection.

Real-time

Two-way sync

Changes in Dynamics 365 Business Central or Supabase instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dynamics 365 Business Central or Supabase data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Dynamics 365 Business Central or Supabase record.

Observability

Monitoring

Track your Dynamics 365 Business Central ⇄ Supabase sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Dynamics 365 Business Central and Supabase.

How the Dynamics 365 Business Central and Supabase connectors work

Dynamics 365 Business Central

Integration surface
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
Change detection
API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime
Capabilities
read · write · webhooks

Supabase

Integration surface
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
Change detection
Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes
Capabilities
read · write · CDC · webhooks
Rate limits
SQL access is bounded by connection limits (pooled connections are provided); the REST layer is subject to the platform's limits
How it works

How to connect Dynamics 365 Business Central to Supabase — three steps, no code

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.

  1. 01

    Connect your apps

    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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Dynamics 365 Business Central connected
    Supabase connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Dynamics 365 Business Central ⇄ Supabase
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Dynamics 365 Business Central Supabase
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Dynamics 365 Business Central and Supabase integration FAQ

SECURITY

Security teams trust Stacksync

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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 543 integrations available for Dynamics 365 Business Central and Supabase.

Popular · 8 of 543
All Dynamics 365 Business Central integrations All Supabase integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own