HRMS migration
Field-level mapping, validation, and rollback between Business Draft and Recruit CRM & ATS. We move data and schema; workflows are rebuilt natively in Recruit CRM & ATS.
Business Draft
Source
Recruit CRM & ATS
Destination
Compatibility
9 of 10
objects map 1:1 between Business Draft and Recruit CRM & ATS.
Complexity
BStandard
Timeline
1-2 weeks
Overview
Moving from Business Draft to Recruit CRM is primarily a CSV-to-import migration, not an API-to-API transfer. Business Draft does not publish API documentation or a developer reference in public sources, so we extract all migratable records via in-platform CSV exports and stage them in a working environment for field-level mapping to Recruit CRM. We preserve candidate profile data, application stage history with timestamps, review decisions, and offer metadata. We do not migrate Automated Workflows, self-scheduling links, or background check vendor reports. Video response files download as standalone binary assets for manual re-hosting. We deliver a written inventory of every active Business Draft workflow requiring rebuild in Recruit CRM's automation builder, along with a background check re-initiation checklist for the customer's compliance team. Recruit CRM supports API access at the Business tier ($150/user/month), enabling bulk re-import of complex datasets after field mapping is confirmed.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Business Draft object lands in Recruit CRM & ATS, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Business Draft
Candidate
Recruit CRM & ATS
Contact
1:1Business Draft Candidates map to Recruit CRM Contacts. All profile fields including name, email, phone, LinkedIn URL, skills, and location migrate directly. Video response files attached to candidate profiles download as standalone binary assets and are flagged for manual re-hosting in Recruit CRM's document library or an external host. Any custom candidate fields defined in Business Draft map to Recruit CRM custom fields, which Business tier supports up to 100 of.
Business Draft
Job
Recruit CRM & ATS
Job / Position
1:1Business Draft Job postings map to Recruit CRM Job records. Title, department, location, employment type, job description, and posting status migrate. Active job postings in Business Draft are set to open status in Recruit CRM at migration time. Archived or filled positions migrate with closed status preserved.
Business Draft
Application
Recruit CRM & ATS
Candidate in Pipeline
1:1Business Draft Applications (linking a Candidate to a Job with stage progression) map to Candidate records positioned within a Recruit CRM Job pipeline. Stage names and timestamps (Started Applying, Review, Interview) migrate to Recruit CRM pipeline stages. The full stage progression history with timestamps preserves the candidate journey for audit and reporting. Stage probability percentages are not applicable in Recruit CRM in the same way they are in deal-centric CRMs, so stage data migrates as status history rather than percentage-weighted pipeline metrics.
Business Draft
Review Decision
Recruit CRM & ATS
Candidate Note or Activity
1:1Business Draft Review Decisions attached to Applications at the Review Stage migrate as Notes or Activity entries on the Candidate record in Recruit CRM. The decision type (Advance, Reject, Hold) and any accompanying recruiter notes transfer as structured text. We map these to Notes attached to the candidate rather than a native Decision object, since Recruit CRM does not have a dedicated review-decision object equivalent.
Business Draft
Dropped Applicant
Recruit CRM & ATS
Candidate (Rejected Status)
1:1Business Draft Candidates who began but did not complete an Application (dropped applicants) migrate with their partial submission data preserved. Status is set to Rejected or Dropped in Recruit CRM with the last stage reached and timestamp preserved. Dropped applicant records are migrated because they represent pipeline visibility and may contain valuable sourcing data even for incomplete applications.
Business Draft
Automated Workflow
Recruit CRM & ATS
Automated Sequence (Business tier)
lossyBusiness Draft automated workflow triggers (SMS, email, stage-transition actions, dropped applicant recovery) do not migrate as code. We deliver a written inventory of every active Business Draft workflow specifying its trigger event, conditions, and actions. The customer configures equivalent automated email sequences in Recruit CRM's sequencing tool (available at Business tier) or workflow builder post-migration. This is a manual rebuild step, not an automated import.
Business Draft
Background Check
Recruit CRM & ATS
Background Check (status flag)
1:1Background check status and most-recent summary migrate as a custom field or note on the Candidate record. The full vendor report PDF remains with the background check provider and does not reside in Business Draft's database. We flag which candidates require re-initiation of background checks post-migration and advise customers to request existing reports directly from their vendor before closing the Business Draft account.
Business Draft
Offer
Recruit CRM & ATS
Offer / Placement Record
1:1Business Draft Offer records linked to Applications (compensation details and acceptance status) migrate as structured offer data in Recruit CRM. Offer document attachments export as binary files separately and require manual re-upload to the new system. Acceptance status, compensation amount, start date, and offer notes transfer as structured fields where Recruit CRM supports them.
Business Draft
Self-Scheduling Link
Recruit CRM & ATS
Not migratable
1:1Business Draft self-scheduling links are ephemeral platform artifacts generated dynamically for Interview Stage candidates and expiring after use. These do not migrate as persistent records. After migration, candidates requiring interview scheduling use Recruit CRM's built-in scheduling or calendar integration to generate new links.
Business Draft
Owner (User)
Recruit CRM & ATS
User
1:1Business Draft Owner records (recruiters assigned to Candidates, Jobs, and Applications) map to Recruit CRM User records by email match. Any Business Draft owner without a matching Recruit CRM User is held in a reconciliation queue for the customer's admin to provision before record import completes.
| Business Draft | Recruit CRM & ATS | Compatibility | |
|---|---|---|---|
| Candidate | Contact1:1 | Fully supported | |
| Job | Job / Position1:1 | Fully supported | |
| Application | Candidate in Pipeline1:1 | Fully supported | |
| Review Decision | Candidate Note or Activity1:1 | Fully supported | |
| Dropped Applicant | Candidate (Rejected Status)1:1 | Fully supported | |
| Automated Workflow | Automated Sequence (Business tier)lossy | Fully supported | |
| Background Check | Background Check (status flag)1:1 | Fully supported | |
| Offer | Offer / Placement Record1:1 | Fully supported | |
| Self-Scheduling Link | Not migratable1:1 | Fully supported | |
| Owner (User) | User1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Business Draft gotchas
No publicly documented API endpoint surface
Video response files stored in proprietary format
Background check results are third-party dependent
Recruit CRM & ATS gotchas
API rate limits are license-scaled and can throttle bulk migration
Custom field schemas vary per organization and require field-level mapping
Files and email attachments require separate extraction and re-upload
Email sequences and automation logic do not transfer between platforms
Pair-specific challenges
Migration approach
Discovery and export field coverage confirmation
We audit the Business Draft instance across Candidates, Jobs, Applications, stage configurations, review decisions, offer records, and any custom field definitions. We confirm which fields are available in Business Draft's CSV export against what the customer needs in Recruit CRM. If export coverage is incomplete, we identify manual extraction steps or flag fields that require post-migration re-entry. The discovery output is a written migration scope document listing every migratable object, every non-migratable object, and a timeline estimate.
CSV extraction and staging
We extract all migratable records from Business Draft using their in-platform CSV export tools. Extracted files are staged in a secure working environment where we inventory record counts, identify duplicate candidates across Applications, flag partial submission records (dropped applicants), and assess the overall data quality. Any data hygiene issues (inconsistent date formats, missing required fields for Recruit CRM) are documented and resolved in staging before mapping begins.
Field mapping to Recruit CRM schema
We map every Business Draft export field to its Recruit CRM equivalent. This includes candidate profile fields to Contact fields, Job fields to Position fields, Application stage history to pipeline stage entries, review decisions to Notes or Activity records, and offer metadata to Offer records. Dropped applicants are mapped to Candidate records with Rejected status. We use Recruit CRM's bulk import template (or their API if the Business tier is in use) as the target schema. Custom fields from Business Draft map to Recruit CRM custom fields, with a maximum of 100 supported at Business tier.
Video and background check extraction
We download all video response files from Business Draft as standalone binary assets and export them alongside the candidate CSV. We flag which candidates have video responses in a dedicated column. Background check status flags and summaries export as structured fields; the customer receives a list of candidates requiring background check re-initiation with their vendor contact information. These are held separately from the primary record migration and require manual post-migration action.
Bulk import and reconciliation
We perform bulk import into Recruit CRM using their native import tool or API (Business tier). Record counts are reconciled at each phase: Contacts (Candidates), Jobs (Positions), Applications (pipeline entries), Notes (review decisions), and Offers. Any rejected records due to required-field mismatches or validation errors are corrected and re-imported. The customer's admin validates 25-50 spot-check records against the source Business Draft data before production cutover sign-off.
Cutover, final delta, and workflow inventory handoff
We freeze writes to Business Draft during the cutover window, run a final delta import of any records modified since the initial extraction, and confirm Recruit CRM as the system of record. We deliver the automated workflow inventory document listing every Business Draft workflow requiring rebuild in Recruit CRM, plus the background check re-initiation checklist. We support a three-day hypercare window for reconciliation issues. We do not rebuild workflows in Recruit CRM as part of the migration scope.
Platform deep dives
Business Draft
Source
Strengths
Weaknesses
Recruit CRM & ATS
Destination
Strengths
Weaknesses
Complexity grading
Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Business Draft and Recruit CRM & ATS.
Object compatibility
1 of 7 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
Business Draft: Not publicly documented.
Data volume sensitivity
Business Draft doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Business Draft to Recruit CRM & ATS migration scoping. Not seeing yours? Book a call.
Walk through your Business Draft to Recruit CRM & ATS migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Business Draft
Other ways to arrive at Recruit CRM & ATS
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.
