Migrate from Business Draft to BambooHR

Business Draft Candidates map to BambooHR Employees, but the path differs based on hiring status. Candidates with a hired Application (Offer accepted, stage = Hired) become BambooHR Employee records with hire date, department, and job title populated from the Application and Offer data. Candidates without a hired Application become BambooHR Applicants in the Hiring module. We resolve the conversion at migration time using Business Draft's stage history. Candidates with partial submissions (dropped applicants) become Applicants with an incomplete application flag rather than Employees. The BambooHR Employee record is the primary object for all post-hire HR operations including onboarding, time-off, and performance.

Business Draft Job postings map to BambooHR Job Openings. The job title, department, and posting status (Open, Closed, Draft) transfer directly. Job posting date and closing date migrate as metadata fields. Job Openings in BambooHR link to Applicants through the Hiring module, and to Employees once an offer is accepted and the applicant converts to an employee record.

Business Draft Applications link a Candidate to a Job and track stage progression (Started Applying, Review, Interview, Offer). Stage history and timestamp for each stage transition migrate as structured data attached to the BambooHR Applicant. Review decisions (approve/reject at each stage) map to the BambooHR Applicant status workflow. The Application-to-Candidate relationship is preserved as a linked record pair so the full hiring journey is visible in BambooHR.

Business Draft configurable Application stages (Started Applying, Review, Interview) map to BambooHR Hiring pipeline stages. We map each Business Draft stage name to an equivalent BambooHR stage and preserve the probability or weighting if configured. Custom stage names (e.g., Technical Screen, Executive Interview) require manual definition in BambooHR's Hiring settings before migration because BambooHR's default pipeline uses a simpler stage set.

Business Draft Offer records (compensation details and acceptance status) map to BambooHR's offer metadata within the Hiring module. Offer documents export as binary files separately and are attached manually post-migration. Acceptance status from Business Draft determines whether the Applicant converts to an Employee record.

Recruiter decisions at the Review stage (approve, reject, move forward) migrate as structured notes on the BambooHR Applicant record. The decision text and reviewer name transfer; the original Business Draft decision timestamp is preserved as a custom field note. BambooHR does not have a native review-decision object, so this maps as an applicant note rather than a typed field.

Business Draft Candidates who began but did not complete an Application migrate to BambooHR Applicants with an incomplete application flag and the original partial submission timestamp. Partial field data (name, email, resume if submitted) transfers; stage progression data is limited to the last completed stage. The customer decides whether to re-engage these candidates in BambooHR or treat them as inactive.

Business Draft video response submissions download as standalone binary files during extraction and are delivered alongside the candidate record CSV. Video files cannot be imported into BambooHR as inline attachments. The customer re-hosts videos on a video platform (Vimeo, YouTube, or internal hosting) and links to them manually from the BambooHR Applicant record if async video evaluation continues as a hiring practice.

Business Draft background check status flags and summaries migrate as notes on the BambooHR Applicant record. The detailed vendor report (PDF from Checkr, HireRight, or similar) does not transfer from Business Draft and must be re-requested from the vendor directly. We flag which candidates require re-initiation of background checks post-migration and provide a list ordered by application date.

Business Draft automated workflow triggers (SMS, email, stage transition reminders) do not have a direct BambooHR equivalent as migratable code. We extract and document every active Business Draft workflow including its trigger conditions, recipient logic, and action sequence. The customer uses this inventory to configure equivalent automations in BambooHR Actions or an iPaaS connector post-migration. Self-scheduling links are ephemeral platform artifacts and are not migratable.