Migrate from Paycom to Crelate

Paycom Employee records function as candidate records when the migration scope is recruiting-focused. The four-character eecode is extracted as a legacy_id__c field in Crelate for dedupe and reconciliation. Employee first name, last name, email, phone, address, hire date, department, job title, employment status, and manager relationship all map directly to Crelate Contact fields. We flag employees with a candidate_flag custom field if they are to be surfaced in recruiting workflows, because not all Paycom employees are active recruiting prospects.

Paycom does not have a separate Company object; organizational hierarchy lives as department and division data within the Employee record. We extract distinct employer entities from the employee's company_name field (if populated) and from division or subsidiary designations, and create Crelate Company records. Each Company gets a unique company_id for subsequent Contact linking. Multiple employees from the same organization attach to one Company via the Contact-Company lookup.

Paycom's get_new_hire_custom_fields endpoint exposes client-specific text, select, and date fields on the new hire profile. These map to Crelate custom fields on Contact that we pre-create during the schema design phase. Each Paycom custom field description becomes the Crelate field label, with the logical name assigned as the API field name. Picklist-type Paycom custom fields become Crelate picklist or multi-select fields with the same option values.

Paycom background check results (status code, completion timestamp, flags) are extracted per candidate and stored as a Crelate Contact custom field for structured visibility and a Crelate Activity note for audit trail. Detailed criminal, credit, or drug screening results that cannot be stored in structured fields are documented as an Activity note with the check type and status.

Paycom Vault payroll card enrollment status (boolean flag) and card delivery method are extracted from the employee record as a Crelate Contact custom field. This is a compliance-relevant flag for candidates who receive pay via payroll card; it migrates as a structured field rather than a note so that Crelate users can filter and report on it without opening a notes record.

Paycom Employee records carry hire date, termination date, rehire date, and status change events. The current employment status (active, terminated, leave of absence) maps to a Crelate Contact custom field; historical status transitions are captured as Crelate Activity records with type = Status Change and a note carrying the effective date and previous/new status. This preserves the status audit trail without creating duplicate Contact records.

Paycom timecard data (clock-in/out, total hours, overtime flags, absence punches) is employee-owned and manager-approved. We extract a summary snapshot as a Crelate Contact custom field (last submitted hours, overtime flag) and a general Activity note with the last completed pay period summary. Full timecard history does not map to Crelate because Crelate has no timekeeping engine; detailed punch data is documented as a migration inventory item for the customer's HR admin if a timekeeping platform is selected separately.

Pre-hire benefits elections (medical, dental, vision, 401k, HSA) stored in Paycom as enrollment records tied to candidates are extracted as Crelate Contact custom fields for plan type and coverage tier, plus an Activity note with plan name, deduction amount, and effective date. Post-hire benefits data (active employee enrollments) does not migrate because Crelate has no benefits administration module; we document it as an HR inventory item.

Paycom labor allocation distributions (department codes, job codes, GL codes, cost center splits) are stored per employee and tied to payroll costing. We extract the primary cost center and GL code as Crelate Company custom fields if the Company represents a department or cost center, or as Contact custom fields if the allocation is employee-specific. Multi-distribution splits (common in nonprofit grant-funded organizations with 20+ cost center allocations) are documented in a separate labor allocation inventory sheet.

Historical payroll runs (gross pay, net pay, tax withholdings, deduction amounts) do not migrate to Crelate because Crelate has no payroll engine. We extract a payroll summary record per employee (most recent pay period gross, net, and federal tax withholding YTD) as a Crelate Contact custom field to support compensation-based recruiting tasks. Full payroll history is archived and delivered as a CSV export for the customer's payroll administrator or retained for audit purposes.

PTO accrual balances are computed by Paycom's rules engine and exposed as a current balance on the employee record. Crelate has no accrual engine, so the balance snapshot does not migrate as a functional field. We extract the as-of-date balance as a Crelate Contact custom field labeled pto_balance_snapshot__c with the effective date for reference. The customer's new PTO platform (if replacing Paycom entirely) re-computes accruals from hire date or accepts the snapshot as a starting balance.

Garnishment orders (child support, tax levies, wage assignments) carry deduction percentages computed internally by Paycom against federal and state guidelines. Crelate has no payroll engine and cannot apply garnishments. We extract the order record (begin date, amount, percentage vs. flat flag, exemption amounts, end date) as a Crelate Activity note on the Contact for the customer's HR admin to configure in the new payroll platform. The deduction computation does not migrate because it cannot be re-computed externally.