Migrate from ZenHR to Crelate

ZenATS Candidate records map to Crelate Candidate as the primary migration object. We map first name, last name, email, phone, current company, current title, source, and tags directly. Candidate status in ZenATS (active, placed, rejected, withdrawn) maps to Crelate's Candidate Status field. We preserve the original ZenATS candidate_id as a custom field zenats_candidate_id__c for reconciliation. SMS and email communication bodies sent to candidates are not exposed via the ZenHR API; we transfer metadata (timestamps, template names) only and flag the gap during scoping.

ZenATS Vacancy records map to Crelate Job. The ZenATS vacancy title becomes the Job title, job_description maps to the Job description field, and status (open, on hold, filled, cancelled) maps to Crelate Job status. Department, location, employment type, and salary range from ZenATS map to their Crelate equivalents. We preserve stage history with each stage transition timestamp from ZenATS as notes on the Crelate Job record.

ZenATS pipeline stages (Applied, Screening, Interview, Offer, Hired, Rejected, etc.) map to Crelate Job Stages configured in the destination before migration. Stage probability percentages from ZenATS set the Crelate stage weighting for reporting. We sequence stage values in order matching the ZenATS pipeline so that Crelate reporting reflects the original funnel conversion rates.

ZenATS interview records map to Crelate Activity records (type = Interview) linked to the Candidate and Job. Interviewer name, date, duration, interview type, and interviewer notes transfer as Activity details. If ZenATS stores scorecards or structured feedback, we map those to Crelate Activity custom fields or linked Notes attached to the Activity.

ZenHR Employee records that represent active or past candidates in the recruiting context map to Crelate Candidate or Contact depending on the recruiting workflow. We scope this mapping during discovery: employees hired through ZenATS pipelines migrate as Candidates with status changed to Hired; passive talent stored in ZenHR without a vacancy association migrates as Crelate Contacts. Name, email, phone, department, and job title map directly. Payroll compensation fields do not migrate because Crelate has no payroll schema.

Candidate resumes, cover letters, and supporting documents stored in ZenATS attach to the corresponding Crelate Candidate record via Crelate's resume and document upload API. We map document type, upload date, and expiry information as metadata on the Crelate Attachment. Document binary transfer uses the Crelate bulk attachment API with rate-limit handling.

ZenHR Users who have access to ZenATS map to Crelate Users by email match. ZenHR role names (Recruiter, Hiring Manager, Admin) map to Crelate User Roles and Permissions. Users without ZenATS access are excluded from the Crelate migration scope. Active/inactive status and last login date from ZenHR transfer as User metadata fields in Crelate.

ZenHR tenant-specific custom fields on Candidate and Vacancy objects are discovered during pre-migration field audit. Each custom field is typed (text, number, date, picklist, boolean) and mapped to a Crelate Custom Field of equivalent type. Custom picklist values in ZenATS are replicated as Crelate picklist options. Any custom field with no Crelate equivalent is flagged with a recommendation for a custom field or note-field workaround.

ZenHR Branches that represent physical office locations associated with vacancies map to Crelate Job Location. We map branch name, address, and city from ZenHR Branch to the Crelate Location field. ZenHR organizational levels and positions do not map to Crelate because Crelate has no HR org hierarchy; we document these as out-of-scope in the migration report.

HR Letters generated in ZenATS for candidates (offer letters, onboarding checklists, onboarding schedules) map to Crelate Notes attached to the Candidate record with a type indicating the letter purpose. The e-signature audit trail migrates as note metadata. HR letter templates are documented in the migration report for manual rebuild in Crelate's template system.

ZenHR Timeoff records represent leave balances for employees, not recruiting availability. Crelate has no leave management schema. Timeoff data is excluded from the Crelate migration scope entirely. If the customer requires leave tracking post-migration, we recommend a separate HRIS platform (BambooHR, Rippling, or Workday) running in parallel. We document this as an out-of-scope data category in the migration report.

ZenHR payroll runs, financial transactions, loans, overtimes, and EOSB calculations have no equivalent in Crelate. Crelate handles placement invoicing and client billing for recruiting fees, but not employee payroll. We exclude all financial and compensation data from the Crelate migration scope. If the customer needs historical payroll records for compliance or audit, we recommend exporting those as PDFs or reports from ZenHR before the migration window and storing them outside Crelate.