Migrate from ChartHop to Recruit CRM & ATS

ChartHop People records map to Recruit CRM Candidates. Core fields (name, email, phone, job title, department) migrate 1:1. Reporting manager relationships do not map natively to Recruit CRM's candidate model since Recruit CRM does not store employee hierarchy; we preserve the manager reference as a custom text field manager_name__c. Compensation fields (base, variable, equity) migrate as custom fields on the Candidate record. Active employment status maps to candidate availability status in Recruit CRM.

ChartHop Jobs (open or filled positions) map to Recruit CRM Vacancies. Job title, department, job level, and compensation band migrate. Job status (active, closed, on-hold) maps to Recruit CRM vacancy status. Headcount planning scenario data attached to a Job (proposed hires, budget impacts) cannot migrate because ChartHop does not expose scenario data via API; we flag active scenarios during scoping for manual re-creation.

ChartHop department hierarchy (parent-child relationships) maps to Recruit CRM organizational structure as a custom Department field on Candidate and Vacancy. We reconstruct the full department tree as a flat list plus parent references. Matrix team affiliations (cross-functional reporting) do not map to Recruit CRM's standard schema and are flagged for admin review.

Jobvite requisitions synced to ChartHop migrate to Recruit CRM Vacancies with job requisition ID preserved. Status (open, filled, cancelled) maps to vacancy status. Internal transfers synced from Jobvite to ChartHop are NOT supported by ChartHop and will not appear in the export; we flag internal transfer records for manual re-entry. Email matching between ChartHop and Jobvite (required by ChartHop's connector) is audited during pre-migration validation.

Greenhouse job data synced to ChartHop migrates to Recruit CRM Vacancies. Greenhouse custom fields require custom field mapper setup in ChartHop before export; we audit whether custom field mappers are configured and whether they follow ChartHop's required endpoint-prefixed naming convention (e.g., job.custom_fields.greenhouse_field). Missing or misconfigured mappers result in data gaps that we surface before migration.

ChartHop compensation fields (base compensation, cash compensation, variable pay, equity, total compensation, compensation band) migrate as custom fields on the Recruit CRM Candidate record. Each compensation component maps to a separate custom field (base_comp__c, variable_comp__c, equity__c, compensation_band__c). Compensation cycle configurations (merit, promotion) are planning data and do not migrate; we export a snapshot of the most recent cycle values as reference documents.

ChartHop unlimited custom fields require a governance audit before migration because the platform enforces no naming conventions or deduplication. We identify duplicate or near-duplicate custom fields (e.g., 'Comp Band' vs 'Compensation Band') and surface them for customer review. Each validated custom field maps to an equivalent Recruit CRM custom field with appropriate data type (text, date, picklist, number). Field-level access controls from ChartHop do not transfer.

ChartHop file attachments per employee profile (miscellaneous or field-linked) migrate to Recruit CRM candidate attachments. All files must be under 100MB per ChartHop's limit. We use ChartHop's file export mechanism to retrieve documents and attach them to the corresponding Candidate record. File type categorization does not map to Recruit CRM categories and is preserved as a note or custom text field.

Current PTO balances as of the migration snapshot migrate as custom fields on the Candidate record (pto_balance__c). Historical accrual logs are available via a separate ChartHop export pass but Recruit CRM does not have a native accrual tracking model; we recommend exporting accrual history as a reference spreadsheet for the customer's HR admin to maintain separately if needed.

Performance review cycles, review forms, and submitted responses stored in ChartHop's Performance module do not map to Recruit CRM objects. Recruit CRM is a recruitment ATS, not a performance management system. We export review metadata (cycle names, form structures) and anonymized response aggregates as reference documents. Review templates with custom question types are flagged for manual re-creation if needed at the destination HRMS.

ChartHop Goals (company, team, and individual objectives with progress tracking) do not map to Recruit CRM objects. Recruit CRM does not have a goals or OKR module. We export goal hierarchies and progress values as a reference document. Cascading goal dependencies (where child goals roll up to parent goals) cannot be preserved and are flagged for manual re-creation if needed at the destination platform.