Migrate from Teamdoor to BambooHR

Teamdoor candidate records map to BambooHR employee profiles. The candidate's name, email, phone, and address fields map directly. Employment status (active, inactive, hired) determines the BambooHR hire date field; rejected candidates are stored as inactive employees for talent-pool continuity.

Teamdoor's per-job pipeline stages (Applied, Screening, Interview, Offer, Hired, Rejected) are mapped to BambooHR Hiring pipeline stage values. Each job in Teamdoor maps to one BambooHR Job record; the pipeline stage values are configured in BambooHR Hiring before migration so the pick-list aligns.

Teamdoor job postings map directly to BambooHR Job Opening records. Title, description, department, and location fields map field-by-field. Teamdoor's multi-language job descriptions are concatenated into the BambooHR description field with language labels preserved.

Teamdoor talent pool entries contain source, rating, skill tags, and recruiter notes. Since BambooHR has no native talent-pool object, we create a custom field (Talent_Pool_Source__c) and a custom text field (Talent_Pool_Skills__c) on the employee record to preserve source attribution and skill tags for future hiring campaigns.

Teamdoor recruiter notes and evaluation comments on a candidate record map to BambooHR Employee Notes. The note body, author, and original timestamp are preserved. Notes from rejected candidates are attached to the corresponding inactive employee record for talent-pool reference.

Resume and cover-letter files attached to a Teamdoor candidate record are downloaded and re-uploaded to the corresponding BambooHR employee Files section. PDF and DOCX formats are supported; file size limit is 25MB per file per BambooHR storage constraints.

Teamdoor interview ratings stored as numeric or star-score fields on the candidate record migrate to a BambooHR custom number field (Interview_Rating__c) on the employee record. Where Teamdoor stores structured evaluation rubrics, the raw score is preserved as a text custom field for manual review.

Teamdoor tracks the source channel for each candidate (LinkedIn, 104, Indeed, referral, etc.) as a candidate property. This maps to a BambooHR custom text field (Recruitment_Channel__c) on the employee record, preserving attribution data for ROI reporting.

Teamdoor department assignment on a job posting or candidate record maps directly to BambooHR Employee Department. The department list is pre-created in BambooHR during schema setup; unmapped departments are flagged for admin resolution before the migration runs.

Teamdoor Pro/Enterprise custom fields on candidate records are discovered via the API and mapped to BambooHR custom fields. Field type translation: pick-list values become BambooHR dropdown custom fields, numeric values become number fields, and free-text fields become text custom fields. Custom field creation in BambooHR is done before migration so the field IDs are available for mapping.

Teamdoor workflow rules for stage transitions, email triggers, and AI scheduling do not migrate. These must be rebuilt in BambooHR using BambooHR's workflow and approval tools or the BambooHR open API. We export the rule definitions as a JSON reference file for your BambooHR admin to use as a rebuild specification.

Offer letters generated within Teamdoor and attached to the candidate record are treated as candidate attachments. They download and re-upload to the BambooHR employee Files section under the Documents tab. The offer letter is linked to the employee record even if the candidate has not yet transitioned to a hired status.