Migrate from Workstream to Crelate

Workstream Employee records map to Crelate Candidate. We extract all three lifecycle tabs (Active, Onboarding, Offboarded) explicitly during scoping and map Workstream's lifecycle state to a custom Crelate field (e.g., original_lifecycle_stage__c) plus Crelate's native candidate status. Workstream standard fields (name, contact info, hire_date, job_title, department, location assignment) map to typed Crelate Candidate fields. We preserve termination date and offboarded reason as custom fields if the customer's compliance policy requires them.

Workstream Positions map to Crelate Job Orders. Each Workstream Position record carries title, department, pay rate/range, schedule type, and job description; these map to Crelate Job Order title, description, and salary fields. We resolve the Workstream location assignment and attach it as a Crelate Job Order location or a custom field. Position status (Open, Paused, Filled, Closed) maps to Crelate Job Order status with the corresponding status values configured in Crelate before migration.

Workstream Position Templates are reusable job definitions that instantiate multiple Position records. We flatten all template-fed Position instances during the export phase, creating one Crelate Job Order per instantiated Position. The template origin is preserved as a tag or custom field on each Job Order (e.g., template_source__c) so the customer can see which positions were standardized versus ad hoc.

Workstream Applications (candidate submissions tied to a Position) map to Crelate's Candidate-to-Job-Order association. Application status (Applied, Screening, Interview, Offer, Hired) maps to Crelate's placement pipeline status values. Screening question answers and communication history migrate as custom fields or notes on the candidate record. We resolve the candidate and job order references at migration time using Workstream's application_id and the extracted candidate and position identifiers.

Workstream Locations are the primary organizational unit and carry name, address, and manager. We map these to Crelate Locations if the Crelate destination has the Locations module enabled, or to Departments if that is the customer's preferred organizational unit. Location-role combinations that determine pay and schedule authority are preserved as custom fields on the Candidate record since Crelate does not natively model per-location role scoping.

Workstream Roles scoped to locations do not have a direct Crelate equivalent. We model location-role combinations as custom fields on Candidate (e.g., location_name__c, role_title__c, assigned_role__c). The pay rate associated with a role-location assignment migrates as a custom field on the Candidate record or as a salary field on the associated Job Order.

Workstream custom fields on employees (text, date, number, dropdown) scoped by role, location, or department migrate to equivalent Crelate custom fields on the Candidate object. Workstream's per-record field presence variation (a field may exist on one employee record but not another) is handled by mapping only fields that are populated for each individual record, avoiding null-fill issues. We detect field-level presence during profiling and generate a per-record field manifest before import.

Workstream position-scoped custom fields migrate to Crelate Job Order custom fields. These typically capture role-specific requirements (certifications required, shift pattern, equipment needed) that Crelate Job Order custom fields can hold. We match field types: Workstream dropdown becomes Crelate picklist, Workstream number becomes Crelate number, Workstream text becomes Crelate text.

Workstream pay rate, pay schedule, and payroll sync status are available as employee properties. We map pay rate to Crelate Job Order salary or to a custom field on the Candidate (e.g., offered_salary__c, pay_rate__c). Workstream's payroll provider integration status (ADP, Paychex, Paylocity) migrates as a text field noting the integration; the OAuth connection itself does not transfer.

Workstream's configurable hiring pipeline stages (Applied, Screening, Interview, Offer, Hired) map to Crelate's candidate status values on the Candidate-Job-Order association. Stage probability percentages and stage order are preserved. If Crelate's default statuses do not match the customer's pipeline, we configure custom status values during the Crelate setup phase before migration.

Offboarded employee records from Workstream's third employee tab migrate to Crelate Candidates with a termination_custom_status__c field set to Offboarded, along with termination_date__c and termination_reason__c custom fields. We include offboarded history only if the customer explicitly opts in during scoping, as Crelate is an ATS not a payroll or HRIS system and offboarded employee records may not align with the customer's active candidate workflow.

Workstream's SMS-based candidate communication history migrates to Crelate Activity records linked to the Candidate. Each SMS thread becomes a note or activity entry with timestamp and direction (sent/received). Crelate's communication tracking does not natively replicate Workstream's SMS UX, so we preserve the communication content as structured notes rather than as native SMS objects. The customer rebuilds automated SMS workflows in Crelate's communication tools post-migration.