Migrate from Workable to BambooHR

Workable Candidates map to BambooHR Applicants. 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.

Workable Jobs map to BambooHR Job Openings. 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.

Workable HRIS Employee records (name, personal email, phone, address, hire date, employment status, department, job title) map directly to BambooHR Employee records. 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.

Workable Interview records (date, interviewer, meeting type, candidate, job) do not have a native BambooHR equivalent object. 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.

Workable scorecards are structured evaluation templates with rating scales and written feedback attached to interviews. 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.

Workable Offers store compensation details, start dates, and status (accepted, declined, retracted). 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.

Workable PTO balances and approval history on Standard and above plans map to BambooHR Time-Off records. We export balance amounts and approval status, noting that Workable accrual methods may differ from BambooHR's calculation rules. Reconciliation of opening balances is performed before migration, with any discrepancies flagged for the customer's HR admin to resolve.

Workable Departments map directly to BambooHR Departments. Department names, codes, and hierarchies carry over. If Workable uses nested departments, we flatten the hierarchy into BambooHR's single-level department structure and note the parent-child relationship in a custom field.

Workable Talent Pools are customer-created candidate groupings for future roles. BambooHR does not have a native talent pool object. We map pool names and member associations to BambooHR Applicant Tags or a custom status field. The customer selects the approach during scoping based on how they use talent pools in Workable.

Workable recruiters, hiring managers, and collaborators assigned per job map to BambooHR owner or collaborator fields on the Job Opening and Applicant records. Role naming differs between platforms; we use Workable role labels as-is in a custom field on the BambooHR record.

Workable custom candidate fields map to BambooHR custom fields on the Applicant object. We audit all custom field names, types, and values during scoping. Custom fields are available on BambooHR Pro and above; if the destination account is on the Essentials or entry tier, some custom fields may require an upgrade. Note that custom field mapping for Workable data requires a Premier or Enterprise Workable plan per Workable's integration documentation.

Resume files are extracted separately from Workable candidate profiles via the /candidates/{id}/resume endpoint. We batch resume downloads using paced requests to respect the 10-req/10-sec rate limit, then re-associate each file with the corresponding BambooHR Applicant record during import. File naming conventions and timestamps are preserved where supported.