Migrate from ChartHop to BambooHR

ChartHop People records map directly to BambooHR Employee records. Standard fields including name, email, phone, address, date of hire, employment status, and work location migrate 1:1. Custom fields on the ChartHop profile migrate as BambooHR custom fields, which support text, number, date, and picklist types. ChartHop's 16-field-type flexibility (calculated fields, multiple choice, yes/no) may require type reduction; calculated fields that reference live ChartHop data cannot reproduce in BambooHR and are documented as read-only reference values.

ChartHop Job records (title, department, level, compensation band) map to BambooHR Employment History entries and custom fields. BambooHR stores job title as a single text field on the Employee record; the full job history is reconstructed via the Employment History table. Compensation band information from ChartHop Jobs migrates to custom fields on the Employee record. Job status (active, closed, on-hold) does not map to a BambooHR native field and is stored as a custom field.

ChartHop department hierarchy maps to BambooHR Departments with the parent-child relationship preserved. BambooHR Department records have name, location, and parent department fields. We reconstruct the full department tree as a flat list of Department records with Parent Department set per the ChartHop hierarchy. Matrix team affiliations stored at the department level in ChartHop are flagged as non-migratable because BambooHR does not model cross-functional team structures.

ChartHop's org chart is a rendered view of People and Jobs with reporting lines. We export the underlying data (people, jobs, managers) and reconstruct the reporting hierarchy in BambooHR. BambooHR generates a read-only org chart from the manager relationships on Employee records. Matrix reporting relationships (employees with multiple managers) cannot be represented in BambooHR's org chart; we document these as reference records in the migration deliverable.

ChartHop's compensation fields (base compensation, cash compensation, variable pay, equity, total compensation) organized into built-in categories map to BambooHR Pay entries. Each BambooHR Pay entry captures pay rate, pay frequency, and effective date. Multiple compensation components (base, bonus, equity) require separate Pay entries or custom fields. Historical compensation changes from ChartHop migrate as individual Pay history entries with correct effective dates.

ChartHop custom fields organized into user-defined categories migrate to BambooHR custom fields. We audit for duplicate or near-duplicate field names (e.g., 'Comp Band' vs 'Compensation Band') and surface them for customer review before mapping. BambooHR supports fewer data types than ChartHop; calculated fields and formula-based fields cannot reproduce and are migrated as static read-only values. Field-level access controls from ChartHop do not map to BambooHR's permission model and are documented separately.

ChartHop PTO balances, accrual policies, and time-off requests map to BambooHR Time Off entries. Current balances migrate as of the migration snapshot date. Historical accrual logs migrate as separate time-off entries with zero balance and a note referencing the historical record. BambooHR's unlimited custom time-off policies map directly from ChartHop's time-off policy configuration.

ChartHop review cycles, review forms, and submitted responses migrate to BambooHR Performance Reviews. Review templates with custom question types, branching logic, or weighted scoring may require simplification. We export review records and responses; review status (draft, submitted, acknowledged) maps to BambooHR review status. Review metadata including template structure is documented for manual rebuild if the destination template diverges significantly.

ChartHop Goals (company, team, and individual objectives with progress tracking) map to BambooHR Goals on Pro and above tiers. Goal hierarchies and parent-child linkages migrate as parent goal references. Cascading goal dependencies that rely on ChartHop's live-connection to people data may require manual re-linkage. Goals on BambooHR Core tier are not available and are documented as requiring manual rebuild or a tier upgrade.

ChartHop file uploads per employee profile migrate to BambooHR Employee Documents. We export files via ChartHop's file export mechanism and re-upload to BambooHR under the corresponding Employee record. All files must be under 100MB per ChartHop's limit and under BambooHR's file size constraints. File categorization (miscellaneous or field-linked) is preserved in the BambooHR document type field.

ChartHop headcount planning scenarios (create, update, terminate/backfill, promotion, budget, custom types) are sandbox planning objects exposed exclusively inside ChartHop's planning workflow engine and are not accessible via public API. BambooHR does not have a headcount planning or scenario modeling module at any tier. We flag all active scenarios during migration scoping, export them as reference documents, and deliver them to the customer for manual re-creation in their preferred planning tool or spreadsheet.

ChartHop Matrix Teams model cross-functional collaboration where employees report to multiple leaders. BambooHR does not support multi-manager relationships or cross-functional team assignments natively. We export the matrix assignment data as a reference CSV alongside the migration so the customer has an audit record. Matrix team filtering and reporting must be handled via BambooHR custom fields or an external tool post-migration.