Workable to BambooHR migration
We migrate Candidates, Employees, Jobs, Offers, and Time-Off records from Workable into BambooHR with the full pipeline history preserved, resume attachments re-associated, and Workable's 10-req-per-10-second API constraint handled through batched export sequencing.
FlitStack AI migrates applicants, job openings, employees, note or custom fields and custom fields on applicants from Workable to BambooHR, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

What moves from Workable to BambooHR?
Moving from Workable to BambooHR is a migration from a recruiting-first platform with an HRIS layer toward an HRIS-first platform with an ATS module.
Read the full summary
Workable organizes hiring around Candidates, Jobs, Pipeline Stages, Interviews, Scorecards, and Offers; BambooHR centers on Employees, Departments, Time-Off, and Benefits with an applicant tracking system built on top. The migration requires sequencing Candidates before Employee records (since BambooHR links new hires to existing employee profiles), resolving the scorecard-to-evaluation field mapping, and extracting resume attachments separately from the Workable API. Workable's native BambooHR integration only activates at the Hired stage, so full pipeline history and interview data require a custom migration approach. We do not migrate Workflows, automated actions, or stage-based triggers as code; we deliver a written inventory for the customer's admin to rebuild in BambooHR.
Candidate → Applicant
Workable Candidates map to BambooHR Applicants.
How it maps
The BambooHR Applicant record stores name, email, phone, job applying for, stage, source, and resume. We map communication history (notes and comments) to BambooHR's notes section and preserve the original Workable candidate ID in a custom field workable_candidate_id__c for audit and cross-reference. Pipeline stage names map to BambooHR's applicant stage values, which are configurable per job in BambooHR.
Job → Job Opening
Workable Jobs map to BambooHR Job Openings.
How it maps
Job title, department, location, status (open/closed/on hold), and description carry over. Workable's maximum active-job-slot limit per pricing tier does not apply in BambooHR, which sets limits by plan (5 on Pro, 25 on Elite, 50 on Elite with add-ons). We flag any customer with active jobs exceeding the BambooHR plan limit before migration so the admin can upgrade or close stale postings.
Employee (HRIS layer) → Employee
Workable HRIS Employee records (name, personal email, phone, address, hire date, employment status, department, job title) map directly to BambooHR Employee records.
How it maps
We use the Workable HRIS export endpoint and map department and job title to BambooHR's organizational structure fields. Employment status (active, inactive, contractor) maps to BambooHR's employment status values.
Interview → Note or Custom Field
Workable Interview records (date, interviewer, meeting type, candidate, job) do not have a native BambooHR equivalent object.
How it maps
We map interviews to structured notes on the Applicant record with interviewer name, date, and meeting type stored in a standardized format. If the customer uses BambooHR's hiring add-on, interview scheduling data is re-created manually using BambooHR's calendar integration.
Scorecard → Custom Fields on Applicant
Workable scorecards are structured evaluation templates with rating scales and written feedback attached to interviews.
How it maps
BambooHR does not have a native scorecard object. We map scorecard template names and field labels to custom fields on the BambooHR Applicant object, and preserve the actual ratings and written feedback as structured values. Rating scales (1-5 stars, thumbs up/down, pass/no pass) are noted and mapped to numeric or text custom fields; the original scale is preserved in field-level documentation.
Offer → Offer Letter (via Document or Custom Field)
Workable Offers store compensation details, start dates, and status (accepted, declined, retracted).
How it maps
We map accepted offers to BambooHR employee records with hire date and job title populated from the offer. Offer letter attachments migrate as documents re-linked to the BambooHR Employee record. Offer status and compensation details are stored in custom fields on the Employee or in the onboarding checklist.
- CandidateApplicant1:1
- JobJob Opening1:1
- EmployeeEmployee1:1
- InterviewNote or Custom Fieldtransformed
- ScorecardCustom Fields on Applicanttransformed
- OfferOffer Lettertransformed
+ 6 more in the mapping below
How Workable and BambooHR differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Workable | BambooHR |
|---|---|---|
| Platform focus | Recruiting-first ATS with bundled HRIS for onboarding and time-off | HRIS-first platform with ATS, onboarding, performance, and benefits modules |
| ATS pipeline depth | Full candidate pipeline with structured interview kits, scorecards, and multi-interviewer feedback | Applicant tracking with core candidate fields and new-hire packet; evaluation tools are lighter |
| Pricing model | Priced by total company headcount (~$149-$3,000+/month); billing rises with any new hire | Per-employee per-month pricing (from $10/user); volume discounts applied automatically |
| API rate limit | 10 requests per 10 seconds, throttling bulk exports | Higher throughput via REST and Bulk APIs without aggressive rate caps |
| Custom field scope | Custom candidate and job fields available on Standard and above | Custom employee and applicant fields on Pro and above; ATS custom fields are limited |
| Time-off data | PTO balances and approval history on Standard and above | Native time-off management included at all paid tiers; balances carry over |
| Automation | Stage-based automated actions and email triggers on Premier and Enterprise | Workflows and approvals on Pro and above; no equivalent to Workable's hiring-stage automation |
What to watch for in a Workable to BambooHR migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Workable API rate limit of 10 req/10 sec throttles bulk exports
Workable enforces a 10 requests per 10 second rate limit that becomes a bottleneck for candidate-heavy migrations.
How we handle it
We implement exponential backoff and chunk exports into small batches with randomized request spacing. For databases over 2,000 candidates, this pacing extends export timelines significantly. We scope the data volume upfront and provide a realistic export duration estimate before migration begins, warning customers if the export phase alone will take more than a few hours.
Scorecards and interview data lack native BambooHR equivalents
Workable's structured interview scorecards with rating scales and multi-interviewer feedback are a core differentiator, but BambooHR does not have a native scorecard object.
How we handle it
We map scorecards to custom fields on the Applicant record, which preserves the data but loses the structured evaluation workflow. Teams that rely heavily on scorecard-driven hiring decisions should plan to re-establish evaluation templates in BambooHR or adopt a separate evaluation tool post-migration.
Workable-to-BambooHR native integration only fires at the Hired stage
The official Workable-BambooHR integration (documented on both Workable Backstage and BambooHR Marketplace) only exports candidate data when a candidate moves to the Hired stage.
How we handle it
Pipeline history, interview records, and scorecards from earlier stages are not included. A full historical migration must go through a custom export process rather than relying on the native integration, which only covers net-new hired candidates going forward.
Custom field mapping requires Workable Premier or Enterprise
Per Workable's integration documentation, mapping custom Workable data fields into BambooHR requires a Workable Premier or Enterprise plan.
How we handle it
Customers on Workable Standard cannot export custom field data via the official integration path. We audit the Workable plan tier during discovery and flag whether custom field data can be exported directly or requires a manual CSV workaround.
Workable annual billing with no refunds creates overlapping subscription cost
Workable requires annual billing for standard rates and does not issue refunds for mid-cycle cancellations or downgrades.
How we handle it
Customers mid-annual subscription who migrate to BambooHR pay for both platforms simultaneously until the Workable renewal date. We map out the billing cycle dates during scoping and advise on timing the migration cutover close to a renewal date to minimize overlap, or we flag the overlap period for the customer to factor into budget planning.
How the migration runs
Discovery and Workable plan audit
We audit the Workable account across plan tier (Starter/Standard/Premier/Enterprise), active job count, candidate volume, HRIS module usage (Employees, Departments, Time-Off), custom fields, interview scorecard templates, and talent pool structures.
What this step covers
We confirm the API access method (API key availability and rate-limit acknowledgment) and the billing renewal date. The discovery output is a written migration scope with object inventory, volume estimates, and a timeline range based on the API pacing required for the dataset.
Schema pre-creation in BambooHR
We create the destination schema in BambooHR before any data moves.
What this step covers
This includes provisioning Departments and organizational hierarchy, configuring Job Opening fields to match Workable job structure, setting up Applicant stage values (mapped from Workable pipeline stages), and pre-creating any custom fields on Applicant and Employee objects for scorecard and custom field data. Schema is validated in BambooHR's test environment before production data is loaded.
Batched candidate export with rate-limit pacing
We extract all Candidate records from Workable using the REST API with 10-req/10-sec pacing.
What this step covers
Candidates are exported in batches of 50 with randomized delay between batches to avoid 429 responses. Resume attachments are extracted separately using the /candidates/{id}/resume endpoint, also paced. For large candidate databases, this phase may run over multiple days. We generate a candidate inventory report with record counts by stage, source, and job before mapping begins.
Employee and HRIS data export
We extract HRIS-layer data from Workable: Employee records (for customers using Workable's HRIS module), Departments, Time-Off balances, and Job Titles.
What this step covers
If the customer used Workable only for recruiting and managed employees in another system, we skip this step and focus exclusively on ATS data. Department and employee data are validated for completeness before mapping to BambooHR's organizational structure.
Scorecard and interview field mapping
We map Workable scorecard templates and interview data to the BambooHR custom field structure.
What this step covers
Each scorecard question maps to a custom field on the Applicant record; rating values are stored as numeric or text. We generate a field mapping spreadsheet for the customer to review and approve before custom fields are created in BambooHR. This step is iterative because BambooHR's custom field type options (text, number, dropdown, checkbox) constrain how Workable data can be represented.
Production migration in dependency order
We run production migration in record-dependency order: Departments first, then Job Openings (so applicants have a job to apply to), then Employees (for HRIS records), then Applicants (with resume files re-linked), then Time-Off records, then custom field data.
What this step covers
Each phase emits a row-count reconciliation report comparing Workable source counts to BambooHR destination counts. Delta records modified during migration are captured in a final sync pass before cutover.
Cutover, validation, and automation rebuild handoff
We freeze Workable writes during the cutover window, run a final delta sync of any records modified during migration, then enable BambooHR as the system of record.
What this step covers
We deliver a written inventory of all Workable automated actions, stage-based triggers, and talent pool groupings with recommended BambooHR equivalents for the customer's admin to rebuild. We support a one-week hypercare window for reconciliation issues. We do not rebuild Workable automations as BambooHR Workflows within the migration scope; that is a separate engagement or internal admin task.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom field count, and whether interview scorecards and pipeline-stage history are in scope. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Workable to BambooHR →Why teams move from Workable to BambooHR
- Workable prices by total company headcount rather than by recruiter seats, so onboarding any new employee regardless of hiring activity inflates the monthly bill. BambooHR's per-employee model with automatic volume discounts is more predictable for growing companies. G2 and Capterra reviewers consistently cite headcount-based pricing surprises as a driver for evaluating alternatives, with many noting that BambooHR's cost structure becomes substantially more favorable as headcount grows past 50 employees.
- BambooHR consolidates employee records, onboarding, time-off, performance reviews, and benefits tracking in a single platform without requiring a second HRIS subscription. Workable's HRIS module is bundled but reviewers note it lacks the depth of dedicated HRIS platforms for ongoing employee lifecycle management beyond the hiring phase. Teams migrating from Workable to BambooHR are typically consolidating onto one system rather than maintaining parallel subscriptions.
- BambooHR scores higher on overall user satisfaction across ease of use and customer support metrics (4.6 on Capterra vs 4.4 for Workable). Reviewers on G2 specifically call out BambooHR's intuitive layout and mobile app for managing HR tasks on the go, while Workable reviewers highlight ATS strength but note the platform becomes harder to justify when hiring volume does not require an enterprise ATS feature set.
- Workable's native BambooHR integration only fires at the Hired stage, passing candidate details to BambooHR for onboarding. Full candidate pipeline history, interview scorecards, stage progression data, and evaluation ratings require a separate migration approach. Teams that want complete historical recruiting data accessible within BambooHR cannot rely on the native integration to carry that information.
- BambooHR's per-employee pricing model combined with automatic volume discounts and a free 15-day trial lowers the entry barrier compared to Workable's annual-billing-required model with no refunds. For small to mid-sized teams evaluating HR and ATS consolidation, BambooHR's pricing transparency and month-to-month flexibility represent a structural advantage over Workable's commitment-heavy billing.
Questions, answered
Workable to BambooHR migration questions
How long does a Workable to BambooHR migration take?
Most migrations land between three and five weeks for accounts with fewer than 500 candidates, 50 employees, and straightforward organizational structure. Migrations with large candidate databases (over 5,000 records), extensive interview history, many custom fields, or multiple active job slots with stage progression data extend to eight to twelve weeks because of Workable API rate-limit pacing, resume attachment extraction time, and scorecard field mapping.
Do Workable's automated actions and stage-based triggers migrate to BambooHR?
No. Workable automated actions (email triggers, stage-based rules, interview scheduling automations) and stage-based workflows are configuration data that do not export in a portable format. We do not migrate them as code. We deliver a written inventory of every active Workable automation with its trigger, conditions, actions, and a recommended BambooHR Workflow equivalent for the customer's HR admin to rebuild. BambooHR Workflows are available on Pro and above but use a different trigger and action model.
We already use the native Workable-BambooHR integration. Can FlitStack AI migrate the historical pipeline data that the integration does not cover?
Yes. The native Workable-BambooHR integration only fires when a candidate moves to the Hired stage, passing name, email, phone, job title, department, and resume to BambooHR. It does not cover candidate pipeline history, interview records, scorecards, or stage progression data. We run a custom export of the full candidate database from Workable, including earlier pipeline stages and interview data, and map it to BambooHR Applicant records with scorecard data stored in custom fields. Resume attachments are extracted and re-associated separately.
Do interview scorecards migrate completely?
Partially. Workable scorecard templates and their ratings can be mapped to BambooHR custom fields on the Applicant record, preserving the question text, rating value, and written feedback. However, the structured evaluation workflow (multi-interviewer assignments, passing thresholds, scorecard routing) does not have a native BambooHR equivalent. We store the structured data; the evaluation process re-creation is documented for the customer's admin to rebuild in BambooHR or a separate evaluation tool.
How does Workable's API rate limit affect the migration timeline?
Workable's 10 requests per 10 second rate limit is the primary constraint for candidate-heavy migrations. We pace exports using exponential backoff and batch processing with randomized delays. For a database of 5,000 candidates with resume attachments, the export phase alone can take two to three days under this constraint. We scope the data volume upfront, estimate the export duration honestly, and warn customers when their dataset will extend the project timeline significantly.
Can we migrate talent pool data from Workable to BambooHR?
Yes, with a structural change. Workable Talent Pools are candidate groupings with names and member associations. BambooHR does not have a native talent pool object. We map pool names and member lists to BambooHR Applicant Tags or a custom status field, depending on how the customer plans to use the groupings in BambooHR. The customer selects the approach during scoping based on their talent pool usage pattern.
What happens to our Workable data after migration to BambooHR?
FlitStack AI does not retain source data after migration completion. We deliver a final reconciliation report with record counts by object and a field-level mapping audit, then the customer controls Workable account closure. Workable's data retention and account cancellation policies are independent of the migration; we advise customers to review Workable's data export and account closure process separately with their Workable account manager, particularly given the annual billing model and no-refund policy.
Related migrations
Sources: official documentation
- Import Tool Training — BambooHR Partners
- Custom Dashboards: Import CSV Data — BambooHR Product Updates
- Importing Data into BambooHR — BambooHR Support
- Field Types — BambooHR Documentation
- Add or Update Values for List Fields — BambooHR Documentation
- Sync HRIS Data from BambooHR — Culture Amp Support
- Customize Your BambooHR Account — BambooHR Help Center
Get a quote
Moving from Workable to BambooHR?
Tell us roughly how many records and objects you have. We scope the mapping and the BambooHR setup with you, then send a quote.
Get a quote