Migrate from Workable to Recruit CRM & ATS

Workable Candidates map 1:1 to Recruit CRM Candidates. We export full profiles including communication history, evaluations, comments, source, and status. Resume files are extracted separately via /candidates/{id}/résumé since the CSV export does not include attachments; we re-associate each resume file to the matching candidate record post-import. All custom candidate fields audit and map to equivalent Recruit CRM custom fields.

Workable Jobs are a separate object with title, department, location, and status. Recruit CRM stores roles as part of the candidate record rather than a standalone Jobs object. We create a candidate record for each Workable Job with role details preserved, and flag archived jobs for customer decision on whether to migrate or skip. Active-job-slot limits from Workable tiers do not apply in Recruit CRM.

Workable pipeline stages are per-job with movement history and candidate counts. We map stage names and sequences to Recruit CRM's pipeline stages. Recruit CRM configures stages at the system level rather than per-job, so we consolidate the per-job stage map into a shared pipeline configuration and document the original Workable per-job stage assignments for the customer to review.

Workable Interviews link to Candidates and Jobs with scheduling data, interviewer assignments, and meeting type. We preserve interview dates, times, interviewers, and meeting links as structured fields on the mapped Recruit CRM Interview record. Interview scheduling conflicts with Recruit CRM's calendar integration are flagged during scoping.

Workable Scorecards are structured evaluation forms attached to interviews with ratings and written feedback. We export the scorecard template, ratings, and reviewer comments. Rating scales may differ between Workable and Recruit CRM and require normalization during the transform phase. Custom scorecard templates are preserved as the template structure and mapped to Recruit CRM's evaluation format.

Workable Offers store compensation, start date, and status with document attachments. We migrate Offer records as Recruit CRM Placements or as Offer records depending on the destination tenant configuration. Status transitions (accepted, declined, retracted) are preserved as lifecycle data. E-signature documents attached to Workable Offers may require re-upload in Recruit CRM if the e-sign integration differs.

Workable Talent Pools are customer-created groupings of candidates with member associations. Recruit CRM has no separate Talent Pool object; we map Talent Pool memberships to Tags on the candidate record. Each Workable Talent Pool becomes a tag label, and candidates are associated by copying the tag to their Recruit CRM record. Pool descriptions migrate as tag notes if the destination supports them.

Workable recruiters, hiring managers, and collaborators assigned per job map to Recruit CRM Contacts with their original Workable role preserved in a custom field. We resolve recruiters by email match. If the destination Recruit CRM tenant uses the Client module, team members may also map to internal User records depending on the tenant configuration.

Workable custom candidate fields audit and map to Recruit CRM custom fields. Custom field types (text, number, date, picklist, checkbox) must match Recruit CRM's supported field types. Custom fields on Jobs that become role-attached fields in Recruit CRM require separate field creation and association during the configuration phase.

Workable's HRIS layer includes Employees, Departments, Job Titles, and Employment Status on Standard and above plans. Recruit CRM is an ATS and recruitment CRM with no HRIS module. We do not migrate employee records in standard scope. If the customer requires employee data for compliance or reporting, we can export a separate HRIS data file as a manual handoff for their records team rather than a system-to-system import.