Migrate from TRAFFIT to Zoho Recruit

TRAFFIT Jobs map directly to Zoho Recruit Job Openings. We export the job title, description, status, stage definitions, and assigned users. Zoho Recruit enforces a maximum active job count per edition (1 on Free, 100 on Standard, 250 on Professional, 750 on Enterprise); we verify the destination edition accommodates the migration scope during scoping. Closed jobs migrate as inactive Job Openings to preserve the historical record.

TRAFFIT Candidates map to Zoho Recruit Candidates. Zoho Recruit requires Last Name on every Candidate; TRAFFIT records without a Last Name value receive a placeholder ('Not Provided' or equivalent) during transformation. We apply the active-candidate filter during scoping to exclude soft-deleted records, which otherwise inflate export scope and create ghost records in Zoho Recruit. Email, phone, address, and source attribution migrate directly.

TRAFFIT Applications (the link between a Candidate and a Job) map to the association between a Zoho Recruit Candidate record and a Job Opening via the candidate's application history. We preserve the application date, stage, source, and any application-specific notes. Where a Candidate has applied to multiple Jobs in TRAFFIT, each application creates a separate association record in Zoho Recruit.

TRAFFIT Adverts (job listing objects with publication dates and status) map to Zoho Recruit Job Opening content. The advert body, publication date, board status, and posting URL migrate as Job Opening fields. Where multiple Adverts reference the same Job, we consolidate into a single Job Opening with the primary advert content. Zoho Recruit handles job posting distribution separately via its Jobs on Google Search and social posting features.

TRAFFIT custom fields on Candidates and Jobs map to Zoho Recruit custom fields. We discover field types via the TRAFFIT API during data audit and map to Zoho Recruit equivalent types (Text, Picklist, Multi-select Picklist, Date, Number, Checkbox). Standard Edition limits custom fields to 50 per module; Professional and Enterprise allow 300. If the destination is Standard and custom field count exceeds 50 on any module, we identify overflow fields for customer review. Lookup and formula fields require Professional or above and are flagged during scoping.

TRAFFIT user records (email, name, role, active status) export for migration into Zoho Recruit via CSV. Zoho Recruit requires that importing users do not already have a separate Zoho Recruit account; existing accounts must be closed before user import. Hiring Manager accounts (free-tier in TRAFFIT) map to Zoho Recruit recruiter licenses of the appropriate role level. We verify license count against the destination edition during scoping.

TRAFFIT tags used for candidate categorization and talent-pool segmentation migrate as Zoho Recruit tags on the Candidate record. Where tags represent a controlled vocabulary used for filtering, we may map them to a picklist custom field instead of free-form tags, depending on the customer's preferred structure. We preserve the original tag names for audit.

Resume files, cover letters, and uploaded attachments associated with TRAFFIT Candidates migrate to Zoho Recruit as Candidate attachments. We export files with their original names and link them to the corresponding Candidate record. Zoho Recruit Standard and above support document attachments; file size limits and storage quotas apply per edition.

TRAFFIT consent records (timestamp, consent type, withdrawal status) migrate to Zoho Recruit as custom fields on the Candidate record (e.g., gdpr_consent_date, gdpr_consent_type). If the GDPR Assistant add-on ran automated anonymization, affected records may have partially redacted consent histories; we document any gaps in the consent timeline before migration sign-off. We check for active anonymization policies during discovery.

TRAFFIT's separate CRM Persons object (contacts outside the recruitment funnel) maps to Zoho Recruit Contacts or Clients depending on the customer's intended use. We export CRM person records including all custom fields. If Zoho Recruit is also being used for client relationship management alongside recruitment, CRM Persons map to the Client module; if only ATS functionality is in scope, they map to Contacts.

TRAFFIT tracks application origin (job board, referral, direct, etc.) as a source label on each application. We export source labels and map them to Zoho Recruit's Candidate Source picklist values. Custom TRAFFIT source types require creation of corresponding picklist values in Zoho Recruit before migration.

Candidate activity records in TRAFFIT (calls logged, internal notes, stage-change events, interaction history) are stored in an internal event system with no export endpoint via API or XLS. We do not migrate activity timelines. We flag this explicitly during scoping and scope only objects with stable export paths: candidate profiles, applications, jobs, documents, and consent records.