Real-time
Two-way sync
Changes in Microsoft Dynamics GP or Onelogin instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Security and identity
Microsoft Dynamics GP to Onelogin integration — real-time, two-way sync
Keep Microsoft Dynamics GP and Onelogin 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 Microsoft Dynamics GP and Onelogin
Keep the employee, group, and account records that Microsoft Dynamics GP and Onelogin share aligned in real time, so a person added, moved, or offboarded in one system shows up correctly in the other within seconds.
An ERP and an identity system describe the same workforce from two angles. Microsoft Dynamics GP holds the authoritative record of who works at the company, and often their department, title, manager, and cost center. Onelogin controls the accounts, groups, and access those same people use every day. When the two aren't connected, every hire, transfer, and departure has to be keyed twice, and the window between someone leaving in Microsoft Dynamics GP and their account still being active in Onelogin is a real security exposure.
Stacksync syncs Inventory Items (IV), GL Accounts & Journal Entries, Receivables & Payables Transactions, Company Databases in Microsoft Dynamics GP with Roles, Apps (app instances), Groups, Mappings (mapping rules) in Onelogin in real time, with field-level mapping and conflict resolution in place of CSV exports and nightly jobs. A new hire, a department change, or a termination propagates within seconds, and where you want changes to flow both ways — the ERP's org data into the directory, account status back into the ERP — the same mapping handles it.
That matters most at offboarding and audit time. When the directory reflects the ERP's current headcount and org structure, disabling access no longer depends on someone remembering to update a second system, and access reviews start from a roster both sides already agree on.
Common use cases
- 01 Replicate GP company databases into a warehouse for financial and operational reporting.
- 02 Sync customers and invoices between GP and a CRM so sales sees balances and billing history.
- 03 Read Users, Apps, and Groups into a database for identity, license, and app-assignment inventory across the OneLogin account.
- 04 Two-way sync Users between OneLogin and an HRIS or Postgres so new hires, attribute changes, and terminations provision and deprovision SSO accounts automatically.
Common sync patterns
Align group and department membership
When someone changes team or department, their group or organizational-unit membership updates to match, keeping access tied to their current role.
One roster on a shared key
People are matched across both systems on an identifier you choose, such as work email or employee ID, so there is a single accurate list of who is active.
Create accounts from new records
A person added in one system gets a matching account or record in the other automatically, so a new hire can be granted access without anyone re-keying their details.
What you can sync between Microsoft Dynamics GP and Onelogin
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 | Onelogin objects | How this pairing syncs | |
|---|---|---|---|
| Inventory Items (IV) Item master and quantity data mirrored to ecommerce and planning systems. | Authentication factors (MFA) Per-user registered MFA factors; enrolled, verified, and removed through the MFA API for lifecycle and security workflows. | Inventory Items (IV) is specific to Microsoft Dynamics GP and Authentication factors (MFA) to Onelogin — each maps to any object or custom field on the other side. | |
| GL Accounts & Journal Entries Financial ledger data replicated to warehouses for consolidated reporting. | Custom user fields Account-level custom attributes on the User record; read and written alongside the standard user profile fields. | GL Accounts & Journal Entries is specific to Microsoft Dynamics GP and Custom user fields to Onelogin — each maps to any object or custom field on the other side. | |
| Receivables & Payables Transactions Open and historical AR/AP transactions read for cash and aging reporting. | Users User accounts (email, username, custom attributes, status, roles); full CRUD via the v2 Users API - create, update, delete, set password, lock/unlock, and add or remove role assignments. | Receivables & Payables Transactions is specific to Microsoft Dynamics GP and Users to Onelogin — each maps to any object or custom field on the other side. | |
| Company Databases Per-company SQL databases that define the scope of any sync. | Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. | Company Databases is specific to Microsoft Dynamics GP and Roles to Onelogin — each maps to any object or custom field on the other side. | |
| Customers Receivables master records (RM tables) synced with CRMs and billing tools. | Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. | Customers is specific to Microsoft Dynamics GP and Apps (app instances) to Onelogin — each maps to any object or custom field on the other side. | |
| Vendors Payables master records aligned with procurement and AP automation. | Groups Account groups used for mapping and reporting; listed and read through the API, which has no create or update endpoint, so groups are read-only. | Vendors is specific to Microsoft Dynamics GP and Groups to Onelogin — each maps to any object or custom field on the other side. |
How changes propagate between Microsoft Dynamics GP and Onelogin
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.
Microsoft Dynamics GP Onelogin Sub-second propagation
DetectionChanges in Microsoft Dynamics GP are captured at the source via change data capture — no polling loop against its API. SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps.
DeliveryEach detected change is written to Onelogin through its API, with automatic retries and rate-limit backoff.
Onelogin Microsoft Dynamics GP Sub-second propagation
DetectionOnelogin notifies Stacksync of record changes through webhook events. Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time.
DeliveryEach detected change is applied to Microsoft Dynamics GP as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Onelogin: Account-level limit of 5,000 API calls per hour shared across all access tokens; responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset, over-limit calls return HTTP 429, and the count resets each hour. Paid plans can request an increase.
What ships with Microsoft Dynamics GP ⇄ Onelogin
Connect Microsoft Dynamics GP and Onelogin for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics GP–Onelogin connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Microsoft Dynamics GP or Onelogin 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 Microsoft Dynamics GP or Onelogin record.
Observability
Monitoring
Track your Microsoft Dynamics GP ⇄ Onelogin sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics GP and Onelogin.
How the Microsoft Dynamics GP and Onelogin connectors work
Microsoft Dynamics GP
- Integration surface
- SQL Server database access plus the eConnect stored-procedure API; Web Services for GP on some deployments
- Authentication
- SQL Server credentials or Windows authentication
- Change detection
- SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps
- Capabilities
- read · write · CDC
Onelogin
- Integration surface
- OneLogin API (REST, v1 and v2 resource endpoints on <subdomain>.onelogin.com) plus the Event Webhook (Event Broadcaster) for event delivery
- Authentication
- OAuth 2.0 client credentials - an admin generates an API credential pair (client_id + client_secret) in the OneLogin portal and exchanges it at POST /auth/oauth2/v2/token for a bearer access token sent on every call; each credential carries a scope (Manage all, Manage users, Read users, etc.) that governs read vs write.
- Change detection
- Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time; the Events API also supports polling with since/until time filters and pagination for historical backfill.
- Capabilities
- read · write · webhooks
- Rate limits
- Account-level limit of 5,000 API calls per hour shared across all access tokens; responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset, over-limit calls return HTTP 429, and the count resets each hour. Paid plans can request an increase.
How it works
How to connect Microsoft Dynamics GP to Onelogin — 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.
- 01
Connect your apps
Authenticate Microsoft Dynamics GP and Onelogin with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Microsoft Dynamics GP
connected
Onelogin
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Microsoft Dynamics GP and Onelogin 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.
objects · Microsoft Dynamics GP ⇄ OneloginCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Microsoft Dynamics GP OneloginCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Microsoft Dynamics GP and Onelogin integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Microsoft Dynamics GP and Onelogin: 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.
-
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 Microsoft Dynamics GP and Onelogin records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Microsoft Dynamics GP and Onelogin connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Microsoft Dynamics GP–Onelogin integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Microsoft Dynamics GP and Onelogin. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Microsoft Dynamics GP: SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps. On Onelogin: Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time; the Events API also supports polling with since/until time filters and pagination for historical backfill. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Microsoft Dynamics GP side: Inventory Items (IV), GL Accounts & Journal Entries, Receivables & Payables Transactions, Company Databases, plus custom fields where Microsoft Dynamics GP exposes them. On the Onelogin side: Roles, Apps (app instances), Groups, Mappings (mapping rules). Stacksync auto-detects both schemas and converts types between the two systems.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 503 integrations available for Microsoft Dynamics GP and Onelogin.
Popular · 8 of 503
-
Microsoft Dynamics GP ⇄ Active Directory - Microsoft Dynamics GP ⇄ Azure Active Directory
-
Microsoft Dynamics GP ⇄ Okta -
Microsoft Dynamics GP ⇄ Auth0 -
Onelogin ⇄ Infor CloudSuite - Onelogin ⇄ Infor LN
- Onelogin ⇄ Infor M3
- Onelogin ⇄ Infor WMS
No integrations match .
