Migrate your TRAFFIT data

Jobs are the core pipeline object in TRAFFIT, holding candidates through stages from application to hire. We export the full job structure including stage definitions and move all active candidates into matching jobs at the destination, preserving stage history.

Candidates are the primary record type. We migrate candidate profiles, contact details, application history, and talent-pool status. Soft-deleted candidates are preserved or excluded based on scoping requirements.

Each application links a candidate to a job with a stage, source, and timestamp. We preserve the full application-to-stage mapping and re-create the association at the destination, handling cases where one candidate has applied to multiple jobs.

Adverts are TRAFFIT's job-listing object. We export advert content, publication dates, and status. Destination platforms may use different listing terminology (Posts, Requisitions), so field mapping is required on a per-destination basis.

TRAFFIT allows custom fields on Candidates, Jobs, and CRM Persons. Custom field types, required flags, and restricted-editing settings must be discovered via the API and mapped to equivalent fields at the destination. Choice-based custom fields require option-value translation.

User records include role, email, and active status. Hiring Manager accounts (free-tier in TRAFFIT) are treated as limited user records. We export all active users for reassignment in the destination ATS, though role hierarchies may not translate 1:1.

Tags are used for candidate categorization and talent-pool segmentation. We preserve tag names and apply them as labels or custom properties at the destination. Where the destination uses a different tagging model, we map tags to the closest equivalent.

Resume files, cover letters, and uploaded documents are attached to candidate profiles. We export files with their associations. File storage formats and attachment limits vary by destination, so document re-upload and storage verification are part of the migration scope.

Activity history (calls logged, notes added, interactions recorded) is tied to TRAFFIT's internal event system and does not have a stable export endpoint. We do not migrate activity timelines as they cannot be reliably reconstructed at the destination.

Consent records track when candidates gave or withdrew permission for data processing. We export consent timestamps and type. Some destination platforms treat consent as a compliance attribute rather than a first-class object, so we map consent to the destination's equivalent compliance field or a custom property.

TRAFFIT maintains a separate CRM Persons object for contacts outside the recruitment funnel. We export CRM person records including custom fields. Not all ATS platforms have a distinct CRM Persons object; in those cases, we merge CRM persons into the candidate or contact object.

TRAFFIT tracks where each application originated (job board, referral, direct). We export source labels and attribution data. Destination platforms may have different source taxonomies, requiring a mapping table at migration time.