Migrate from ChartHop to Zoho Recruit

ChartHop People records map to Zoho Recruit Candidates, but the mapping requires a clear scope decision during scoping. If the migration目标是迁移正在招聘中的职位对应的候选人（现有员工申请内部职位），则People记录转为Candidate并标记为内部申请人。如果迁移目标是建立一个新的候选人数据库，则People记录作为历史数据导入，但需要理解Zoho Recruit的Candidate对象设计用于跟踪求职者而非现任员工。员工的compensation、reporting manager等HR特定字段需要在Candidate上创建自定义字段承接，或作为参考文档存档而非实时迁移。我们使用ChartHop API导出People数据，转换为Zoho Recruit Candidate CSV格式，确保Last Name字段（非可选）有值，对于没有姓氏的记录填充为'Not Provided'或类似占位符。

ChartHop Jobs map directly to Zoho Recruit Job Openings. Job title, department assignment, employment type (full-time, part-time, contract), and job status (active, closed, on-hold) migrate as Job Opening fields. Job status in ChartHop (active/closed/on-hold) maps to Zoho Recruit's Job Opening status field. The Job Opening's associated department links to the migrated Department record via the department lookup relationship. Open positions with approved headcount in ChartHop that are actively recruiting map cleanly; positions marked as future headcount or planning scenarios without an active requisition do not generate Job Openings at migration time.

ChartHop department hierarchy maps to Zoho Recruit's Department module. The parent-child department relationship migrates as the Department hierarchy in Zoho Recruit, preserving the reporting structure. Department head (manager) assignments migrate as a custom field on Department since Zoho Recruit's Department module does not have a native manager field. Matrix team affiliations and cross-functional reporting lines that exist in ChartHop cannot be modeled in Zoho Recruit's flat department structure and are flagged as requiring manual documentation or migration to a custom module if the customer's Zoho Recruit plan supports custom module creation.

ChartHop file attachments per employee profile migrate as Zoho Recruit Attachments linked to the corresponding Candidate record. File type categorization (miscellaneous vs field-linked) maps to Zoho Recruit's attachment structure. All files must be under 100MB per ChartHop's export limit; files exceeding this threshold are flagged for manual handling. We use ChartHop's file export mechanism to retrieve documents and batch-upload them to the corresponding Zoho Recruit Candidate record via the Zoho Recruit REST API with multipart file upload handling.

ChartHop compensation fields (base compensation, variable pay, equity, total compensation, compensation band) do not have native Zoho Recruit Candidate fields. We create custom fields on the Candidate module to capture this data if the customer requires it for internal mobility or historical reference. Custom field limits apply: Standard plan allows 50 custom fields per module, Professional allows 300, and Enterprise allows 300. We audit the compensation field count during scoping and coordinate with the customer's Zoho admin to ensure the plan tier supports the required custom field count before migration. Compensation data is typically treated as sensitive and requires the customer's explicit approval for migration scope.

ChartHop Performance Review cycles, review forms, and submitted responses do not have a Zoho Recruit equivalent. Zoho Recruit is a recruitment ATS and does not include performance management or review cycle functionality. We do not migrate performance review data as records. If the customer requires this data for HR records retention, we export the review data as a reference document and deliver it alongside the migration for manual re-entry into a performance management system (Zoho People, Culture Amp, Lattice, or another dedicated tool). Review templates with custom question types are not migratable.

ChartHop Goals (company, team, and individual objectives with progress tracking) do not map to any Zoho Recruit object. Zoho Recruit's module set covers recruitment workflows only. Goals hierarchies, progress percentages, goal dependencies, and alignment relationships cannot be migrated. We export goal data as a structured CSV for the customer's HR team to re-create in a dedicated goals management platform. Goals linked to specific People records in ChartHop do not preserve the live link in Zoho Recruit.

ChartHop Engagement Survey responses, aggregate results, participation rates, and benchmark comparisons do not have a Zoho Recruit equivalent. Survey metadata (question text, benchmarks) and anonymized response data cannot be imported into Zoho Recruit's schema. We export survey data as reference documents for the customer's HR team if retention is required. Survey results should be migrated to a dedicated engagement platform (Culture Amp, Qualtrics, Culture Index) as a separate migration scope.

ChartHop PTO balances, accrual policies, and time-off request history do not map to Zoho Recruit objects. Zoho Recruit does not include time-off management or HRIS functionality. We export current balances and accrual logs as a separate data pass for the customer's HR team to re-enter into their HRIS (Zoho People, Gusto, ADP, or another platform). Historical time-off requests are not migratable and are flagged for archival export only.

ChartHop Matrix Teams model cross-functional collaboration where employees report to multiple leaders. This non-standard structure has no Zoho Recruit equivalent. We export matrix team assignments as a reference CSV with employee email, matrix team name, and secondary manager relationship. The customer's HR team documents this manually in Zoho Recruit if required, typically as a custom module or as tag values on the Candidate or User record if the plan supports custom fields.

ChartHop Headcount Planning scenarios are sandboxed planning objects inaccessible via API. The scenario engine is tightly coupled to ChartHop's planning workflow and cannot be retrieved programmatically. We flag the existence of any active or archived scenarios during pre-migration scoping and export them as reference documents (PDF or XLSX) for the customer's HR and Finance teams to re-create manually in Zoho Recruit or in a dedicated headcount planning tool. This is a ChartHop platform limitation, not a Zoho Recruit gap.

ChartHop Jobvite connector data (requisition status, candidate associations synced from Jobvite) migrates as part of the Job Opening import. Internal transfers that existed in ChartHop's Jobvite sync do not have a Zoho Recruit equivalent and are flagged for manual re-entry. The Jobvite connector state (last sync timestamp, connection status) is not migratable and requires re-authentication with Jobvite post-migration if the customer continues to use Jobvite as their ATS alongside or instead of Zoho Recruit.