Migrate from Sage People to Crelate

Sage People does not have a dedicated candidate object—recruiting data lives in the Recruitment module with candidate profiles, applications, and vacancy records. We extract Candidate and Application records from Sage People's recruitment module and map them to Crelate Candidate records. The candidate's name, email, phone, source channel, and application status migrate directly. Any Sage People candidate record without a valid email is flagged for manual review because Crelate's ATS relies on email as the primary deduplication key.

Sage People Vacancy records (job postings with requirements, compensation bands, department assignments, and status) map to Crelate Job Orders. The vacancy title, description, location, employment type, and department code migrate as Job Order fields. Compensation band ranges from Sage People Vacancy migrate to Crelate salary or rate fields where the customer has configured those fields. Closed or filled vacancies migrate as historical records; open vacancies migrate as active job orders with the Crelate status workflow applied.

Sage People Application records link a Candidate to a Vacancy with application date, stage, interviewer assignments, and notes. We map application status (Applied, Screening, Interview, Offer, Hired, Rejected) to Crelate's pipeline stage values, preserving the original application date. Interviewer assignments from Sage People map to Crelate's Assigned Recruiters field, and application notes migrate as Crelate notes attached to the job application record.

Sage People organizational hierarchy (Departments with parent-child relationships and cost center codes) has no direct Crelate equivalent because Crelate does not manage organizational structure. We map departments as Crelate Team assignments or as tagged values on Job Orders to preserve which internal team owns a requisition. Manager hierarchies that drive Sage People approval chains are not portable to Crelate and are documented for the customer's HR admin to re-establish as Crelate user assignments and permission sets.

Sage People separates Job templates (position definitions with grade, compensation band, and qualifications) from filled Position records. We map Job title and key requirements into the Crelate Job Order description and qualifications fields. Historical position-filling data (which employee filled which role, with what start date) is employment data that Crelate does not store as candidate history unless the customer specifically requests prior employment to appear as candidate work history on the Crelate profile.

Sage People stores employee documents (contracts, certifications, offer letters) as Salesforce ContentDocument attachments linked to the Employee record. We export document metadata (filename, type, upload date) and binary blobs separately, then associate them with the corresponding Crelate Candidate record using the email-based candidate lookup. Crelate's Resume Toolbox stores resumes and candidate documents; other document types (contracts, certifications) are flagged as HR documents that Crelate does not natively manage and are archived to a shared location rather than inserted into Crelate.

Sage People absence records, leave balances, accrual histories, and carryover rules have no Crelate equivalent. Crelate is an ATS and recruitment CRM with no absence or time-off management capability. We flag all absence data as not migratable, recommend archiving to a PDF or HR document store, and note that if the customer continues to need absence management after moving to Crelate, a separate HRIS tool (BambooHR, HiBob, Access PeopleHR) is required for that function.

Sage People compensation records (salary, bonus, equity, and effective-dated pay changes) have no Crelate equivalent. Crelate stores job order compensation bands and offer letter amounts as recruitment-stage data but does not maintain ongoing employee compensation history. We flag compensation history as not migratable and recommend archiving or exporting to a payroll system or spreadsheet. If the customer needs compensation data accessible post-migration, we recommend a dedicated HRMS alongside Crelate.

Sage People Enhanced Objectives and performance review records store goal text, metrics, review ratings, and 360-degree feedback. Crelate has no performance management module. We flag performance data as not migratable and recommend archiving the records separately. If the customer has purchased Crelate Business Plus with advanced workflow capabilities, objectives could theoretically be stored as custom record types, but this is not a native use case and requires explicit configuration.

Sage People Employee records (name, contact info, employment dates, department, job title, manager, employment status) are core HRIS data with no Crelate equivalent. Crelate manages candidates—individuals being recruited—not current employees. We do not migrate Employee records into Crelate. If the customer needs an HR system alongside Crelate, we recommend a dedicated HRIS platform (Sage People replacement such as BambooHR, HiBob, Access PeopleHR) to manage the employee lifecycle, with Crelate handling talent acquisition separately.

Sage People organizations frequently add custom fields with UD_, UDF_, or IM_ prefixes for tracking org-specific attributes. We inventory all active custom fields, compare them against the Sage People reference schema to identify non-prefixed custom fields (which some orgs create without standard prefixes), and map their data types to Crelate's custom field equivalents. Picklist values on custom fields are mapped as explicit value lists in Crelate. Custom fields that reference Sage People objects without a Crelate equivalent (employee, compensation, absence) are flagged as non-migratable.

Sage People workflow rules and approval chains are not exposed via the Salesforce API and cannot be exported automatically. We document every active Sage People workflow during discovery as a written configuration export (trigger, conditions, actions, routing). Crelate's Business Plus and Enterprise tiers include workflow triggers and automation sequencing that the customer's admin uses to rebuild equivalent processes. We deliver the workflow inventory document and provide Crelate workflow guidance, but rebuilding is a manual admin task outside migration scope.