Migrate from Workable to Crelate

Workable Candidate records map to Crelate Contact records. Workable's flat candidate profile (name, email, phone, social links, application history) becomes a Crelate Contact with standard address and contact info fields preserved. Communication history, comments, and candidate notes migrate as Crelate Activity records or Contact notes. The candidate's current application status maps to a Contact custom field rather than a separate object since Crelate tracks pipeline movement within the Opportunity layer. Workable's candidate scorecards and evaluation ratings migrate as structured custom fields on the Contact.

Workable Job postings (title, description, department, status, location, hiring manager) map to Crelate Job records. Job status (active, paused, archived, draft) migrates to Crelate Job status. Workable's job-specific hiring team assignments (recruiters, hiring managers, collaborators) map to Crelate User assignments on the Job or linked Activity records. Active job count limits per Workable plan tier are flagged during scoping; Crelate's Business tier supports unlimited active job postings.

Workable pipeline stages are per-job with candidate counts and movement history. Crelate uses global Opportunity stages across all Opportunities rather than per-job pipelines. We map Workable stage names and sequence order to Crelate Opportunity stages, preserving probability percentages and stage-specific notes. Stage behavior differences are documented: Workable stage gates may behave differently from Crelate's open-stage model where Opportunities can move freely across stages without hard gates.

Workable Interview records (scheduling data, interviewer assignments, meeting type, date/time) map to Crelate Activity records linked to the relevant Contact and Job. Interviewer assignments migrate as Crelate User associations on the Activity. Meeting location or video link details migrate as Activity notes. Interview feedback collected outside of Workable's structured scorecard model migrates as Contact notes or Activity notes depending on whether the feedback is candidate-specific or general.

Workable scorecards are structured evaluation templates attached to interviews with ratings and written feedback. We export scorecard templates and rating values and map them to Crelate Contact custom fields. Rating scales may differ between platforms (Workable uses numeric or star ratings depending on configuration), so we apply scale normalization during the transform phase. Written feedback migrates as a long-text custom field or as a Contact Activity note depending on volume.

Workable Offers (compensation details, start date, offer status: accepted, declined, retracted) map to Crelate Opportunity records. Offer status transitions migrate as Opportunity custom fields or as stage-like custom fields tracking the offer lifecycle. Attached offer documents migrate as file attachments linked to the Opportunity record. If the customer uses Workable's e-signature feature, signed offer PDFs migrate as Opportunity attachments.

Workable's HRIS layer (Employees, Departments, Job Titles, Employment Status) does not have a direct Crelate equivalent since Crelate is a pure ATS/CRM. We map Employee records to Crelate Contacts tagged with a custom Employee Status field. Departments and Job Titles migrate as Contact custom fields or as a separate Department/Title reference list. Customers who need full HRIS functionality after migration should evaluate Crelate alongside a dedicated HRIS; this mapping ensures employee contact data is preserved but the HRIS-specific fields (time-off balances, employment type, start date) require custom field setup in Crelate.

Workable Time-Off balances and requests (Standard+ plans) do not have a native Crelate equivalent. We map PTO balances and approval history to a Crelate custom object (TimeOff Balance) with a lookup to the Contact record, or to a structured set of custom fields on the Contact record. Balance calculation logic does not migrate; Crelate's workflow engine can be configured to recreate time-off request automation post-migration.

Workable Talent Pools are customer-created groupings of candidates. Crelate does not have a native Talent Pool object but uses Tags and Contact Groups to achieve equivalent segmentation. We export pool names and member associations from Workable and create corresponding Tags in Crelate. If the customer has a small number of high-priority pools, we create Contact Groups named after each pool and assign members during migration. Pool-specific notes or descriptions migrate as Tag descriptions where supported.

Workable custom candidate and job fields migrate to Crelate custom fields on the corresponding Core Record (Contact, Company, Opportunity, Job). We audit all custom field names, types, and values during discovery, flagging any Workable field types that require different Crelate field types (e.g., multi-select picklists in Workable may need to become Crelate multi-select lists or tagged text fields). Crelate's Logical Name field (used in API calls) is set to match the Workable field name for consistency. Custom fields on Jobs migrate to Crelate Job custom fields.

Resume files must be extracted separately from Workable candidate profiles via the /candidates/{id}/resume API endpoint; they are not included in the standard CSV or API candidate export. We script bulk resume extraction using the Workable API, download files in bulk, and re-associate them with the corresponding Crelate Contact record using Crelate's Resume Toolbox or direct file attachment. File naming conventions are preserved where possible. This step extends the migration timeline for candidate-heavy databases.

Workable hiring team members (recruiters, hiring managers, collaborators assigned per job) map to Crelate Users by email match. We extract Workable team member roles and map them to Crelate User assignments on Jobs or Activities. If a Workable hiring manager does not have a Crelate User account, they are mapped as a Contact record with a hiring-manager tag. Role naming differs between platforms and is documented during scoping.