Two-way sync
Changes in Microsoft Dynamics GP or Supabase instantly reflect in both systems. No stale data, no manual imports.
Keep Microsoft Dynamics GP 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 Customers, Vendors, Sales Documents (SOP), Purchase Orders (POP) from Microsoft Dynamics GP into Supabase and keeps both sides consistent in real time. Whatever Microsoft Dynamics GP 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 GP 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 GP, keeping the ERP authoritative.
Records from Microsoft Dynamics GP 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 GP objects | Supabase objects | |
|---|---|---|
| Inventory Items (IV) Item master and quantity data mirrored to ecommerce and planning systems. | Schemas Namespaces (public and custom) that scope sync access. | |
| GL Accounts & Journal Entries Financial ledger data replicated to warehouses for consolidated reporting. | auth.users Managed authentication users, often mirrored into CRM or support systems. | |
| Receivables & Payables Transactions Open and historical AR/AP transactions read for cash and aging reporting. | Row Level Security Policies Row-level access rules that govern what the REST layer exposes. | |
| Company Databases Per-company SQL databases that define the scope of any sync. | JSONB Columns Semi-structured payloads such as event properties or nested objects. | |
| Customers Receivables master records (RM tables) synced with CRMs and billing tools. | Database Functions Postgres functions that can transform or validate synced rows. | |
| Vendors Payables master records aligned with procurement and AP automation. | Storage Object Metadata File metadata rows that can be joined to synced application data. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics GP–Supabase connection.
Changes in Microsoft Dynamics GP or Supabase instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Microsoft Dynamics GP 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 GP or Supabase record.
Track your Microsoft Dynamics GP ⇄ Supabase sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics GP 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 GP 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 GP 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 Microsoft Dynamics GP and Supabase: authenticate both systems, choose the objects to sync (such as Microsoft Dynamics GP's Inventory Items (IV) and GL Accounts & Journal Entries), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Microsoft Dynamics GP: SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps. On Supabase: Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Supabase side: JSONB Columns, Database Functions, Storage Object Metadata, Tables, plus custom fields where Supabase exposes them. On the Microsoft Dynamics GP side: Customers, Vendors, Sales Documents (SOP), Purchase Orders (POP). 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 Microsoft Dynamics GP and Supabase: Where Microsoft Dynamics GP is the HR system of record: people data for internal systems; Controlled write-back; Read ERP records with a query. Worker and org records stay current in Supabase for provisioning, access, and reporting systems that read from the database.
Microsoft Dynamics GP: SQL Server database access plus the eConnect stored-procedure API; Web Services for GP on some deployments. Authentication: SQL Server credentials or Windows authentication. 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.
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 Microsoft Dynamics GP and Supabase.