Migrate from Jobtoolz to BambooHR

Jobtoolz Candidate records export to CSV via the built-in Candidates list export. We map Candidate fields (first name, last name, email, phone, location, source, current stage) to BambooHR's Employee data model in the Hiring module. Custom candidate fields migrate as BambooHR Custom Candidate Fields, preserving all values and flagging any type mismatches (e.g. free-text in Jobtoolz that maps to a picklist in BambooHR). Personal email is required on every record before import because BambooHR uses it as the dedupe key.

Jobtoolz Application records link a Candidate to a Vacancy and store the stage history. In BambooHR's Hiring module, the Candidate record carries the stage status directly. We map Application stage history into BambooHR's Candidate stage field and append any stage-change timestamps as a custom text field capturing the progression. Note that BambooHR's Hiring module uses a fixed stage sequence (Applied, Phone Screen, Interview, Offer, Hired, Rejected) that may require collapsing or renaming Jobtoolz's custom stages.

Jobtoolz Vacancy records (title, department, location, employment type, job description, status) map to BambooHR Job postings. We extract the structured vacancy fields and populate BambooHR's Job object, including the job description as rich text, location, employment status, and department. Vacancy custom fields migrate as BambooHR Custom Candidate Fields that appear on applications submitted against the job.

Jobtoolz allows arbitrary pipeline stage names and ordering — the schema is entirely tenant-specific. BambooHR uses a fixed stage sequence (Applied, Phone Screen, Interview, Offer, Hired, Rejected). We capture the complete custom stage sequence during scoping, generate a customer-approved stage mapping table, and collapse any stages that exceed the target model into the nearest BambooHR equivalent. Stage probability percentages migrate if the customer has configured them in Jobtoolz.

Jobtoolz custom fields on Candidate records export as additional columns in the CSV. We recreate each custom field in BambooHR as a Custom Candidate Field, preserving the field label, type (text, number, date, picklist), and all stored values. Any picklist fields in Jobtoolz are recreated as picklist fields in BambooHR to avoid type-mismatch rejections during import.

Jobtoolz supports custom fields on Vacancy records that capture structured data per job posting. We migrate these as BambooHR Custom Candidate Fields that appear on applications submitted against the migrated job, ensuring that any structured job-level metadata (e.g. budget range, hiring manager, clearance level) travels with the job into BambooHR.

Resume, cover letter, and portfolio attachments stored against Jobtoolz Candidate records are downloaded via the authenticated session and re-attached to the corresponding BambooHR Candidate record. We maintain the original file name and file type. Large attachments over 10 MB are flagged for manual review if BambooHR's file size limits apply at the destination tier.

Jobtoolz career site content, company branding assets, and job ad templates are managed via the Jobtoolz Content API with full Bearer token authentication. We extract these as structured content bundles — company description, culture text, logo assets, careers page copy — and deliver them as a content migration package. BambooHR does not host a branded careers site natively; the content package is designed for import into BambooHR's careers page builder or for use with a third-party careers page tool.

Jobtoolz team member accounts and their role assignments (Recruiter, Hiring Manager, Admin) map to BambooHR user accounts. We resolve each Jobtoolz user by email against the BambooHR destination and assign default BambooHR roles (Employee, Manager, or Super Admin) based on the source role. Permission structures differ between platforms; we assign the nearest equivalent role and flag any accounts requiring custom permission set configuration in BambooHR after migration.

Jobtoolz tracks candidate source (referral, job board, direct application, agency) as a Candidate property. We map this to BambooHR's Candidate Source field on the Employee record in the Hiring module. If Jobtoolz uses custom source labels not present in BambooHR's standard source list, we create custom source options in BambooHR's settings before import.