Migrate from ChartHop to Bullhorn ATS & CRM

ChartHop People records map to Bullhorn Candidate. All standard profile fields (firstName, lastName, email, phone with country code, jobTitle, startDate, employmentType) map directly. Custom fields migrate into Bullhorn custom fields on the Candidate entity. Active candidates in Bullhorn are distinguished from inactive by the candidate's employmentStatus mapped to the Candidate isDeleted flag. We resolve manager relationships during migration by cross-referencing manager email against the Bullhorn User table.

ChartHop unlimited custom fields on People must map into Bullhorn's Candidate entity custom fields. Bullhorn ATS Growth edition has no Candidate custom fields; Bullhorn ATS has 2 Custom Objects; Front Office Growth and Enterprise editions support up to 10 Custom Objects with 55 fields each. We audit every ChartHop custom field during scoping, deduplicate near-duplicates (e.g., 'Comp Band' vs 'Compensation Band'), and generate a Custom Object Setup Sheet for Bullhorn Support to create before migration. Custom field types (text, date, multiple choice, yes/no) map to equivalent Bullhorn field edit types.

ChartHop Job records — title, department, employmentType, compensationBand, jobLevel — map to Bullhorn JobOrder. jobTitle in ChartHop becomes title in Bullhorn JobOrder. The ChartHop Job status (active, closed, on-hold) maps to JobOrder status (Open, Closed, Canceled). compensationBand data from ChartHop migrates to JobOrder custom fields; Bullhorn's standard JobOrder does not have a native compensation band structure. jobLevel maps to a Bullhorn custom field if the customer requires level classification at the JobOrder level.

ChartHop Department records represent internal organizational units. Bullhorn does not have a native internal-department object. We map ChartHop Departments to Bullhorn CorporateDepartment if the customer's Bullhorn edition includes this object, or to a custom field on JobOrder (department__c) and Candidate (primaryDepartment__c) for filtering and reporting. The department tree's parent-child hierarchy is preserved as a custom text field (departmentPath__c) since Bullhorn's CorporateDepartment does not natively support recursive parent-child trees.

ChartHop's manager field on each Person record stores a reference to another Person record. We resolve this at migration time by extracting the manager's email from ChartHop and matching it against Bullhorn User records. If the manager is not a Bullhorn User, we assign the record to the nearest available Bullhorn User and flag the orphan for admin review. Bullhorn does not have a native reporting-structure object, so manager relationships are stored as a custom lookup field on the Candidate record pointing to the Bullhorn User who is the hiring manager.

ChartHop Matrix Teams model cross-functional reporting where one employee has multiple managers. Bullhorn has no native multi-manager structure. We export matrix assignments (person email, team name, role, primary manager, secondary manager) and load them into a Bullhorn Custom Object. The custom object links to Bullhorn Candidate records via a custom lookup field. Access controls on the custom object restrict visibility to relevant departments. Bullhorn Support must create this Custom Object before migration; the setup sheet is included in the pre-migration handoff package.

ChartHop compensation fields (baseCompensation, cashCompensation, variableCompensation, equityCompensation, totalCompensation, payFrequency) map to Bullhorn Candidate custom fields or a Custom Object linked to Candidate. We determine the target based on the customer's Bullhorn edition and Custom Object budget. Compensation band data from ChartHop's Compensation module migrates as a separate export pass with company, bandMin, bandMid, bandMax, and jobLevel fields loaded into a compensation-bands Custom Object if available. Historical compensation cycles are not migrated as structured records unless a Custom Object is allocated for them.

ChartHop PTO balances (current balance, accrual rate, policy type) are exported as a snapshot. Bullhorn has no native PTO tracking object. The migration maps current PTO balances to Bullhorn Candidate custom fields (ptoBalance__c, ptoAccrualRate__c, ptoPolicyType__c) if the customer does not license Bullhorn Time & Expense. Historical accrual logs require a separate export pass and are delivered as a CSV reference document for the customer's HR admin to reconcile against their payroll system. PTO data does not map into Bullhorn's standard ATS or CRM objects.

ChartHop Performance review cycles, review forms, and submitted responses are exported as structured records. Bullhorn has no native performance review object. We map completed review data (reviewer name, reviewee email, reviewPeriod, overallRating, responseText) into a Bullhorn Custom Object linked to the Candidate record, provided the Bullhorn edition supports Custom Objects. Review templates with custom question types require manual re-creation in Bullhorn Forms or as Bullhorn custom fields. We deliver a written inventory of each review cycle with its field mapping so the customer's admin can confirm completeness before migration.

ChartHop Goals store company, team, and individual objectives with progress values linked to live people data. Bullhorn has no native goal-tracking object. We export goal hierarchies (goalName, goalType, ownerEmail, parentGoal, progressPercent, status) and load them into a Bullhorn Custom Object linked to the relevant Candidate record via a lookup. Cascading goal dependencies are preserved as a text field listing the parent goal ID since Bullhorn Custom Objects do not support native parent-child relationship fields without Salesforce Object creation. Goal rebuild in Bullhorn depends on whether the customer licenses Bullhorn Automation (Herefish) for task-based goal tracking.

ChartHop Engagement survey responses and aggregate results are exported with anonymization where required. Bullhorn has no native engagement survey object. Survey metadata (question text, participation rate, benchmark data) is preserved in a Bullhorn Custom Object if the Bullhorn edition supports Custom Objects. Anonymized individual responses migrate as aggregate records to avoid re-identification risk. Survey creation and distribution tools do not migrate; we recommend Bullhorn's native survey capabilities or a third-party integration as the replacement path.

ChartHop file uploads per employee profile (miscellaneous and field-linked files) migrate as Bullhorn ContentDocument records linked to the Candidate via ContentDocumentLink. All files must be under Bullhorn's 100MB limit per document; files exceeding this threshold are flagged and delivered as a separate ZIP archive for manual upload. We preserve the original file name, file type, upload date, and the ChartHop custom field the file is linked to (mapped to a Bullhorn custom field on the Candidate for reference). File access controls from ChartHop do not transfer; Bullhorn document security is managed through Bullhorn's own user-role permissions.

ChartHop's org chart is a rendered view of People, Jobs, and reporting lines. Bullhorn does not render org charts. We export the underlying data — every Person record with their manager reference, department, and job title — as a structured reference document (CSV + JSON) that the customer can use to re-create the org view in a third-party visualization tool or within Bullhorn's reporting structure. Matrix reporting relationships are included in this export and are separately mapped via the Matrix Team Custom Object (see mapping row 6). The visual layout itself does not migrate.

ChartHop headcount planning scenarios — including proposed hires, budget impacts, approval statuses, and scenario types (create, update, terminate/backfill, promotion, budget, custom) — are inaccessible via ChartHop's public API. We flag the existence of active scenarios during pre-migration scoping and export them as reference documents (CSV) for the customer's HR and Finance teams to re-create manually in Bullhorn or a third-party headcount planning tool. Bullhorn does not have a native headcount planning module; customers typically integrate Bullhorn with an HRMS (Workday, BambooHR) or use Bullhorn's Custom Objects to model headcount scenarios post-migration.