Migrate from Workable Zone - HRM to BambooHR

Workable Candidate records map to BambooHR Employee records. The native Workable-to-BambooHR integration transfers hired candidates automatically, but for migration we extract all candidates (hired and prospect) via the bulk API, enrich each record with resume binary and attachment URLs, and import via BambooHR's employee bulk import endpoint. We preserve the candidate's application source, pipeline stage history, and scorecard evaluations as custom fields on the resulting Employee record since BambooHR does not natively store ATS pipeline data on employee profiles.

Workable HR module employee records map directly to BambooHR Employee records. Standard fields (name, email, phone, address, start date, job title, manager) migrate 1:1. Custom fields on the Workable employee profile (skills, payroll details, performance flags) map to BambooHR custom employee fields if the destination schema is pre-configured with matching field types. We flag any Workable custom fields that have no BambooHR equivalent and escalate to the customer's admin for schema extension before migration.

Workable active job postings map to BambooHR Job Openings in the ATS module. Each BambooHR Job Opening receives the job title, location, department assignment, and employment status from the Workable job record. We resolve the department hierarchy during this mapping: Workable's top-level department maps to BambooHR Department, and Workable's sub-department maps to a BambooHR custom field (e.g., subdivision__c) if the customer requires that level of hierarchy in reporting.

Workable pipeline stages (Applied, Phone Screen, Interview, Offer, Hired, Rejected) map to BambooHR application stages. We extract the customer's custom stage names and order from Workable's pipeline configuration and configure BambooHR's ATS stages to match. Any stage that has no BambooHR equivalent is mapped to the nearest available stage and flagged in the reconciliation report.

Workable interview scorecards and evaluator feedback are stored as structured fields on the candidate record. BambooHR does not have a native scorecard object. We extract scorecard data from the Workable bulk export, transform it into a JSON blob stored in a BambooHR long-text custom field on the Employee record, and deliver a separate mapping document showing the original scorecard structure for the customer's admin to review or rebuild as a BambooHR form if desired.

Workable offer letters store compensation details as text fields and the signed PDF as a binary attachment. The salary amount, frequency, and currency migrate to BambooHR Employee fields (pay rate or compensation fields). The signed offer letter PDF migrates as a BambooHR Employee document attached to the new hire record, stored in the Signed Documents folder. Workable's integration note: offers export to BambooHR's Signed Documents folder, which may restrict visibility to the employee and HR admin depending on BambooHR's folder permissions configuration.

Workable supports custom text, number, date, dropdown, and boolean fields on candidates, employees, and jobs. We map these field-by-field to BambooHR custom fields of equivalent type. Workable's field export for custom fields requires Premier or Enterprise plan access to the bulk API; Standard-plan customers cannot export custom fields programmatically. We audit the customer's Workable plan tier during scoping and flag any Standard-plan custom field data that requires manual CSV extraction or plan upgrade before migration begins.

Workable HR module time-off balance records map to BambooHR time-off entries. We extract the current balance for each leave type (vacation, sick, personal) per employee and create corresponding BambooHR time-off entries with the correct leave type and balance amount. We do not reconcile balances against a payroll export; the migration delivers balance records as a point-in-time snapshot. Annual carryover and accrual policy configuration is a BambooHR admin task post-migration.

Workable stores candidate resumes and offer letter PDFs as binary attachments. The standard Workable Candidate Details CSV export intentionally excludes these files. We use the Workable bulk API export endpoint to extract resume binaries and attachments for every candidate record, then upload them to the corresponding BambooHR Employee file attachments. File naming convention follows: {candidate_id}_{original_filename} to preserve traceability. Attachments without a valid candidate match (orphaned files) are held in a quarantine folder for admin review.

Workable training records and development progress data stored on employee profiles map to BambooHR custom fields (training status, certification expiry, skills matrix) if the customer requires this data. BambooHR's Training & Skills module is a separate product tier in some configurations; we verify availability during scoping and map accordingly. If BambooHR Training is not available in the customer's plan, we flag training records for manual handoff.