Migrate from Tracker to Bullhorn ATS & CRM

Tracker Candidate records map directly to Bullhorn Candidate. Core fields (name, email, phone, resume text, status) migrate as standard field-to-field mapping. We deduplicate on name, email, and phone before Bullhorn import because Tracker积累了无限记录的惯性导致重复数据，导入 Bullhorn 后会产生额外的用户计费影响. Resume files are extracted from Tracker export as separate document attachments and re-linked to the Bullhorn Candidate record using the candidate's Bullhorn ID resolved at import time.

Tracker Job records map to Bullhorn JobOrder. Job title, description, location, status, and assigned recruiter fields migrate to Bullhorn equivalents. The Job's assigned recruiter resolves to Bullhorn User ID via email match before JobOrder insert. Job status mapping (Open, Closed, On Hold) translates to Bullhorn JobOrder status values. Any custom fields on the Tracker Job enumerate during discovery and map to Bullhorn JobOrder custom fields.

Tracker Company records map to Bullhorn ClientCorporation. The company name and address fields migrate directly, and domain normalization supports deduplication during import. ClientCorporation is created before any Candidate or JobOrder that references it so that the clientCorporationID lookup is satisfied at the moment of insert. We preserve the Tracker Company ID as a custom field tracker_company_id__c for audit trail.

Tracker Contacts (hiring managers and client-side relationships distinct from Candidates) map to Bullhorn ClientContact. Each ClientContact is linked to its parent ClientCorporation via clientCorporationID resolved by company name match. The Tracker contact ID is preserved as tracker_contact_id__c for reconciliation. We flag any Tracker Contacts without a matching Company during deduplication and present a resolution report before committing the import.

Tracker Placements map to Bullhorn Placement as the billable event record. We preserve the start date, end date, compensation, bill rate, and any mark-up or margin fields. The Placement's candidate and job references resolve to Bullhorn Candidate ID and JobOrder ID respectively at migration time, preserving the full back-office chain integrity. Historical placement records are critical for agency billing history and must not lose their Candidate-to-JobOrder linkage during import.

Tracker activity calls migrate to Bullhorn Task with TaskSubtype set to Call. Call disposition, duration, and any notes transfer to Bullhorn custom Task fields. The WhoId on Task points to the migrated Bullhorn Candidate or ClientContact; the WhatId points to the related JobOrder or Placement. ActivityDate preserves the original Tracker timestamp for timeline ordering.

Tracker email activities migrate to Bullhorn EmailMessage records (the email content) linked to an Activity Task record (the timeline entry). The email body and subject migrate directly; attachments migrate as Bullhorn ContentDocument records linked via ContentDocumentLink. WhoId and WhatId on the Task resolve to migrated Bullhorn Candidate or ClientContact and the related JobOrder or Placement respectively.

Tracker meeting activities migrate to Bullhorn Event records. StartDateTime, EndDateTime, and Location migrate directly. Attendee lists from Tracker resolve to Bullhorn EventRelation records linked to the migrated Candidate, ClientContact, and User. Meeting notes migrate to the Event description field or attach as ContentDocument if the Tracker meeting had an associated document.

Tracker Notes linked to Candidates or Jobs migrate to Bullhorn Note records attached via ContentDocumentLink to the parent Candidate, ClientContact, JobOrder, or Placement. Rich text formatting in Tracker notes is preserved in Bullhorn Note body. If the Tracker note references any external attachments, those files are extracted and re-linked to the Bullhorn Note record.

Tracker task activities migrate to Bullhorn Task with Status, Priority, and ActivityDate preserved. Task assignment migrates by resolving the Tracker recruiter ID to Bullhorn User ID via email match. Any Tracker task without a matching User is assigned to a migration-system service account for the customer's Bullhorn admin to reassign post-migration.

Tracker pipeline stage names and candidate-stage associations map to Bullhorn JobOrder status values or a Bullhorn custom picklist field. We enumerate the complete set of Tracker stage names during discovery and configure corresponding Bullhorn JobOrder status values (or a custom field if the stage model is non-standard). Stage-level automation rules in Tracker do not migrate and are included in the automation rebuild inventory.

Tracker custom fields on Candidate, Job, and Company objects enumerate during discovery. Each Tracker custom field name and type (text, number, date, picklist, checkbox) maps to an equivalent Bullhorn custom field on the corresponding Bullhorn entity. Bullhorn entity-level custom field limits apply; if a Tracker object has more custom fields than Bullhorn's per-entity allowance, we identify the overflow and recommend Bullhorn Custom Object for the excess fields.

Resume files, cover letters, and uploaded attachments stored against Tracker Candidate records are extracted from the export and re-associated to the corresponding Bullhorn Candidate record using the Bullhorn ID resolved at import time. Each document becomes a ContentDocument with a ContentDocumentLink pointing to the Candidate. We preserve the original file name and MIME type metadata.

Any commission, bonus, or split-revenue fields stored on Tracker Placements migrate to Bullhorn Placement custom fields. Commission percentage, recruiter split, and manager override fields are preserved as Bullhorn number or currency fields on the Placement object. If Tracker stores commission in a separate related object, we flatten it during the transform phase before Placement insert.