Migrate from ZingHR to Recruit CRM & ATS

ZingHR employee records that were hired through the Talent Acquisition module map to Recruit CRM Candidate records. We extract name, contact details, employment history, and skills from the Attribute Master API. Employee status (Active, On Notice, Separated) maps to Recruit CRM candidate status. Separated employees land in Recruit CRM as inactive candidates for talent-pool reuse. Custom employee attributes from the Attribute Master API map to Recruit CRM custom fields enumerated during scoping.

ZingHR job postings created in the Talent Acquisition module map to Recruit CRM Job records. We extract job title, description, location, employment type, and skills requirements. Job status (Open, Closed, On Hold) maps to Recruit CRM Job status. Active job postings are migrated first to preserve pipeline continuity.

ZingHR candidate profiles created during the recruitment process map directly to Recruit CRM Candidate records. We preserve resume/CV as an attached document in Recruit CRM. Candidate source (referral, job board, direct application) from ZingHR maps to a Recruit CRM custom field or source picklist value.

ZingHR digital onboarding tasks and checklists map to Recruit CRM's task assignment capability. We extract onboarding step names, responsible parties, due dates, and completion status. Onboarding in Recruit CRM is task-based rather than structured-form-based; we transform ZingHR's checklist format into a Recruit CRM task list with due dates and owner assignments. A written handoff document describes the original checklist structure for manual reconstruction if full fidelity is required.

ZingHR department hierarchies map to Recruit CRM Teams or Divisions. We extract department names, cost centers, and reporting relationships. Recruit CRM does not have a native org-chart object; we map department names to Recruit CRM's team structure or a custom division field on the Job record.

ZingHR manager-employee associations map to Recruit CRM's recruiter assignment on Candidates and Jobs. We extract the current active reporting lines from ZingHR's Attribute Master API and assign the corresponding recruiter as the Candidate owner or Job assignee in Recruit CRM. Any pending Maker-Checker bulk manager-change records are flagged and held from migration until resolved in ZingHR or manually re-created in Recruit CRM.

ZingHR company-specific custom attributes exposed via the Attribute Master API enumerate during scoping. We map each custom field to a Recruit CRM custom field of matching type (text, picklist, number, date). Recruit CRM supports custom fields on all standard objects via the settings UI. Custom fields are pre-created in Recruit CRM before any record migration begins to avoid type-mismatch errors during import.

ZingHR employee documents including offer letters, ID proofs, and experience certificates map to Recruit CRM candidate document attachments. We extract document name, type, and upload date. Documents are downloaded individually from ZingHR's ESS and re-uploaded to Recruit CRM as candidate attachments. The original document category in ZingHR maps to a Recruit CRM document type picklist value.

ZingHR attendance punch-in/punch-out data does not have a structural equivalent in Recruit CRM, which is a recruitment ATS rather than a timekeeping system. We export attendance summaries as a CSV report and archive it as a downloadable artifact for the customer's HR or finance team. Attendance data is not imported into Recruit CRM's candidate or job records.

ZingHR leave entitlement, accrual history, and used/taken balances do not migrate to Recruit CRM. Leave management is outside Recruit CRM's scope as a recruitment ATS. We export current leave balances as of migration date as a CSV report for the customer's HR team to maintain in a separate system or manual records. Leave data is not imported into Recruit CRM.

ZingHR payslip data including earnings, deductions, and net pay do not have a destination in Recruit CRM. Payroll history is an HRMS function not supported by a recruitment ATS. We export payroll registers as a compliance-ready archive CSV organized by pay period and employee. Payslips are not imported into Recruit CRM's candidate or placement records.

ZingHR performance review records including goals, ratings, and reviewer comments are outside Recruit CRM's recruitment ATS scope. We export performance data as a CSV report with employee ID, review period, goal alignment, and rating for the customer's HR team to archive separately. Performance data is not imported into Recruit CRM.