Migrate from Business Draft to Crelate

Business Draft Candidate records map to Crelate Contact as the primary person record. The Candidate's name fields, email, phone, address, and profile data migrate to Crelate Contact with the same field values. We resolve Crelate's lookup rules where an AdditionalContact field requires an _Id, FirstName, and LastName structure—if the _Id is blank and name fields are present, Crelate creates a new Contact. We apply this rule during bulk import by batching new Contact creation before any records that reference them.

Business Draft video response files are downloaded as standalone binary assets during extraction and exported separately from the candidate CSV. Crelate does not accept inline video attachments via standard import, so we deliver video files with a mapping spreadsheet linking each file to the corresponding Crelate Contact record by email or ID. The customer's admin must re-host the videos (on their own hosting or a platform like Vimeo) and add a link or note to the Contact record manually. We include the re-hosting instructions in the delivery package.

Business Draft Job postings map to Crelate Job. We extract Job title, department, location, status (Open/Closed), and posting date from the Business Draft export and insert them into Crelate Job records via the REST API. The Name field is required per Crelate's API; we map Business Draft's job title directly to Crelate Job Name.

Business Draft Application records link a Candidate to a Job and track stage progression through the hiring pipeline. We map the Application to a Crelate Job Order entry, preserving the stage name and any timestamps associated with the last stage transition. We resolve the Contact reference (Candidate) and Job reference (Job) by matching email to Crelate Contact Name/email and Job Name before inserting Application records.

Business Draft Interview Stages are defined within Applications with automated scheduling link triggers. Crelate uses a pipeline-and-stage model on Job Orders. We map Business Draft stage names (e.g., Started Applying, Review, Interview) to the nearest Crelate stage equivalents in the customer's configured pipeline, documenting any stage that does not have a direct Crelate equivalent as a candidate for a custom stage.

Business Draft Review Decisions are structured decisions attached to Applications at the Review Stage. Crelate does not have a dedicated Review Decision object. We map review decisions to Crelate Notes attached to the Job Order, or to Tags on the Job Order if the customer has configured a review status Tag set. We preserve the decision value and the timestamp of the decision.

Business Draft Dropped Applicants are Candidates who began but did not complete an Application. We extract partial submission data and create Crelate Contact records with available profile fields and a Tag indicating 'Dropped Applicant' and the associated Job. We note which fields are missing so the customer's admin can set expectations for incomplete record coverage.

Business Draft Offer records attached to Applications include compensation details and acceptance status. Crelate Job Orders do not have a native Offer sub-object. We map offer metadata (offered salary, start date, status) to Crelate Notes on the Job Order, or to custom fields on the Job Order if the customer has configured compensation fields during Crelate setup.

Business Draft background check status and summary attach to Candidate records advancing past Interview Stage. The full vendor report remains with the background check provider and is not stored in Business Draft. We map the most recent status and summary to a Crelate Note on the Contact record, and we flag which Candidates require re-initiation of background checks post-migration, advising the customer to request existing reports from the provider before Business Draft account closure.

Business Draft automated workflows (SMS, email triggers on stage transitions and dropped applicants) have no direct Crelate equivalent that migrates as code. We deliver a written inventory of every Business Draft workflow listing its trigger, conditions, and actions. Crelate Automation and Sequencing are available at the Business Plus tier and require rebuild by the customer's admin post-migration. We document the recommended Crelate automation configuration for each migrated workflow.

Business Draft self-scheduling links are dynamically generated for Interview Stage candidates and expire after use. They are ephemeral platform artifacts and are not migratable as persistent records. We do not attempt to migrate these links. The customer's admin recreates scheduling links in Crelate or through a connected scheduling tool post-migration.

Business Draft custom field definitions on Candidates, Jobs, and Applications require manual re-creation in Crelate. Crelate's custom fields support Short/Long Answer, Picklist (single and multi-choice), Monetary, Date, and Star Rating types. We audit Business Draft custom fields during discovery, produce a Crelate custom field creation checklist with field types and options, and the customer's admin creates the fields in Crelate before we run the final migration import so that data populates into the correct fields rather than being dropped.