Migrate your Paylocity data

Employees are uniquely identified by the composite of Employee ID plus Company ID. This composite key must be preserved in the destination system — mapping by Employee ID alone risks duplicate records if the customer has multiple Paylocity Company IDs. We validate both keys during scoping and apply them consistently at import time.

Name, address, contact info, hire date, job title, department, employment status, and termination data migrate directly. These are well-structured fields with stable schema across Paylocity editions.

Pay rates, salary changes, bonus amounts, and pay frequency are available via API but the compensation record structure varies by pay type (hourly vs. salary vs. commission). We apply pay-type-aware field mapping to the destination before writing.

Paylocity exposes employee benefit elections, carrier assignments, and deduction amounts via the Benefits API. The underlying benefit plan definitions (plan rules, contribution tiers) are admin-managed objects not exposed via API — we migrate enrollment records and election snapshots, not plan design. Carrier mapping is required if the destination uses different carrier identifiers.

Historical pay run records are retrievable via the Pay Entry API. We migrate gross pay, net pay, tax withholdings, and deduction line items as reference records. Retroactive pay adjustments cannot be re-posted — we capture the final state as of the migration date and treat it as a balance snapshot in the destination.

W-4 federal allowances, state withholding allowances, and supplemental tax rates are per-employee settings that vary by tax jurisdiction. We map these to the destination system's tax election fields, applying jurisdiction-specific defaults where the destination uses different naming conventions.

Current accrual balances and available-snapshot data are available via API. However, accrual rate logic (monthly accrual vs. anniversary-based, carryover caps, negative-balance rules) differs by employer configuration. We migrate balance snapshots and let the destination system recalculate accruals going forward.

Organizations with multiple Paylocity Company IDs may represent separate legal entities, subsidiaries, or benefit divisions. We map each Paylocity Company ID to the corresponding destination entity — consolidating into one organization or splitting across multiple destination companies based on the customer's target structure.

Custom employee properties are user-defined fields with variable data types (text, number, date, dropdown). The schema and allowed values are customer-specific and not always consistently named across modules. We perform field-level discovery during scoping and apply explicit value mapping at import time.

Documents stored in the Employee Profile — offer letters, signed agreements, certifications — are migratable as binary file imports. We map file type, employee association, and document category to the destination's document storage model. Access control inheritance is applied based on the destination system's permissions model.