Migrate from Tracker to BambooHR

Tracker Candidates who have a placed status (linked Placement record with a start date) map to BambooHR Employee records with employment details (hire date, compensation, employment status) enriched from the Placement. Tracker Candidates without a Placement require a disposition decision: if the customer licenses BambooHR ATS Advantage ($129/mo), they migrate as Applicants; otherwise, they are dispositioned as inactive records outside BambooHR's standard HRIS. We run candidate deduplication against name, email, and phone before import and present a duplicate report for admin resolution.

Tracker Placements carry the billable event data: start date, pay rate, bill rate, and the assigned recruiter. We map Placements to BambooHR Employee records by matching the placed Candidate to the corresponding Employee, and we populate BambooHR's hire date, pay rate, and employment status fields from the Placement data. The bill rate does not map to a standard BambooHR field; we store it in a custom field placement_bill_rate__c or flag it for the customer's admin to maintain in a separate compensation record.

Tracker Companies function as parent records for Candidates and Contacts. In BambooHR HRIS, each Employee has a single company assignment (the company field on the Employee record). We map Tracker Company name to BambooHR Employee.company and deduplicate using domain normalization. If the customer manages multiple legal entities or client relationships, we create a custom Organization field to preserve the Tracker Company hierarchy.

Tracker Jobs represent open requisitions with location, description, and assigned recruiter. If the customer licenses BambooHR ATS Advantage, Tracker Jobs map to BambooHR Job postings. Without the ATS add-on, Jobs require disposition: either exported as a written job inventory for manual reposting or migrated to a custom BambooHR Requisition object we create during schema setup. The mapping depends on whether the customer intends to use BambooHR's native hiring flow post-migration.

Tracker Contacts represent hiring managers and client-side relationships distinct from Candidates. Internal employees at the customer's organization who appear as Tracker Contacts map to BambooHR Employee records. External client contacts without an employment relationship in BambooHR are stored as Notes attached to the corresponding Company or Account record, or flagged for the customer's admin to manage as a separate CRM.

Tracker Activity history (calls, emails, meetings, notes) attached to Candidates and Placements migrates to BambooHR as Notes on the corresponding Employee record. We preserve the activity type, timestamp, and content body. BambooHR's employment timeline supports Notes as the primary historical context artifact; we set the Note created date to the original Tracker activity timestamp to preserve the chronological record. Attachments migrate as BambooHR file attachments linked to the Employee.

Tracker custom fields on Candidate, Job, and Company objects enumerate during discovery. We map each to a BambooHR custom Employee field of the matching type (text, number, date, dropdown). Fields with no BambooHR equivalent are flagged in a custom field disposition report for the customer's admin to resolve before import. Multi-select Tracker custom fields map to BambooHR multi-select picklists.

Tracker pipeline stages define candidate progression through a Job. If the customer takes the BambooHR ATS add-on, stages map to BambooHR job application statuses. Without the ATS add-on, pipeline stage data migrates as a custom Candidate field (stage_name__c) that the customer's admin uses for reference, because BambooHR's core HRIS does not enforce a recruiting pipeline structure.

Resume files, cover letters, and uploaded attachments stored against Tracker Candidate records extract from the CSV export and re-associate as BambooHR Employee file attachments. We map the filename to the BambooHR Employee using the candidate-to-employee matching key and preserve the original upload date as the file creation timestamp. PDF resumes migrate with full text intact.

Tracker Automation Playbook sequences (multi-step email drips, SMS triggers, recruiter alerts, status-update automations) do not export as portable artifacts. We do not migrate automation logic. During scoping, we enumerate every active Automation Playbook and deliver a written inventory with trigger, conditions, and recommended BambooHR Workflow equivalent for the customer's admin to rebuild post-migration. This document is the handoff artifact for the automation layer.