Migrate from TRAFFIT to Crelate

TRAFFIT Candidate records map to Crelate Person records. Full name, email, phone, address, and LinkedIn profile URL migrate as standard Person fields. We apply an active-candidate filter during extraction to exclude soft-deleted records; TRAFFIT's soft-delete does not permanently remove candidates and the XLS export may include them unless explicitly filtered. Custom fields on Candidates (such as source-specific attributes or certification flags) map to Crelate custom fields, with type validation performed during the data audit phase to catch any field type changes that occurred mid-use in TRAFFIT.

TRAFFIT Jobs (Recruitments) map to Crelate Jobs. The job title, description, status, and assigned hiring manager migrate directly. TRAFFIT's pipeline stages map to Crelate's job pipeline stages, and we configure the stage probability values during Crelate setup before import. Jobs with confidential status in TRAFFIT map to the confidential flag on Crelate Jobs if the customer's Business Plus plan supports it.

Each TRAFFIT Candidate-to-Job application carries a stage, source attribution, and submission timestamp. We re-create the candidate-to-job association in Crelate as an Application record linked to the Person and Job. The application source label (referral, job board, direct) migrates from TRAFFIT's Application Sources object and maps to Crelate's Candidate Source taxonomy. Where a candidate has applied to multiple jobs, we create one Application record per job to preserve the full pipeline history.

TRAFFIT Adverts (job listing objects with publication dates and status) map to Crelate Job Postings. Advert content migrates as the job posting body text, and publication status maps to the active or closed flag on Crelate. Adverts with past publication dates that are still active in TRAFFIT are set to closed in Crelate unless the customer requests otherwise.

TRAFFIT user records (recruiter seats and free-tier Hiring Managers) map to Crelate Users. We extract active users by email, name, and role. Hiring Managers without a Crelate seat are provisioned as Users with the appropriate Crelate role (Hiring Manager or Recruiter) before candidate import, because OwnerId references on Applications and Jobs must be satisfied at the time of record insert.

TRAFFIT's Talent Pool is a segmented candidate database with member tagging, while Crelate does not have a native Talent Pool object equivalent. We configure Crelate's tagging system to represent Talent Pool membership by migrating each Talent Pool as a named tag and applying it to all members. The customer chooses during scoping whether to consolidate all pools into tags or create a custom candidate field to represent pool membership separately from tags.

TRAFFIT allows custom fields on Candidates, Jobs, and CRM Persons with configurable types and required flags. We export the current field schema via the extended API during scoping, validate field types against actual values (TRAFFIT allows mid-use type changes that can leave values incompatible with the new type), and map each custom field to a Crelate custom field of the equivalent type. Type-mismatch records are flagged for manual review before import.

Resume files, cover letters, and uploaded attachments linked to candidate profiles migrate as Crelate Documents attached to the corresponding Person record via the Resume Toolbox feature. File storage formats and attachment limits in Crelate (increased on Business Plus) are checked during scoping; documents exceeding Crelate's per-plan storage limits are flagged and the customer decides which files to prioritize.

GDPR Consent records in TRAFFIT track consent type, timestamp, and withdrawal status for each candidate. Crelate does not have a dedicated consent object with timestamps and an audit trail. We migrate consent data as a custom compliance attribute on the Person record, mapping consent type to a picklist and consent timestamp to a date field. The customer configures the custom field label during Crelate setup. If the GDPR Assistant add-on has run automated anonymization on any candidate before migration, the affected consent records are partially redacted; we document any gaps in the consent timeline before sign-off.

TRAFFIT maintains a separate CRM Persons object for contacts outside the recruitment funnel (hiring managers, client contacts, referrers). Crelate has no separate CRM Persons object; these records map to the Crelate Company object as client contacts, with the contact name and role stored on the Company record. We flag this as a mapping that changes the data model and note it during scoping so the customer can decide how to handle records that were stored as CRM Persons but have no active job association in TRAFFIT.

TRAFFIT tracks application attribution (referral, LinkedIn, Indeed, direct) as a labeled field on each application. These source labels migrate to Crelate's Candidate Source taxonomy. Where TRAFFIT uses a source label that has no direct Crelate equivalent, we map it to a catch-all 'Other' source and document the mapping in the final deliverable for the customer's admin to review and relabel as needed.

TRAFFIT job stages (pipeline stages from application through hire or rejection) map to Crelate job pipeline stages. We configure the stage sequence in Crelate before import, preserving stage order and assigning probability percentages where the customer uses stage-based forecasting. Stages unique to TRAFFIT (such as confidential stages on sensitive recruitments) are mapped to the nearest equivalent Crelate stage or created as custom stages on the Business Plus plan.