Migrate your Tracker data

Candidates is the primary record object in TrackerRMS. All plans offer unlimited candidate storage, and the standard field set (name, contact info, resume, status) is well-documented and stable. We perform 1:1 field mapping for standard properties and handle custom candidate properties as mapping work during scoping.

Jobs represent open requisitions with status, location, description, and assigned recruiter. We map Jobs 1:1 in most migrations. Pipeline stages attached to jobs are preserved as a separate object we handle in parallel.

Companies function as parent records for candidates and contacts in TrackerRMS. We map Companies to the destination's Account/Organization object using name matching and domain normalization to deduplicate during import.

Contacts are distinct from Candidates and represent hiring manager and client-side relationships. We map Contacts to the destination's Contact or Person record type and preserve association to the parent Company.

Placements record placed candidates with start date, compensation, and bill rate. We map Placements as the billable event object and preserve the link back to both the Candidate and the Job. Historical placement data is included in full exports.

Activities represent logged calls, emails, notes, and task completions. TrackerRMS stores activity history as timestamped events linked to candidates and jobs. We map activities to the destination's engagement or activity timeline, noting that some automated email activities may not export cleanly.

Pipeline stages define the progression of candidates through a job. TrackerRMS supports configurable stage names and statuses. We map stage names and map candidate-stage associations, but stage-level custom logic (auto-advancement rules, mandatory fields per stage) does not export and requires rebuild at the destination.

Automation workflows built in Tracker's Automation Playbook are not exposed via export. We flag this upfront during scoping: email sequences, trigger-based field updates, and recruiter alerts will not transfer as functional automation rules. Candidates and candidate history transfer; the automation logic must be rebuilt.

Resume files, cover letters, and uploaded attachments are stored against candidate records. We extract documents from the export and re-associate them to the corresponding candidate record at the destination, handling file format normalization where needed.

TrackerRMS allows custom fields on candidate, job, and company objects. We enumerate custom field names and types during discovery, then map each to the destination's equivalent custom property. Field types (dropdown, date, text) are matched to maintain data integrity.