Real-time
Two-way sync
Changes in Microsoft Dynamics 365 or Paylocity instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Human resources
Microsoft Dynamics 365 to Paylocity integration — real-time, two-way sync
Keep Microsoft Dynamics 365 and Paylocity 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 365 and Paylocity
Keep the people, teams, and status that Microsoft Dynamics 365 and Paylocity share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.
Each tool in Microsoft Dynamics 365 keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Paylocity is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.
Stacksync syncs Opportunities, Cases (Incidents), Quotes, Orders & Invoices, Products in Microsoft Dynamics 365 with Earnings (Pay Setup), Local and State Taxes, Direct Deposit, Pay Statements in Paylocity bi-directionally and in real time. A person added, moved, or offboarded in Paylocity creates or updates the matching user in Microsoft Dynamics 365 within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Microsoft Dynamics 365 captures details of its own, such as a corrected contact or a login identity, those can flow back to Paylocity in whichever direction you configure.
Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.
Common use cases
- 01 Replicate standard and custom Dataverse tables into a warehouse for reporting.
- 02 Enrich leads from external data sources and write scores back onto Dynamics records.
- 03 Push hired candidates from an ATS into Paylocity via the Onboarding endpoint, then read Onboarding Status to confirm the record before the first payroll run.
- 04 Upsert recurring Deductions and Earnings on employee records when benefits or 401(k) elections change in a benefits admin system, without re-keying payroll setup.
Common sync patterns
Onboarding: access ready on day one
A new hire recorded in Paylocity creates the matching user in Microsoft Dynamics 365 with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
Offboarding: no standing access after a departure
When someone is marked as leaving in Paylocity, the matching account in Microsoft Dynamics 365 is deactivated or flagged, so departures do not leave open access behind.
One employee directory
A person's name, title, contact details, or status corrected in either system updates the other, so both sides stop maintaining separate copies of the same person.
What you can sync between Microsoft Dynamics 365 and Paylocity
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 365 objects | Paylocity objects | How this pairing syncs | |
|---|---|---|---|
| Activities Emails, calls, and tasks captured for engagement analytics. | Earnings (Pay Setup) Recurring earning codes at the employee level; two-way via Upsert Earning and Delete, with Get All Earnings and Get by earning code for reads. | Activities is specific to Microsoft Dynamics 365 and Earnings (Pay Setup) to Paylocity — each maps to any object or custom field on the other side. | |
| Custom Tables Dataverse tables that carry business-specific entities through the same API surface. | Local and State Taxes Two-way via Create/Update/Delete Local Tax and Upsert Primary / Non-Primary State Tax; Get by tax code and Get All for reads. | Custom Tables is specific to Microsoft Dynamics 365 and Local and State Taxes to Paylocity — each maps to any object or custom field on the other side. | |
| Accounts Company records synced bi-directionally with ERPs, databases, and billing systems. | Direct Deposit Read-only: Get All Direct Deposit and Get Employee Bank Accounts return main and additional allocations. Bank details cannot be written through the API. | Accounts is specific to Microsoft Dynamics 365 and Direct Deposit to Paylocity — each maps to any object or custom field on the other side. | |
| Contacts Person records kept consistent with marketing, support, and data-warehouse copies. | Pay Statements Read-only detailed payroll statement data — earnings, deductions, taxes, and direct deposit allocations by year, check date, or date range. Pulled for reporting, never written. | Contacts is specific to Microsoft Dynamics 365 and Pay Statements to Paylocity — each maps to any object or custom field on the other side. | |
| Leads Inbound records enriched and routed from external sources into sales queues. | Company Codes Read-only reference codes and descriptions (cost centers, departments, positions) used to validate field mappings on employee writes. | Leads is specific to Microsoft Dynamics 365 and Company Codes to Paylocity — each maps to any object or custom field on the other side. | |
| Opportunities Pipeline records synced with forecasting, CPQ, and billing systems. | Custom Fields Read-only company-specific custom fields returned by category, used to enrich the employee record downstream. | Opportunities is specific to Microsoft Dynamics 365 and Custom Fields to Paylocity — each maps to any object or custom field on the other side. |
How changes propagate between Microsoft Dynamics 365 and Paylocity
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 365 Paylocity Sub-second propagation
DetectionMicrosoft Dynamics 365 pushes changes as they happen — webhook events backed by change data capture. Change data capture (CDC) via the Dynamics 365 Change Tracking feature.
DeliveryEach detected change is written to Paylocity through its API, with automatic retries and rate-limit backoff.
Paylocity Microsoft Dynamics 365 Sub-second propagation
DetectionPaylocity notifies Stacksync of record changes through webhook events. Webhooks — Paylocity POSTs Employee New Hire, Employee Change, Termination, Payroll Processed, and Time Off Approval events to a callback URL.
DeliveryEach detected change is written to Microsoft Dynamics 365 through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Paylocity: 25 requests per second (1,500 per minute); exceeding it returns HTTP 429. Every path is scoped to a Paylocity-assigned companyId (a company code, not a UUID).
What ships with Microsoft Dynamics 365 ⇄ Paylocity
Connect Microsoft Dynamics 365 and Paylocity for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics 365–Paylocity connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Microsoft Dynamics 365 or Paylocity 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 365 or Paylocity record.
Observability
Monitoring
Track your Microsoft Dynamics 365 ⇄ Paylocity 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 365 and Paylocity.
How the Microsoft Dynamics 365 and Paylocity connectors work
Microsoft Dynamics 365
- Integration surface
- REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface
- Authentication
- Microsoft OAuth sign-in: user provides the D365 environment URL, signs in with Microsoft credentials, and accepts the Stacksync app (permissions to read CRM data and interact with OData entities)
- Change detection
- Change data capture (CDC) via the Dynamics 365 Change Tracking feature; standard entities have change tracking enabled by default, custom entities require enabling "Track Changes" in Power Apps/Dataverse table properties
- Capabilities
- read · write · CDC · webhooks
Paylocity
- Integration surface
- REST API (v1 and v2), JSON payloads
- Authentication
- OAuth 2.0 client credentials via the Paylocity Identity Provider (/IdentityServer/connect/token) with the WebLinkAPI scope; access tokens expire after one hour and API access must be enabled by Paylocity for the company
- Change detection
- Webhooks — Paylocity POSTs Employee New Hire, Employee Change, Termination, Payroll Processed, and Time Off Approval events to a callback URL; payloads carry only companyId and employeeId, so the receiver calls the relevant API to fetch changed values. Scheduled polling is used for objects without webhooks.
- Capabilities
- read · write · webhooks
- Rate limits
- 25 requests per second (1,500 per minute); exceeding it returns HTTP 429. Every path is scoped to a Paylocity-assigned companyId (a company code, not a UUID).
How it works
How to connect Microsoft Dynamics 365 to Paylocity — 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 365 and Paylocity 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 365
connected
Paylocity
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Microsoft Dynamics 365 and Paylocity 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 365 ⇄ PaylocityCustomers 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 365 PaylocityCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Microsoft Dynamics 365 and Paylocity integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Microsoft Dynamics 365 and Paylocity: authenticate both systems, choose the objects to sync (such as Microsoft Dynamics 365's Activities and Custom Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Microsoft Dynamics 365 side: Opportunities, Cases (Incidents), Quotes, Orders & Invoices, Products, plus custom fields where Microsoft Dynamics 365 exposes them. On the Paylocity side: Earnings (Pay Setup), Local and State Taxes, Direct Deposit, Pay Statements. 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 365 and Paylocity: Onboarding: access ready on day one; Offboarding: no standing access after a departure; One employee directory. A new hire recorded in Paylocity creates the matching user in Microsoft Dynamics 365 with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
-
Microsoft Dynamics 365: REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface. Authentication: Microsoft OAuth sign-in: user provides the D365 environment URL, signs in with Microsoft credentials, and accepts the Stacksync app (permissions to read CRM data and interact with OData entities). Paylocity: REST API (v1 and v2), JSON payloads. Authentication: OAuth 2.0 client credentials via the Paylocity Identity Provider (/IdentityServer/connect/token) with the WebLinkAPI scope; access tokens expire after one hour and API access must be enabled by Paylocity for the company. Stacksync manages authentication, retries, and rate limits on both sides.
-
Microsoft Dynamics 365: Change tracking returns only rows changed since a delta token, giving integrations an incremental read path without full re-pulls. Paylocity: The rate limit is 25 calls per second (1,500 per minute); full-employee reads must be paged and throttled to avoid HTTP 429 errors. Stacksync's field mapping accounts for these differences between Microsoft Dynamics 365 and Paylocity without custom code.
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 513 integrations available for Microsoft Dynamics 365 and Paylocity.
Popular · 8 of 513
-
Microsoft Dynamics 365 ⇄ Jobvite -
Microsoft Dynamics 365 ⇄ Lever -
Microsoft Dynamics 365 ⇄ Namely -
Microsoft Dynamics 365 ⇄ Ukg Ready -
Paylocity ⇄ Orderful -
Paylocity ⇄ Resend -
Paylocity ⇄ ServiceNow -
Paylocity ⇄ Slack
No integrations match .
