Migrate from TRAFFIT to Recruit CRM & ATS

TRAFFIT Jobs are the core pipeline object holding candidates through customizable stages. We export the full job structure including stage definitions, descriptions, assigned owners, and job status (active, paused, closed). Recruit CRM Jobs accept the same field structure: title, description, requirements, location, salary range, and pipeline stage values. The stage names migrate as-is and are re-applied to Recruit CRM's pipeline kanban view.

TRAFFIT Candidates map directly to Recruit CRM Candidates. We migrate contact details (name, email, phone, LinkedIn URL), application history, talent-pool membership, tag assignments, and custom field values. Soft-deleted candidates are excluded by applying TRAFFIT's filtered-view logic during export to avoid importing ghost records into Recruit CRM. Candidate status (active, archived) is preserved as a Recruit CRM candidate attribute.

TRAFFIT's separate CRM Persons object stores external contacts (clients, hiring managers, referrers) outside the recruitment funnel. Recruit CRM does not have a separate CRM Persons object; all contacts are Candidates. We migrate TRAFFIT CRM Persons as Candidates in Recruit CRM and flag them with a custom type attribute (client_contact or referrer) so that the customer's team can distinguish external contacts from recruitment candidates. Where a CRM Person email matches an existing Candidate (from a prior application), we flag the duplicate for manual resolution rather than merging automatically.

TRAFFIT Adverts are job-listing objects with publication dates, status, and content tied to job board distribution. Recruit CRM uses Job Posts for the same purpose. We export advert titles, full descriptions, publication dates, and status, then re-create them as Recruit CRM Job Posts with the same publication metadata. Multiposting status from TRAFFIT (which is limited and requires paid integrations) migrates to Recruit CRM's job board distribution settings, which support no-code integrations with major job boards at the Business tier.

Each TRAFFIT application links a Candidate to a Job with a stage, source attribution, and application timestamp. Recruit CRM does not have a standalone application object; candidate-to-job associations are implicit in the pipeline view. We re-create the application linkage by assigning each migrated Candidate to the correct Recruit CRM Job and setting the initial pipeline stage to match the TRAFFIT application stage. Source attribution (referral, job board, direct) migrates as a candidate attribute.

TRAFFIT allows custom fields on Candidates, Jobs, and CRM Persons with type, required-flag, and restricted-editing settings. Recruit CRM supports custom fields on Candidates and Jobs. We discover the full TRAFFIT custom field schema via API during scoping, re-create equivalent fields in Recruit CRM with matching types, and validate all values against Recruit CRM's type constraints before import. Custom fields that reference CRM Persons and have no Candidate equivalent are applied to the appropriate candidate record with a flag indicating their original CRM Persons origin.

Active TRAFFIT user accounts (recruiters, admins, hiring managers) migrate as Recruit CRM Users. We resolve by email match. Hiring Manager accounts (free-tier in TRAFFIT) become standard Recruit CRM users; their permission level is set based on the TRAFFIT role designation during scoping. Any TRAFFIT user without an email match is held in a reconciliation queue for the customer to provision before record import begins.

TRAFFIT tags are used for candidate categorization and talent-pool segmentation. We export tag names and talent-pool assignments and apply them as Labels in Recruit CRM. Recruit CRM's label system supports multiple labels per candidate, matching TRAFFIT's multi-tag capability. Talent-pool designations migrate as a dedicated candidate attribute so that agencies can preserve their talent-pool segmentation strategy.

TRAFFIT consent records track candidate permission for data processing with timestamps and consent type. We export consent timestamps and types as candidate attributes in Recruit CRM. We check during discovery whether the GDPR Assistant add-on is active and whether any anonymization policies have run; if candidates have already been anonymized, consent records for those candidates are documented as partial or redacted and flagged for the customer's compliance review before import. Recruit CRM's GDPR compliance tools activate post-migration for ongoing consent management.

TRAFFIT tracks where each application originated (job board, referral, direct, sourcing integration). We export source labels and preserve them as candidate attributes in Recruit CRM. Where TRAFFIT source labels do not map directly to Recruit CRM's built-in source taxonomy, we use a custom source field to retain the original attribution data. Source data is valuable for post-migration reporting on candidate acquisition channels.

Resume files, cover letters, and uploaded attachments linked to candidate profiles in TRAFFIT are exported with their file associations and re-uploaded to Recruit CRM as candidate documents. File storage formats (PDF, DOCX, RTF) are preserved. Recruit CRM's document attachment limits apply at the Business tier; we verify file sizes against destination limits during the data audit phase and flag any oversized attachments for the customer to compress or host externally with a reference link stored in Recruit CRM.