Migrate from Paycor to Crelate

Paycor Person records filtered by recruiting status map to Crelate People. Standard fields (name, email, phone, address) migrate 1:1. Paycor candidate source, employment eligibility (I-9), and pay rate fields map to Crelate custom fields on the People record. Paycor's candidate status and stage values require mapping to Crelate's pipeline stage taxonomy during transformation. Duplicate detection uses email as the primary dedupe key with a secondary match on phone number.

Paycor Company records map to Crelate Company. Company name, domain, address, and industry map directly. Companies used as client references in Paycor recruiting become Crelate Companies with the client flag set. We flag any Company records with no associated recruiting activity for archival rather than live migration to reduce Crelate clutter.

Paycor Job postings map to Crelate Job records. Job title, job description, status (open, filled, closed), and work location map directly. Paycor's employment type, remote work flag, and salary range fields migrate as Crelate custom fields since Crelate Job standard fields do not cover all Paycor position attributes. Job description requires a content transform: Paycor stores descriptions as rich text; Crelate Job descriptions are plain text, so we strip HTML formatting during extraction.

Paycor hiring pipeline data maps to Crelate Opportunity, with the Paycor job requisition linked as a custom field on the Opportunity. Pipeline stage names from Paycor require explicit mapping to Crelate Opportunity stage names (e.g., Application Received, Phone Screen, On-site, Offer, Hired) during transformation. We run a stage reconciliation against Crelate's opportunity stage configuration before migration begins so the target stages exist before records insert.

Paycor candidate tags and source attributions map to Crelate Tags applied to the People record. Tags used for talent pool segmentation (e.g., sourcer, referral source, skill tag) migrate as Crelate Tags; taxonomy alignment happens during scoping so the destination tag list is pre-built before migration. Tags that represent business process state rather than talent attributes require a separate review with the customer to determine the correct Crelate placement.

Paycor engagement notes attached to candidate or employee records migrate as Crelate Notes linked to the People record. Rich text formatting is preserved where Crelate's note format allows. We exclude notes from Paycor's performance review module (one-on-ones, compensation reviews) because these represent HR evaluation data that has no natural placement in Crelate's recruiting note structure; these are flagged for separate archival export.

Paycor Employee records from the HR module have no native equivalent in Crelate. Crelate People records are designed for candidates and contacts, not full HR profiles. We scope this mapping as configuration: if the customer uses Paycor primarily for recruiting and wants employee background data accessible in Crelate for backgrounding and onboarding, we import key fields (name, contact, employment eligibility) as custom fields on the People record. Payroll, compensation, benefits, and HR classification data is excluded and flagged for archival to a separate system or document archive.

Paycor payroll registers, pay stubs, tax filings, and garnishment orders do not migrate to Crelate. Crelate is an ATS and recruiting CRM; it has no payroll processing, tax filing, or garnishment management capability. We flag payroll records for export to a compliance archive (ResNav Solutions or similar) before cutover and deliver a written list of payroll data locations requiring archival. These records must not be deleted from Paycor until the archive is confirmed and a legal hold review is completed.

Paycor Time Off Plans, accrual rates, and current PTO balances have no Crelate equivalent. Crelate does not manage time-off tracking or leave balances. We exclude these records from migration and flag them for retention in Paycor or export to the customer's chosen HR platform post-migration. PTO balance data that affects employee onboarding eligibility (e.g., accrued vacation that carries over) requires a separate export reviewed by the customer's HR team before the new HR system is configured.

Paycor benefit deduction codes, garnishment orders, and insurance carrier feeds do not migrate to Crelate. Crelate has no benefits administration module. We export deduction and garnishment data for the customer's HR team to enter into their chosen HR platform post-migration. EDI benefit feed configurations from Paycor (a known pain point cited in G2 and Reddit reviews) are documented separately as an integration note for the new HR platform rather than migrated as data records.

Paycor organizational hierarchy objects (Departments by Legal Entity, Job Titles, Work Locations, Pay Groups, and Labor Categories) map as Crelate custom fields on Job and People records rather than as native objects. Crelate does not have a native org hierarchy model. We create custom fields (department, job title, work location, pay group) on the appropriate Crelate record type during pre-migration setup so that organizational context from Paycor is preserved at the field level for reporting and filtering in Crelate.

Paycor HR documents (I-9s, W-4s, employee policies, onboarding paperwork) are stored separately from the Employee record and require specialized extraction. Crelate does not have a native HR document management system. We coordinate with a document archive partner (ResNav Solutions, TAP Innovations) to extract these at scale and deliver them as a structured archive package. I-9 and W-4 records must be retained per federal compliance requirements regardless of platform change, and we flag this retention obligation during pre-migration scoping.