Two-way sync
Changes in Azure Synapse Analytics or Paylocity instantly reflect in both systems. No stale data, no manual imports.
Keep Azure Synapse Analytics 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.
Workforce data is some of the most requested data in the warehouse and some of the most awkward to move: the record types are many, the fields carry sensitive personal information, the APIs are strict, and hand-built extract jobs go stale or break quietly. Whether Paylocity is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in Azure Synapse Analytics next to everything else the company measures.
Stacksync syncs Company Codes, Custom Fields, Employees, Onboarding from Paylocity into tables in Azure Synapse Analytics continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Azure Synapse Analytics, such as headcount rollups, cost allocations, or attrition risk flags, can be written back to fields in Paylocity where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.
Analysts combine Paylocity's workforce records with finance, product, or operational data already in Azure Synapse Analytics for reporting the HR system cannot produce on its own.
Because changes stream continuously, reports query current workforce data rather than waiting for an overnight load window to finish.
A continuously synced copy in Azure Synapse Analytics gives you a durable, queryable record of how Paylocity's records change over time, for headcount planning and audit questions.
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.
| Azure Synapse Analytics objects | Paylocity objects | How this pairing syncs | |
|---|---|---|---|
| Materialized views Precomputed aggregates that speed reads of frequently synced result sets. | 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. | Materialized views is specific to Azure Synapse Analytics and Direct Deposit to Paylocity — each maps to any object or custom field on the other side. | |
| SQL pools Dedicated or serverless compute contexts that determine how and where queries run. | 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. | SQL pools is specific to Azure Synapse Analytics and Pay Statements to Paylocity — each maps to any object or custom field on the other side. | |
| Tables (dedicated SQL pool) Distributed warehouse tables that serve as sync destinations for analytics workloads. | Company Codes Read-only reference codes and descriptions (cost centers, departments, positions) used to validate field mappings on employee writes. | Tables (dedicated SQL pool) is specific to Azure Synapse Analytics and Company Codes to Paylocity — each maps to any object or custom field on the other side. | |
| External tables Tables over files in the data lake, queried through serverless SQL and often read-only in syncs. | Custom Fields Read-only company-specific custom fields returned by category, used to enrich the employee record downstream. | External tables is specific to Azure Synapse Analytics and Custom Fields to Paylocity — each maps to any object or custom field on the other side. | |
| Views Curated projections used when downstream tools should not read base tables directly. | 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. | Views is specific to Azure Synapse Analytics and Employees to Paylocity — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that separate staging, integration, and presentation layers. | 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. | Schemas is specific to Azure Synapse Analytics and Onboarding to Paylocity — each maps to any object or custom field on the other side. |
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.
DetectionStacksync polls Azure Synapse Analytics for changes on an incremental schedule, reading only records changed since the previous pass. Polling on watermark columns.
DeliveryEach detected change is written to Paylocity through its API, with automatic retries and rate-limit backoff.
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 Azure Synapse Analytics as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Synapse Analytics–Paylocity connection.
Changes in Azure Synapse Analytics or Paylocity instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Azure Synapse Analytics or Paylocity data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Azure Synapse Analytics or Paylocity record.
Track your Azure Synapse Analytics ⇄ Paylocity sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Azure Synapse Analytics and Paylocity.
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 Azure Synapse Analytics 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.
Pick the Azure Synapse Analytics 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.
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 Azure Synapse Analytics and Paylocity: authenticate both systems, choose the objects to sync (such as Azure Synapse Analytics's Materialized views and SQL pools), 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 Azure Synapse Analytics and Paylocity records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Azure Synapse Analytics and Paylocity connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Azure Synapse Analytics–Paylocity integration in-house.
Yes — Stacksync ships production-grade connectors for both Azure Synapse Analytics and Paylocity. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Azure Synapse Analytics: Polling on watermark columns; Synapse SQL pools do not expose log-based CDC for downstream consumers. 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 Azure Synapse Analytics side: Tables (dedicated SQL pool), External tables, Views, Schemas, plus custom fields where Azure Synapse Analytics exposes them. On the Paylocity side: Company Codes, Custom Fields, Employees, Onboarding. Stacksync auto-detects both schemas and converts types between the two systems.
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 541 integrations available for Azure Synapse Analytics and Paylocity.