Migrate from Paycom to Recruit CRM & ATS

Paycom employee records map to Recruit CRM candidate profiles using the employee's email address as the primary dedupe key. First name, last name, personal email, phone, address, eecode (preserved as a custom field), hire date, employment status, and job title transfer directly. If the employee record includes a resume attachment, we extract it and attach it to the Candidate record in Recruit CRM. Active employees map to active candidates; terminated employees map to inactive candidates with their termination date preserved. If Recruit CRM already contains candidate records from a prior import, we run an email-based deduplication pass before upsert to avoid creating duplicate profiles.

Paycom job title and department from the employee record map to the candidate's employment history (position held) field in Recruit CRM. The department name is also mapped to a Job Position record in Recruit CRM so that the candidate's experience aligns with open job positions in the system. If the same job title appears across multiple departments, we preserve the full combination as a single experience entry.

Paycom client-specific custom fields on the new hire profile (exposed via the get_new_hire_custom_fields endpoint) map to Recruit CRM's custom candidate fields. We map field types directly: text fields to text, date fields to date, and select fields to picklist. Custom field labels are preserved with a paycom_ prefix to distinguish them from native Recruit CRM fields. During scoping, we retrieve the full custom field schema from Paycom via API and configure matching fields in Recruit CRM before migration begins.

Paycom employment status (active, on leave, terminated) maps directly to candidate status in Recruit CRM. Active employees become active candidates; employees on leave become candidates with a leave status flag; terminated employees become inactive candidates. The termination date transfers as the end date of the most recent position entry in the candidate's experience history.

Paycom payroll run history does not map to any standard ATS object in Recruit CRM because Recruit CRM does not have a payroll module. We flag this during scoping: if the customer requires payroll reference data (most recent pay date, pay frequency, exempt/non-exempt classification) for compliance or background-verification purposes, we extract the latest payroll run record per employee and store it as a read-only custom text field on the candidate record. This is a reference-only field, not a payroll object.

Benefits elections (medical, dental, vision, 401k, HSA) stored as enrollment records in Paycom have no equivalent object in Recruit CRM's ATS schema. We extract the most recent benefits enrollment summary per employee and store it as a JSON-formatted custom field on the candidate record for reference. Customers who need benefits data in a dedicated HRIS retain it in Paycom or a separate HR system and use Recruit CRM exclusively for recruiting.

If Paycom stores the employing company's legal name or a parent-organization field, it maps to the Client record in Recruit CRM. For organizations migrating from Paycom to Recruit CRM as a full recruiting function replacement, the Client record represents the company doing the hiring. We create the Client record before any candidate import so that the client reference is available at insert time. Multiple Paycom entities (subsidiaries or branches) map to multiple Client records.

Enhanced background check results stored per candidate in Paycom (check status, completion date, flags) migrate to Recruit CRM as a checklist item attached to the candidate or as a custom status field. Detailed criminal records, credit checks, and drug screening results are not migrated due to compliance and data-minimization obligations; we extract the check status and date only. The customer's compliance team must review and re-run background checks if required by jurisdiction after migration.

Vault payroll card enrollment status and card delivery records are stored as a boolean flag and delivery date in the Paycom employee record. We extract enrollment status and transfer it as a custom field on the candidate record. Recruit CRM does not have a payroll card object. This field is informational only and does not affect ATS workflows.

Garnishment orders (child support, tax levies, wage assignments) stored as deduction records in Paycom are excluded from migration to Recruit CRM. Recruit CRM has no garnishment or payroll deduction module. We document garnishment order counts and total deduction amounts in the migration inventory report so the customer's payroll administrator can re-enter them in the destination payroll system (Paycom or a replacement). Garnishment calculation rules computed internally by Paycom are opaque and cannot be independently re-computed.