Migrate from Tracker to Crelate

Tracker Candidates map directly to Crelate Person records with a candidate type designation. Standard fields (name, email, phone, address, resume, status) transfer via CSV import. We map the Tracker candidate status to Crelate's status workflow and preserve any source tracking as a tag. Custom fields on candidates enumerate during discovery and map to Crelate custom properties. Resume files extract from Tracker CSV attachments and re-associate to the corresponding Crelate Person record by candidate ID lookup.

Tracker Jobs map 1:1 to Crelate Job records. Fields including title, location, description, status, assigned recruiter, and job type transfer directly. Pipeline stages attached to jobs in Tracker map as configurable stage names in Crelate's job pipeline. We map stage names and candidate-stage associations, but stage-level automation rules do not migrate and are flagged for rebuild.

Tracker Companies function as parent records for candidates and contacts and map to Crelate Organization records. We use name matching and domain normalization for deduplication during import. Organization is created before any Person import so that the lookup relationship is satisfied at the moment of Person insert. Industry, address, and custom company fields transfer as Crelate Organization properties.

Tracker Contacts are distinct from Candidates and represent hiring manager and client-side relationships. They map to Crelate Person records with a contact type designation. We preserve the association to the parent Organization record via Organization name lookup. Email, phone, title, and custom contact fields map directly. Contact notes and activity history transfer to the Crelate Person activity stream.

Tracker Placements record placed candidates with start date, compensation, bill rate, and client reference. We map Placements as the billable event object and preserve the link back to both the Candidate Person record and the Job record. Historical Placements are sequenced before other imports to maintain the billable relationship chain. Placement status (active, completed, terminated) maps to Crelate Placement status.

Tracker Activities represent logged calls, emails, meetings, notes, and task completions as timestamped events linked to candidates and jobs. We map Tracker Activity type to Crelate Activity subtype: calls map as Task with Call subtype, meetings map as Event with attendee links, emails map as Activity with engagement tracking, and notes map as pinned notes on the Person or Organization record. ActivityDate preserves the original timestamp for timeline ordering.

Resume files, cover letters, and uploaded attachments stored against candidate records extract from the Tracker export and re-associate to the corresponding Crelate Person record. We extract document filenames and content, match against the candidate record by ID or email, and upload as Crelate attachments with the correct Person reference. Crelate's Resume Toolbox feature processes imported resumes for parsing.

Tracker custom fields on candidate, job, and company objects enumerate during discovery. We map each to Crelate's equivalent custom property with type matching (text, number, date, picklist, multi-select). Field-level validation rules in Tracker do not transfer and are noted for Crelate configuration post-migration. Custom field dependencies on automation rules are flagged in the automation inventory.

Tracker pipeline stages define candidate progression through a job with configurable stage names and statuses. We map stage names and candidate-stage associations to Crelate's job pipeline stages, preserving the sequence order. Stage-level automation rules do not migrate; they appear in the automation inventory for rebuild. Stage probabilities transfer where available.

Tracker tags on candidates, jobs, and companies map to Crelate tags. Tags used for skill classification, source tracking, and status labeling transfer as Crelate tags with the same label. Multi-select tag fields migrate as multiple individual tags. Tags used for automation routing appear in the automation inventory.

Tracker Owners map to Crelate Users by email match. We resolve every distinct Owner referenced on Candidate, Job, Company, and Placement records. Owners without a matching Crelate User go to a reconciliation queue for the customer's admin to provision before record import resumes. User permissions and roles do not transfer and require Crelate configuration post-migration.

Tracker Automation Playbook sequences (email drip campaigns, SMS triggers, recruiter alerts, status update rules) are stored as platform-native workflow logic and do not export. We do not migrate them. We deliver a written inventory of every active Tracker automation with its trigger conditions, actions, and recommended Crelate workflow equivalent. The customer's admin rebuilds them in Crelate's workflow builder (Business Plus and Enterprise tiers). This is a mandatory disclosure for every Tracker migration.