Migrate from Paycor to Recruit CRM & ATS

Paycor Employee records map to Recruit CRM Candidate profiles. Core demographic fields (name, email, phone, address) migrate 1:1. Employment tenure and original hire date map to Recruit CRM work experience entries or a custom hire_date field. Current compensation from Paycor maps to a custom currency field on the Candidate record; note that Recruit CRM does not have a native compensation management module and this field is informational only. Active employee status maps to a Candidate status of Active; terminated employees require a scoping decision (archive, move as Inactive, or exclude).

Paycor Persons records (linked to Employee and containing demographic data) merge into the Candidate record during migration. Name formats, mailing addresses, and contact preferences migrate directly. Personal email addresses map to Candidate secondary email fields. Paycor's emergency contact data has no equivalent in Recruit CRM and is flagged for documentation or archival.

Paycor Legal Entities (the organizational hierarchy root representing subsidiaries or distinct business units) require a scoping decision: they map to Recruit CRM Client records if the organization is a client company being recruited against, or to a custom organizational unit field if they represent internal corporate structure. We document the Legal Entity hierarchy during scoping and the customer decides the destination strategy before migration begins.

Paycor Job Titles map to Recruit CRM Job Order titles if creating job records for internal postings, or to a custom title field on the Candidate record for preserving employment history. Paycor's job title associations to employees and departments migrate as a current_title custom field on the Candidate. Job titles used in payroll rule filters are documented but not migrated to Recruit CRM since the ATS has no payroll rule engine.

Paycor Departments by Legal Entity map to Recruit CRM custom dropdown fields on the Candidate record. We preserve department codes, names, and parent-child relationships in a custom departments field. Organizations with multiple subsidiaries may choose to map departments as Tags on the Candidate record for segmentation. The department-level cost center hierarchy does not map to any Recruit CRM object and is documented for the customer's GL team.

Paycor Work Locations (geographic locations tied to Legal Entities for tax jurisdiction and overtime rules) map to candidate address fields in Recruit CRM for candidates who relocated during employment. Tax jurisdiction and FLSA overtime rules associated with Work Locations have no equivalent in Recruit CRM and are documented for the customer's payroll team if payroll is retained on a separate platform.

Paycor Time Off Plans define accrual rules; Time Off Types define categories (PTO, sick, etc.). Accrual rates, carryover rules, and current balances have no equivalent in Recruit CRM's recruiting data model. We export current PTO balances as informational text in a custom pto_balance__c field on the Candidate record and archive accrual transaction history separately. The customer decides whether balances migrate or are archived based on whether the receiving payroll system will recalculate.

Paycor Pay Groups define grouping rules for compensation and benefits eligibility, and Labor Categories define job classification for costing. Neither concept exists in Recruit CRM. We document Pay Group and Labor Category assignments per employee as a CSV export for the customer's payroll team. If the destination payroll platform is known, we provide a Pay Group mapping to that system's pay group equivalent.

Paycor Employee Earnings (hourly rates, salary, bonus) and time punch data have no equivalent in Recruit CRM. Hourly rate information can be stored as a custom salary_expectations or current_salary field on the Candidate record if relevant to recruiting, but accrual history, punch data, and payroll registers are archived. We recommend a payroll export as a PDF or structured file stored in the candidate document section if audit retention is required.

Paycor benefit deduction codes and garnishment orders are payroll compliance records with no place in a recruiting ATS. We export active deduction codes and garnishment amounts as a structured CSV for the customer's payroll team. EDI deduction format requirements are documented for the receiving payroll platform's import specification. We do not map these to Recruit CRM fields because candidate benefit information is not collected or stored in the ATS model.