Migrate from ChartHop to Crelate

ChartHop People records map to Crelate Candidates. Standard fields including name, title, department, manager, email, phone, start date, employment status, and location migrate as typed Candidate fields. Compensation fields (base salary, variable pay, equity, total comp) have no standard Crelate equivalent and are stored in custom fields created during schema design. Employee type (full-time, part-time, contractor) maps to a Candidate custom field. Active employees migrate as active Candidates; terminated employees migrate with status set to Archived or Inactive depending on the customer's retention policy.

ChartHop Jobs represent open or filled positions with title, department, level, and compensation band. Open ChartHop Jobs map to Crelate Job Orders with title, department, location, and employment type preserved. Filled positions in ChartHop may map to placed Candidates in Crelate if the customer wants historical placement records; otherwise they are treated as closed job orders. Job status (active, closed, on-hold) maps to Crelate Job Order status values configured during migration.

ChartHop Department records map to Crelate Companies if the customer uses Crelate's Client relationship model for internal departments, or to a custom Department picklist field on the Candidate record if Crelate is used exclusively for internal recruiting. We use the customer's Crelate usage pattern to determine which mapping applies. Parent-child department hierarchy is stored as a custom text field on the Department record.

ChartHop's native manager field stores a person's direct supervisor as a structured relationship. Crelate has no native org chart or reporting relationship field on Candidate. We create a custom Manager field on the Candidate record that stores the manager's name and email as text. This preserves the reporting relationship for reference but does not create a hierarchical query structure in Crelate.

ChartHop Matrix Teams model cross-functional collaboration where employees report to multiple leaders. Crelate does not support matrix reporting as a native structure. We export matrix team assignments as tag records linked to each affected Candidate. Tags are created in Crelate with names matching ChartHop team names, and CandidateTagAssignment records link each person to their matrix teams. The customer reviews the tag list during scoping to confirm naming conventions.

ChartHop custom fields (text, date, multiple choice, yes/no, calculated) map to Crelate custom fields of equivalent data type. We identify and surface duplicate or near-duplicate custom fields during pre-migration review (e.g., 'Comp Band' vs 'Compensation Band') and the customer chooses a consolidation action before schema creation. Crelate custom field types include Short/Long Answer, Picklist, Date, Numeric, Monetary, and Boolean. Field-level access controls from ChartHop are documented but cannot be replicated in Crelate's ATS context without admin-level reconfiguration.

ChartHop compensation fields (base compensation, cash compensation, variable pay, equity, total compensation, compensation bands) map to custom Monetary fields on the Crelate Candidate record. We create fields including base_salary__c, variable_pay__c, equity__c, and total_compensation__c. Compensation cycle data (merit increase dates, comp review status) migrates as date and text custom fields. Crelate does not have a compensation management module; this data lives as profile metadata on each Candidate.

ChartHop Performance Review cycles, review forms, and submitted responses have no equivalent in Crelate's ATS schema. We export review metadata (cycle name, review period, participation status) and attach anonymized aggregate results as documents linked to the relevant Candidate. Individual review responses with narrative text are exported as PDF documents stored against the candidate profile. Review templates with custom question types cannot be migrated and are listed in the automation inventory for manual rebuild if needed.

ChartHop Goals (company, team, and individual objectives with progress tracking) do not map to any Crelate object. Goals and their hierarchies are exported as a structured JSON document and as a PDF summary per employee, attached to the corresponding Crelate Candidate record. Cascading goal dependencies are preserved in the document metadata. Goal rebuild options at the destination are documented separately for the customer's HR admin.

ChartHop engagement survey responses and aggregate results require careful handling. For de-identified surveys, response data is exported and stored as an anonymized aggregate document attached to the company's Crelate workspace. For anonymous surveys, individual responses cannot be attributed to any person and are not migrated. Survey metadata (question text, participation rate, benchmark comparison) is preserved in a summary document. Crelate has no engagement survey module; the survey data is migrated as a reference archive.

ChartHop PTO balances and accrual policies migrate as custom fields on the Candidate record (pto_balance__c, accrual_rate__c, pto_policy__c). Historical accrual logs are exported as a separate data pass and stored as a document attached to the candidate record. Crelate does not have a native time-off management module; balances are stored as profile metadata rather than as a transactional leave request system.

ChartHop file attachments per employee profile migrate as Crelate attachments on the corresponding Candidate record. Files must be under 100MB each per ChartHop's limit; we flag any file exceeding this threshold during pre-migration validation and the customer decides whether to split it or store a reference link. Document type categorization from ChartHop (miscellaneous, field-linked) is preserved as a tag on the Crelate attachment. All files are exported from ChartHop's file export mechanism before the migration pipeline begins.

ChartHop Headcount Planning Scenarios (create, update, terminate, promotion, budget, and custom scenario types) are sandboxed planning objects that do not represent live organizational data. ChartHop does not expose these via public API, and the scenario data is tightly coupled to the planning workflow engine. We flag active scenarios during scoping, export them as read-only reference documents before cutover, and deliver them to the customer for manual re-creation in any headcount planning tool they adopt post-migration.

The ChartHop org chart is a rendered visualization of People, Jobs, and reporting relationships. We export the underlying data (people, managers, department hierarchy, matrix assignments) as a structured JSON file and a visual PDF snapshot. Crelate does not render org charts; the hierarchy data is preserved as reference metadata in the exported files. If the customer requires a live org chart in Crelate, they configure a third-party org chart integration post-migration.