Skip to content
Human resources ⇄ Database

Paylocity to SQL Server integration — real-time, two-way sync

Keep Paylocity and SQL Server 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 Paylocity and SQL Server

Put your workforce data where your apps can reach it: SQL Server and Paylocity share the same people, positions, and org structure in real time.

Paylocity is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. SQL Server is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Direct Deposit, Pay Statements, Company Codes, Custom Fields in Paylocity need to exist as queryable Columns, Primary and Unique Keys, CDC Change Tables, Stored Procedures in SQL Server before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.

Stacksync syncs Columns, Primary and Unique Keys, CDC Change Tables, Stored Procedures in SQL Server with Direct Deposit, Pay Statements, Company Codes, Custom Fields in Paylocity field by field, in real time. You decide which system owns which fields — Paylocity typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.

The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.

Common use cases

  • 01 Consolidate branch or plant databases into a single operational SQL Server hub
  • 02 Bi-directional sync between SQL Server rows and CRM objects so .NET line-of-business apps and sales tools share one dataset
  • 03 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.
  • 04 Read Pay Statements and Direct Deposit allocations into a Postgres or warehouse database for labor-cost, GL, and headcount reporting in SQL.

Common sync patterns

Computed and operational fields flow back

Values assembled or corrected in SQL Server write onto the matching record in Paylocity where those fields are writable, keeping the people system enriched.

Mirror people records into the database

Records maintained in Paylocity land as queryable Columns, Primary and Unique Keys, CDC Change Tables, Stored Procedures in SQL Server, so internal apps and dashboards read live data instead of a periodic export.

One directory of record

When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.

What you can sync between Paylocity and SQL Server

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.

Paylocity objects SQL Server objects How this pairing syncs
Custom Fields Read-only company-specific custom fields returned by category, used to enrich the employee record downstream. Primary and Unique Keys Match keys for idempotent upserts and conflict handling. Custom Fields is specific to Paylocity and Primary and Unique Keys to SQL Server — each maps to any object or custom field on the other side.
Employees Core HR record keyed by companyId + employeeId; two-way via Create New Employee (POST) and Update Employee (PATCH), plus Get Employee / Get All Employees for reads. CDC Change Tables System-populated tables holding captured inserts, updates, and deletes for consumers. Employees is specific to Paylocity and CDC Change Tables to SQL Server — each maps to any object or custom field on the other side.
Onboarding Create Employee Onboarding pushes new-hire data into Paylocity's onboarding workflow; Get Onboarding Status reads back partner onboarding progress. Write-in for hires from an ATS. Stored Procedures T-SQL logic that can validate or post-process synced rows. Onboarding is specific to Paylocity and Stored Procedures to SQL Server — each maps to any object or custom field on the other side.
Deductions (Pay Setup) Recurring deduction codes at the employee level; two-way via Upsert Deduction and Delete, with Get Deduction / Get All Deductions for reads. Databases Instance-level databases that scope a sync's reads and writes. Deductions (Pay Setup) is specific to Paylocity and Databases to SQL Server — each maps to any object or custom field on the other side.
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. Schemas Namespaces (dbo and custom) used to organize synced tables. Earnings (Pay Setup) is specific to Paylocity and Schemas to SQL Server — each maps to any object or custom field on the other side.
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. Tables The primary sync target; rows map to records in connected systems. Local and State Taxes is specific to Paylocity and Tables to SQL Server — each maps to any object or custom field on the other side.

How changes propagate between Paylocity and SQL Server

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.

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

SQL Server Paylocity Sub-second propagation

DetectionChanges in SQL Server are captured at the source via change data capture — no polling loop against its API. SQL Server Native Change Data Capture (CDC).

DeliveryEach detected change is written to Paylocity 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).
  • SQL Server: No API rate limits; throughput depends on instance resources, licensing tier, and connection limits.
What ships with Paylocity ⇄ SQL Server

Connect Paylocity and SQL Server for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Paylocity–SQL Server connection.

Real-time

Two-way sync

Changes in Paylocity or SQL Server instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Paylocity or SQL Server 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 Paylocity or SQL Server record.

Observability

Monitoring

Track your Paylocity ⇄ SQL Server sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Paylocity and SQL Server.

How the Paylocity and SQL Server connectors work

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).

SQL Server

Integration surface
SQL over the TDS wire protocol (Tabular Data Stream), via ODBC/JDBC/ADO.NET drivers
Authentication
Database credentials entered as a connection string or as parameters (host/user/password) in the Create New Sync page
Change detection
SQL Server Native Change Data Capture (CDC); a DBA runs a one-time setup script with sysadmin privileges to enable CDC and create Stacksync wrapper procedures
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput depends on instance resources, licensing tier, and connection limits
SQL Server setup guide
How it works

How to connect Paylocity to SQL Server — 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 Paylocity and SQL Server 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
    Paylocity connected
    SQL Server connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Paylocity and SQL Server 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 · Paylocity ⇄ SQL Server
    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
    Paylocity SQL Server
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Paylocity and SQL Server 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 539 integrations available for Paylocity and SQL Server.

Popular · 8 of 539
All Paylocity integrations All SQL Server 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