Migrate from TRAFFIT to BambooHR

TRAFFIT Jobs (called Recruitments) map to BambooHR Jobs. The TRAFFIT job name, description, department assignment, and hiring manager field transfer directly. TRAFFIT pipeline stages require flattening because BambooHR uses a simpler status model (Applied, Phone Interview, On-site Interview, Offer, Hired, Not Hired). We map each TRAFFIT stage to the closest BambooHR status and flag any stages that cannot be represented for manual resolution. Open and closed job status transfers directly.

TRAFFIT Candidate records map to BambooHR Employees with an associated Job Application. Contact details (name, email, phone, address), resume file, and talent pool tags transfer to the BambooHR employee profile. TRAFFIT's candidate source attribution (referral, job board, direct) maps to BambooHR's Application Source field. Soft-deleted TRAFFIT candidates are excluded by default unless the customer requests inclusion; we verify against TRAFFIT's filtered-active-view during scoping.

Each TRAFFIT application (Candidate-to-Job link with stage, source, and timestamp) maps to a BambooHR Job Application record attached to the corresponding Employee and Job. The application date and current stage status transfer. Historical stage-change timestamps are not preserved because TRAFFIT does not expose stage-history via API or XLS export.

TRAFFIT Adverts (job listing records with publication dates and job-board distribution status) map to BambooHR Job records with publication metadata stored in a custom field group. The advert title, content, and publication date transfer; job-board distribution status maps to a custom multi-select picklist reflecting where the advert was posted.

TRAFFIT custom fields on Candidates, Jobs, and CRM Persons map to BambooHR Employee custom fields or Job custom fields depending on the parent object. Field type mapping requires validation: TRAFFIT text, number, date, and dropdown types map directly; checkbox and multi-select types require BambooHR's equivalent custom field type. We validate TRAFFIT field types against actual values during the data audit phase and flag any type-mismatch records. Field required flags are preserved where BambooHR supports required custom fields.

TRAFFIT tags (used for candidate categorization and talent-pool segmentation) map to BambooHR custom label fields on the Employee record. We create a multi-select picklist or text-area field in BambooHR to hold tag names. The customer chooses between preserving all tags as individual values or consolidating into a talent-pool categorization during scoping.

Resume files, cover letters, and uploaded attachments from TRAFFIT migrate as Employee Files in BambooHR. We export files with their original file names and attach them to the corresponding Employee record. File storage limits in BambooHR vary by plan tier; we verify the destination account's storage allocation during scoping and flag any volume concerns.

TRAFFIT CRM Persons (contacts outside the recruitment funnel) map to BambooHR Employee records if they are internal HR contacts, or to a custom contact management approach if the customer needs external contact storage. BambooHR does not have a distinct CRM Persons object; CRM Person records with custom fields are mapped to Employee records with a custom source field indicating their CRM origin.

TRAFFIT user accounts (recruiters, admins) and free-tier Hiring Manager accounts map to BambooHR Employee records with user access. We export active user email, name, and role. TRAFFIT owner assignments on Candidates and Jobs resolve to the corresponding BambooHR Employee for reassignment in the destination system. Inactive TRAFFIT users are excluded unless the customer requests them as inactive BambooHR employees.

TRAFFIT GDPR consent records (consent type, timestamp, and status) map to BambooHR custom fields on the Employee record. BambooHR does not have a native GDPR consent audit object, so we create custom date fields (consent_given_date, consent_type, consent_withdrawn_date) to preserve the compliance record. If the customer had the GDPR Assistant add-on with active anonymization policies, we verify during discovery whether any candidates were anonymized before migration and document any consent gaps.

TRAFFIT tracks where each application originated (job board, referral, direct, etc.) and this attribution data migrates to BambooHR's Application Source field or a custom source taxonomy field. Source labels are preserved as-is where they match BambooHR's built-in options; non-matching labels are mapped to a closest equivalent or stored as a custom text field.

TRAFFIT candidate activities (calls logged, notes added, stage-change events, internal comments) are stored in TRAFFIT's internal event system and are not exposed via API or XLS export. We do not migrate activity timelines. This is explicitly documented during scoping. If the customer requires activity history, they must export manually from TRAFFIT before the migration window begins and handle it separately as a manual record.