Migrate from Tracker to Zoho Recruit

Tracker Candidates map 1:1 to Zoho Recruit Candidates. The primary mapping challenge is Tracker's flexible name fields against Zoho Recruit's mandatory Last Name requirement. We enumerate every Tracker Candidate with a blank last name during discovery and insert a placeholder ('Not Provided', 'Unknown', or similar) before import. Email, phone, resume (as attachment), skills, current employer, current title, and status migrate directly. Tracker candidate custom fields map to Zoho Recruit custom candidate fields created during the import preparation phase.

Tracker Jobs map to Zoho Recruit Job Openings. The mapping covers job title, job status (open/closed/on hold), job type, location, description, assigned recruiter (mapped to Zoho Recruit User by email), department, and salary range fields. Tracker pipeline stages associated with jobs map to Zoho Recruit's candidate status pipeline within each Job Opening rather than as a global stage configuration. We flag any Tracker job with no assigned recruiter for manual assignment during or after migration.

Tracker Companies map to Zoho Recruit Clients. The primary fields (company name, address, phone, website, industry) map directly. Tracker company domain is used as the dedupe key and maps to the Client website field. We normalize domain strings during dedup processing so that 'acme.com' and 'www.acme.com' resolve to the same Client record. Client records import before Candidates so that candidate-to-client associations are satisfied at insert time.

Tracker Contacts (distinct from Candidates; represents client-side hiring managers and client relationships) map to Zoho Recruit Contacts. The mapping covers first name, last name (mandatory in Zoho Recruit), email, phone, title, department, and the linked Client. We use the Contact email as the dedupe key and map the Tracker Contact-Company association to the Zoho Recruit Contact-Client lookup. Any Tracker Contact without an email address requires a placeholder before import.

Tracker Placements (placed candidates with start date, compensation, bill rate, and client reference) have no native Zoho Recruit equivalent object. We create a Zoho Recruit custom module named Placements with fields for start date, end date, compensation, bill rate, billable hours, and links back to the placed Candidate and the originating Job Opening. The custom module is pre-created in Zoho Recruit before migration begins. Customers who prefer to store placement data as notes on the Candidate record can choose that option during scoping; we document both approaches.

Tracker activity history (calls, emails, notes, tasks) maps to Zoho Recruit To-Dos, Notes, and Interviews. Call activities migrate as Zoho To-Dos with call type designation. Email activities migrate as Zoho Notes attached to the corresponding Candidate or Client. Tasks migrate as Zoho To-Dos with due date and status preserved. Each activity links to the Candidate or Client by email or name lookup at migration time. Activities with no resolvable candidate or client reference are held in a separate import batch for manual resolution.

Tracker pipeline stages define candidate progression through a job requisition. Zoho Recruit uses candidate status values within each Job Opening rather than a global pipeline configuration. We map each Tracker stage name to a corresponding Zoho Recruit status value (Applied, Screening, Interview, Offer, Hired, Rejected) and create a candidate status workflow in Zoho Recruit that mirrors the Tracker stage progression. Stage-level automation triggers do not migrate and are documented separately for Zoho Recruit Workflow Rules rebuild.

Tracker resume files and uploaded attachments map to Zoho Recruit Attachments associated with the corresponding Candidate or Client record. We extract documents from the Tracker export, verify the file format (PDF, DOC, DOCX, TXT supported by Zoho Recruit), and re-associate them using the file naming convention in the Tracker export's attachment mapping column. Zoho Recruit's import wizard supports attachment folders in a structured zip file with a Data folder and an Attachments folder; we prepare the zip per Zoho's documented structure.

Tracker custom fields on Candidate, Job, and Company objects map to Zoho Recruit custom fields on the corresponding module. We enumerate all Tracker custom fields during discovery, categorize each by data type (text, number, date, picklist, checkbox), and pre-create matching custom fields in Zoho Recruit before the main import phase. Custom field API names are preserved where possible; Zoho Recruit appends a numeric suffix if the name conflicts with an existing field.

Tracker recruiter users map to Zoho Recruit Users by email match. We extract all Tracker users referenced on Candidate, Job, and Placement records during the discovery phase. If a Tracker user email does not match an existing Zoho Recruit User, we flag it for manual provisioning before the main migration. Zoho Recruit requires at least two Users in the account before importing data; we coordinate this with the customer's admin during setup.

Tracker advertising or sourcing campaigns (if present) map to Zoho Recruit Campaigns. The mapping covers campaign name, type, start and end dates, budget, and associated job openings. Campaigns import before Candidates per Zoho Recruit's documented import sequence so that campaign-candidate associations are preserved at insert time.

Tracker interview records (scheduled interviews linked to a Candidate and Job) map to Zoho Recruit Interviews. The mapping covers interview date and time, interviewer (mapped to Zoho Recruit User), interview type (phone, video, in-person), interview location or video link, and candidate feedback fields. We resolve the Candidate and Job Opening references using email and job title matching at migration time.

Tracker Automation Playbooks (email drip sequences, SMS triggers, recruiter alerts, status update rules) are platform-native workflow logic that does not export. We do not migrate them. We enumerate every active Automation Playbook in Tracker during discovery, document its trigger conditions, actions, and sequence order, and deliver a written inventory with Zoho Recruit Workflow Rules equivalents for your admin to rebuild post-migration. This is a documented handoff, not a functional migration.