Migrate from Business Draft to Bullhorn ATS & CRM

Business Draft Candidate records map to Bullhorn Contact. We extract all profile fields (name, email, phone, address, skills, work history) and map them to Bullhorn Contact fields. Video response file references are flagged separately for manual re-hosting. The Candidate's source (how they entered the pipeline) maps to Bullhorn's source fields. Background check status and summary migrate to a custom field bg_check_status__c on the Contact record; the full vendor report must be re-requested from the background check provider post-migration.

Business Draft Job postings map directly to Bullhorn Job Order (title, department, description, status, posting date). Each Job's posting status (Active, Paused, Filled, Closed) maps to the Bullhorn Job Order status field. We preserve the original Business Draft Job ID in a custom field bd_job_id__c for reconciliation. Job Order must be created before Candidate Submissions are imported to satisfy Bullhorn's foreign key requirements.

Business Draft Application records (linking a Candidate to a Job with stage progression) map to Bullhorn Candidate Submission. The Business Draft stage history (Started Applying, Review, Interview) migrates as Submission status values and a custom stage_history__c JSON field preserving timestamps. We map Business Draft's stage transition timestamps to Bullhorn Submission date fields for pipeline reporting continuity.

Business Draft Interview Stages within Applications (including self-scheduling link triggers and reminder automation) do not have a direct Bullhorn equivalent because self-scheduling links are ephemeral platform artifacts. We map stage names to Bullhorn Submission status values and recreate interview-related Tasks in Bullhorn. The self-scheduling link generation itself must be reconfigured in Bullhorn using Bullhorn's scheduling integration or a marketplace scheduling tool.

Business Draft Review Decisions attached to Applications at the Review Stage migrate as Notes on the Bullhorn Candidate Submission. The structured decision (Advance, Reject, Hold) and any associated recruiter notes map to a custom picklist field review_decision__c and a Note body. We preserve the decision timestamp as a custom date field for audit purposes.

Business Draft Candidates who began but did not complete an Application migrate to Bullhorn Contact records with a custom boolean field is_dropped_applicant__c set to true and submission_status__c set to Incomplete. Partial submission data (fields completed before abandonment) migrates to the Contact record with remaining fields left null. We include the abandonment timestamp in a custom field bd_abandoned_at__c.

Business Draft video response submissions are exported as standalone binary files (MP4 or platform-specific format) paired with a CSV reference containing the Candidate ID, Application ID, and file path. Bullhorn does not accept inline video attachments via standard import. We deliver the video files and reference CSV to the customer for re-hosting (YouTube, Vimeo, or a DAM system) and manual linking to the Bullhorn Contact record via a custom URL field video_response_url__c.

Background check status and summary attached to Candidates advancing past Interview Stage migrate to a custom field bg_check_status__c on the Bullhorn Contact. The full vendor report PDF remains with the third-party provider and is not migratable. We flag which candidates require re-initiation of background checks post-migration and advise customers to request existing reports from the provider before Business Draft account closure.

Business Draft Offer records linked to Applications (compensation details, acceptance status) migrate to Bullhorn Placement records if the Bullhorn edition includes placement tracking, or to a custom Offer object. Offer metadata (salary, start date, offer status) maps to corresponding Placement fields. Actual offer document attachments export as binary files separately for manual re-upload to Bullhorn.

Business Draft Owner records (recruiters assigned to Candidates, Jobs, and Applications) map to Bullhorn User by email match. We extract all distinct Owner emails and match against the Bullhorn destination User table. Any Business Draft Owner without a matching Bullhorn User goes to a reconciliation queue for the customer's Bullhorn admin to provision before record import resumes.

Business Draft custom field definitions (if present on Candidate, Job, or Application) require discovery during scoping because Business Draft does not publicly document field schemas. We identify custom fields during CSV export analysis and map them to equivalent Bullhorn custom fields on the standard object or to Bullhorn Custom Objects if the data structure warrants a separate entity. Bullhorn's Custom Object limit by edition is confirmed before committing to this mapping path.

Business Draft automated workflow triggers (SMS, email, stage transitions, dropped applicant recovery) do not migrate as code to Bullhorn because Bullhorn uses a different automation model (Bullhorn Automation or native workflow builder). We deliver a written inventory of every active Business Draft workflow with its trigger conditions, actions, and a recommended Bullhorn Automation equivalent. The customer's Bullhorn admin or a Bullhorn partner rebuilds automations post-migration. Self-scheduling link configuration is separately documented for rebuild using Bullhorn's scheduling integration.