Migrate from Workable Zone - HRM to Crelate

Workable Candidate records map to Crelate People records with the candidate type designation. The full candidate profile including contact details, application status, source, and pipeline stage assignment migrates 1:1. Resume binaries and attachments are extracted via Workable's bulk API export endpoint and reattached to the corresponding Crelate Person record. Workable's first_name, last_name, email, phone, and address fields map directly to Crelate's equivalent Person fields.

Workable Jobs map to Crelate Job Orders. The active job count in Workable is audited before migration because Workable Standard bills per active job; Crelate does not impose per-job billing. Workable's job title, description, location, employment type, and department fields map to Crelate's job order equivalents. Status (open, paused, closed) maps to Crelate's job order status.

Workable pipeline stages map to Crelate job order stages. We preserve stage names, order, and probability percentages from Workable. Crelate's stage configuration is adjusted during migration to match the Workable pipeline structure exactly so that candidates maintain their correct stage position.

Workable interview scorecards and evaluator feedback migrate as Crelate rating records linked to the Person and Job Order. Structured rating criteria map to Crelate's rating categories; free-text evaluator notes migrate as comments. We flag any formatted rich-text evaluations that require reformatting in Crelate's field type.

Workable Offers map to Crelate Placements with offer status, compensation details, and the offer letter document preserved. Crelate Placements track the placed candidate against a job order and include fee and commission data native to the recruiting agency workflow. We flag whether the offer letter document requires re-attachment in Crelate's document management layer.

Workable custom properties on candidates (text, number, date, dropdown, boolean types) map to Crelate custom properties on People. We create the destination custom property schema in Crelate before migration and map each field by type. Multi-select dropdown values from Workable map to Crelate multi-select properties.

Workable custom properties on jobs migrate to Crelate custom properties on Job Orders. We audit Workable's job-level custom fields during scoping and create matching Crelate custom property definitions before import.

Workable bulk API exports deliver resume binaries, cover letters, and offer letter documents as binary attachments. We reattach each document to the corresponding Crelate Person or Job Order record. File type and original filename are preserved. We flag any oversized files that exceed Crelate's attachment size limits.

Workable Employee records have no Crelate equivalent. Crelate does not function as an HRIS and does not store employee profiles, payroll data, or performance records. We extract Employee records to CSV during migration for the customer's compliance and audit archive, but they do not migrate into Crelate. If the customer needs to preserve employee data, we recommend a parallel migration to a dedicated HRMS platform.

Workable time-off balances, leave requests, and attendance records have no Crelate equivalent. We extract these records as a CSV export for audit purposes but they do not migrate into Crelate. Time-off management requires a separate HRMS destination or manual reconciliation post-migration.

Workable Hiring Plans (structured approval workflows for job reqs) do not migrate to Crelate as automation code. We document every active Hiring Plan in Workable during scoping and deliver a written inventory with Crelate workflow-equivalent recommendations. The customer's admin configures Crelate workflow templates post-migration.

Workable candidate source tracking (Indeed, LinkedIn, referral, direct) maps to Crelate Source records. Source attribution on each candidate migrates as a Source lookup so that recruiting channel analytics are preserved in Crelate's reporting layer.

Workable interview records map to Crelate Activity records of the meeting type, linked to the corresponding Person and Job Order. Interview date, time, location (or video link), interviewer name, and interview type migrate. We resolve the interviewer as a Crelate User by email match.

Workable tags applied to candidates map to Crelate Tags. Multi-checkbox tag values from Workable become Crelate tags that can be applied to People and Job Orders. We preserve the full tag vocabulary from Workable and apply them to the migrated Crelate records during import.

Workable Owners (recruiters assigned to candidates and jobs) map to Crelate Users. We resolve owners by email match against the destination Crelate user list. Owners without a matching Crelate User go to a reconciliation queue for the customer's admin to provision before record import resumes.

Workable's company field on a candidate profile maps to Crelate's Organization lookup on the Person record. If the candidate's current or most recent employer is tracked as a separate entity, we create a corresponding Organization record in Crelate and link it via the Person.OrganizationId lookup.

Workable interview kit templates and scorecard configurations map to Crelate Rating Form Templates. We document the criteria structure, weighting, and rating scale from Workable and deliver a configuration guide for the customer to set up equivalent Rating Forms in Crelate's template builder.

Workable users who access the ATS module map to Crelate Users. We resolve by email match and map the user's role (recruiter, hiring manager, admin) to a corresponding Crelate permission role. Workable users who exclusively managed HRIS functions (payroll, time-off) without ATS access have no Crelate equivalent and are excluded from the user migration.