Real-time
Two-way sync
Changes in MySQL or Paylocity instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Human resources
MySQL to Paylocity integration — real-time, two-way sync
Keep MySQL 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 MySQL and Paylocity
Put your workforce data where your apps can reach it: MySQL 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. MySQL is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Earnings (Pay Setup), Local and State Taxes, Direct Deposit, Pay Statements in Paylocity need to exist as queryable Stored Procedures, Triggers, Databases (Schemas), Tables in MySQL 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 Stored Procedures, Triggers, Databases (Schemas), Tables in MySQL with Earnings (Pay Setup), Local and State Taxes, Direct Deposit, Pay Statements 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 Replicate ERP master data (customers, items, pricing) into the MySQL databases behind storefronts and portals
- 02 Keep e-commerce orders in MySQL flowing into finance and fulfillment systems without export scripts
- 03 Read Pay Statements and Direct Deposit allocations into a Postgres or warehouse database for labor-cost, GL, and headcount reporting in SQL.
- 04 React to the Employee Change webhook to pull the updated Employee record and propagate title, location, or manager changes to downstream apps within minutes.
Common sync patterns
Org and structure stay aligned
Groups, departments, managers, and reporting lines from Paylocity stay consistent in MySQL, so hierarchy-driven logic and permissions don't drift.
Computed and operational fields flow back
Values assembled or corrected in MySQL 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 Stored Procedures, Triggers, Databases (Schemas), Tables in MySQL, so internal apps and dashboards read live data instead of a periodic export.
What you can sync between MySQL 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.
| MySQL objects | Paylocity objects | How this pairing syncs | |
|---|---|---|---|
| Stored Procedures Server-side logic that can post-process synced rows. | 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. | Stored Procedures is specific to MySQL and Pay Statements to Paylocity — each maps to any object or custom field on the other side. | |
| Triggers An alternative change-capture mechanism when binlog access is unavailable. | Company Codes Read-only reference codes and descriptions (cost centers, departments, positions) used to validate field mappings on employee writes. | Triggers is specific to MySQL and Company Codes to Paylocity — each maps to any object or custom field on the other side. | |
| Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. | Custom Fields Read-only company-specific custom fields returned by category, used to enrich the employee record downstream. | Databases (Schemas) is specific to MySQL and Custom Fields to Paylocity — each maps to any object or custom field on the other side. | |
| Tables The primary sync target; rows map to records in connected systems. | 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. | Tables is specific to MySQL and Employees to Paylocity — each maps to any object or custom field on the other side. | |
| Views Read-side projections used as outbound sync sources. | 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. | Views is specific to MySQL and Onboarding to Paylocity — each maps to any object or custom field on the other side. | |
| Columns Field-level mapping targets with engine-typed values. | 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. | Columns is specific to MySQL and Deductions (Pay Setup) to Paylocity — each maps to any object or custom field on the other side. |
How changes propagate between MySQL 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.
MySQL Paylocity Sub-second propagation
DetectionChanges in MySQL are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when.
DeliveryEach detected change is written to Paylocity through its API, with automatic retries and rate-limit backoff.
Paylocity MySQL 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 MySQL as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- MySQL: No API rate limits; throughput is bounded by connection limits and server resources.
- 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 MySQL ⇄ Paylocity
Connect MySQL and Paylocity for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MySQL–Paylocity connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever MySQL 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 MySQL or Paylocity record.
Observability
Monitoring
Track your MySQL ⇄ Paylocity sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between MySQL and Paylocity.
How the MySQL and Paylocity connectors work
MySQL
- Integration surface
- SQL wire protocol (MySQL client/server protocol)
- Authentication
- Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host)
- Change detection
- Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled)
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput is bounded by connection limits and server resources
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 MySQL 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 MySQL 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.
MySQL
connected
Paylocity
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the MySQL 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 · MySQL ⇄ 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.
MySQL PaylocityCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
MySQL and Paylocity integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between MySQL and Paylocity: authenticate both systems, choose the objects to sync (such as MySQL's Stored Procedures and Triggers), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both MySQL and Paylocity. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on MySQL: Database triggers — Stacksync creates deterministic triggers for internal logging and syncing (requires log_bin_trust_function_creators=ON when binary logging is enabled). On Paylocity: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the MySQL side: Stored Procedures, Triggers, Databases (Schemas), Tables, plus custom fields where MySQL 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 MySQL and Paylocity: Org and structure stay aligned; Computed and operational fields flow back; Mirror people records into the database. Groups, departments, managers, and reporting lines from Paylocity stay consistent in MySQL, so hierarchy-driven logic and permissions don't drift.
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 546 integrations available for MySQL and Paylocity.
Popular · 8 of 546
-
MySQL ⇄ Greenhouse -
MySQL ⇄ Jobvite -
MySQL ⇄ Lever -
MySQL ⇄ Namely -
Paylocity ⇄ SQL Server -
Paylocity ⇄ Postgres Heroku -
Paylocity ⇄ Airtable -
Paylocity ⇄ AWS Aurora MySQL
No integrations match .
