Migrate your ChartHop data

The primary employee record in ChartHop includes profile data, compensation fields, reporting relationships, and time-off balances. We map all standard fields 1:1; custom fields require field-level mapping against the destination schema. Sensitive compensation fields may be gated by user access roles.

Jobs represent open or filled positions with title, department, level, and compensation band. We preserve job-to-person associations during migration. Job status (active, closed, on-hold) maps directly to the destination's equivalent status field.

ChartHop organizes employees by department hierarchy. We reconstruct the department tree as a flat list of department records plus parent-child relationships. Matrix team affiliations are handled as secondary assignments separate from the primary reporting structure.

The org chart is a rendered view of People and Jobs with reporting lines. We export the underlying data (people, jobs, managers) rather than the visual layout. Matrix reporting relationships require supplemental mapping since most destination CRMs only support single-manager hierarchies.

ChartHop supports extensive custom fields across multiple data types (text, date, multiple choice, yes/no, calculated). We export field definitions alongside values. Field-level access controls are not migrated; they must be reconfigured at the destination.

Headcount planning scenarios are sandboxed planning objects that model hypothetical changes before approval. ChartHop does not expose these via public API, and the scenario data is tightly coupled to ChartHop's planning workflow engine. We do not migrate scenarios; instead we flag the existence of active scenarios so the customer can re-create them manually or document them as reference.

ChartHop tracks base compensation, cash compensation, variable pay, equity, and total compensation. These fields are organized into built-in categories (Compensation Bands, Base Comp, etc.). We export values as of the migration snapshot date. Historical compensation changes may exist as time-stamped field history that requires a separate export pass.

Performance review cycles, review forms, and submitted responses are stored in ChartHop's Performance module. We export review records and responses; however, review templates with custom question types may require field-level mapping and validation against the destination's performance module schema.

ChartHop's Goals module stores company, team, and individual objectives with progress tracking. Goals are linked to live people data. We export goal hierarchies and progress values; cascading goal dependencies require manual validation at the destination since not all platforms support hierarchical goal trees.

Engagement survey responses and aggregate results are stored in ChartHop. We export anonymized response data where available. Survey metadata (question text, benchmarks, participation rates) is preserved. Individual-level responses are subject to the destination's privacy settings.

ChartHop supports file uploads per employee profile with file type categorization (miscellaneous or field-linked). We export files via ChartHop's file export mechanism. All files must be under 100MB; larger files require chunking. File access controls are not migrated and must be reconfigured at the destination.

ChartHop tracks PTO balances, accrual policies, and time-off requests. We export current balances as of the migration snapshot. Historical accrual logs are available but require a separate export pass. Next-year and multi-year accrual policies need policy-level mapping at the destination.

ChartHop's Matrix Teams feature models cross-functional collaboration where employees report to multiple leaders. This is a non-standard structure in most destination CRMs. We export matrix assignments as a supplemental table linked to the primary People record; the destination must support multi-manager assignments or handle these as a custom relationship object.

Jobvite requisitions sync with ChartHop Jobs. We export job requisition data including status and candidate associations. Internal transfers are not supported in the ChartHop-to-Jobvite sync and must be handled manually. Hiring manager and recruiter accounts must match by email across both systems.