Migrate your Workable data

Candidates are the primary object in Workable. We export full profiles including communication history, evaluations, comments, and resume attachments via the API. All pipeline stages and scorecards attach to Candidates.

Jobs are tied to company-size pricing tiers and carry a maximum active-job-slot limit per tier. We preserve job title, description, department, and status. We flag if the destination requires job reopening or recreation.

Pipeline stages are per-job and contain candidate counts and movement history. We map stage names and sequences but note that stage behavior varies by plan; some plans gate advanced stage configurations.

Interviews link to Candidates and Jobs, including scheduling data, interviewer assignments, and meeting type. We preserve interview dates and attendees as structured fields.

Scorecards are structured evaluation forms attached to interviews. We export the scorecard template, ratings, and written feedback. Rating scales may differ between source and destination and require field-level mapping.

Offers store compensation details, start dates, and status. We export the full offer record including any attached documents. Status transitions (accepted, declined, retracted) are preserved as lifecycle fields.

Workable's HRIS layer includes Employees, Departments, Job Titles, and Employment Status. We export employee records and org structure but note that HRIS fields vary by plan tier and may require custom field mapping.

Time-off balances and requests are available on Standard and above plans. We export PTO balances and approval history. Balance calculations may differ in the destination system and require reconciliation.

Talent Pools are customer-created groupings of candidates. We export pool names and member associations. Not all ATS systems have an equivalent object; some map to Tags or Segments in the destination.

Workable supports custom candidate and job fields. We audit all custom field names, types, and values before mapping to the destination schema. Custom fields on Jobs may behave differently than custom fields on Candidates.

Resume files and attachments are downloadable via the Workable API. We extract them separately from candidate profile data and re-associate them on import. File naming conventions are preserved where possible.

Recruiters, hiring managers, and collaborators are assigned per job. We export team member roles and map them to Owner or Team fields in the destination. Role naming differs across platforms.

Workable automated actions (email/text triggers, stage-based rules) are configuration data that do not have a portable export format. We document the rules during discovery but do not migrate them as functional automation.