Two-way sync
Changes in Microsoft Dynamics NAV or Supabase instantly reflect in both systems. No stale data, no manual imports.
Keep Microsoft Dynamics NAV 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 Item Ledger Entries, Dimensions, Companies, Customers from Microsoft Dynamics NAV into Supabase and keeps both sides consistent in real time. Whatever Microsoft Dynamics NAV 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 Microsoft Dynamics NAV with its validations respected.
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 Microsoft Dynamics NAV, keeping the ERP authoritative.
Records from Microsoft Dynamics NAV live in Supabase as ordinary tables or collections, joinable with the rest of your data.
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.
| Microsoft Dynamics NAV objects | Supabase objects | How this pairing syncs | |
|---|---|---|---|
| Vendors Vendor cards aligned with procurement and AP tools. | Tables Standard Postgres tables; the primary two-way sync target. | Vendors is specific to Microsoft Dynamics NAV and Tables to Supabase — each maps to any object or custom field on the other side. | |
| Items Item cards and availability mirrored to ecommerce and planning systems. | Views Read-side projections exposed to outbound syncs. | Items is specific to Microsoft Dynamics NAV and Views to Supabase — each maps to any object or custom field on the other side. | |
| Sales Orders & Invoices Sales documents created from external orders and read back for posting status. | Schemas Namespaces (public and custom) that scope sync access. | Sales Orders & Invoices is specific to Microsoft Dynamics NAV and Schemas to Supabase — each maps to any object or custom field on the other side. | |
| Purchase Orders Purchasing documents reconciled with receiving and vendor systems. | auth.users Managed authentication users, often mirrored into CRM or support systems. | Purchase Orders is specific to Microsoft Dynamics NAV and auth.users to Supabase — each maps to any object or custom field on the other side. | |
| G/L Entries Posted ledger entries replicated to warehouses for finance reporting. | Row Level Security Policies Row-level access rules that govern what the REST layer exposes. | G/L Entries is specific to Microsoft Dynamics NAV and Row Level Security Policies to Supabase — each maps to any object or custom field on the other side. | |
| Item Ledger Entries Inventory movement history read for stock and costing analytics. | JSONB Columns Semi-structured payloads such as event properties or nested objects. | Item Ledger Entries is specific to Microsoft Dynamics NAV and JSONB Columns to Supabase — 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.
DetectionChanges in Microsoft Dynamics NAV are captured at the source via change data capture — no polling loop against its API. Polling on modified/timestamp fields, or SQL Server change tracking/CDC on on-premises databases.
DeliveryEach detected change is applied to Supabase as a row-level write, with types converted between the two schemas.
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 applied to Microsoft Dynamics NAV as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics NAV–Supabase connection.
Changes in Microsoft Dynamics NAV or Supabase instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Microsoft Dynamics NAV 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 Microsoft Dynamics NAV or Supabase record.
Track your Microsoft Dynamics NAV ⇄ Supabase sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics NAV 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 Microsoft Dynamics NAV 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 Microsoft Dynamics NAV 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.
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 538 integrations available for Microsoft Dynamics NAV and Supabase.