Migrate your Paycom data

Employee records are the primary object in Paycom's single database. Each employee has a four-character eecode as the primary identifier. We map eecodes to the destination system's employee IDs and preserve all standard fields (name, address, employment type, pay type, state tax elections). Custom New Hire fields per client are captured via the get_new_hire_custom_fields endpoint and mapped as custom employee properties.

Payroll runs in Paycom are effective-dated events tied to employees. We extract gross pay, net pay, federal and state tax withholdings, deduction amounts and pay periods. Historical runs are preserved as read-only records. Off-cycle payments and shift differentials are included as line items within the run.

Timecard data is employee-owned in Paycom—employees submit hours and make their own edits with manager approval. We extract clock-in/out timestamps, total hours, overtime flags and any absence punches. Pay rates derived from timecard entries require cross-referencing with the employee pay type record since Paycom stores both approval status and pay computation separately.

PTO accrual rules are configurable per employee or per policy group in Paycom. Accrual balances are computed by the system and exposed via the employee record. We extract current balance, accrual rate, carryover limits and used hours. Accrual logic (front-loaded vs. accrual-per-hour) requires field mapping since some plans use custom accrual schedules not surfaced in standard API fields.

Benefits elections (medical, dental, vision, 401k, HSA) are stored as enrollment records tied to employees and plan years. We extract plan names, coverage tiers, deduction amounts and effective dates. Voluntary benefit codes and employer contribution amounts require explicit mapping because Paycom uses internal deduction codes that vary by client configuration.

Garnishment orders (child support, tax levies, wage assignments) are stored as deduction records with calculation rules. We extract order amounts, percentage vs. flat deduction logic, begin/end dates and exemption amounts. The rules engine for computing maximum allowable deductions is proprietary; we capture the order as entered rather than attempting to re-compute the deduction.

Labor allocation distributions allow payroll costs to be split across departments, jobs or GL codes. The get_labor_allocation_distributions endpoint returns category codes, detail codes, GL codes and tipped-job flags. These are optional per employee and require pre-migration scoping to determine which employees use allocations and which cost centers are active.

Vault is Paycom's proprietary payroll card product. Employee enrollment status and card issuance records are stored in the employee record. We extract vault enrollment as a boolean flag and card delivery status. Active card balances are held at the card processor, not in Paycom, so we do not migrate card balances.

Enhanced Background Checks are a pre-hire feature. Results are stored per candidate with status codes and completion timestamps. We extract the check status, completion date and any flags. Detailed criminal/credit report content is held by the third-party screening vendor and is not accessible via Paycom API.

Custom fields on the new hire profile are unique per client and can be type text, select or date. The get_new_hire_custom_fields endpoint exposes field descriptions and values per eecode. We map these to destination custom employee properties, applying the same type classification so selects land as picklist fields rather than free text.