Migrate from Savvy HRMS to Crelate

Savvy HRMS candidate profiles, application stages, interview scores, and offer details map to Crelate Candidate records. We preserve stage history from the Savvy HRMS Recruitment module as a custom field or tag set in Crelate, converting the source stage names to Crelate pipeline stage equivalents. Interview scores and rating data migrate as custom fields on the Crelate Candidate object. Offer details migrate as a custom record type or note attached to the Candidate. Crelate's talent pool management allows migrated candidates to be immediately searchable for future requisitions.

Savvy HRMS employee records (profiles, job histories, salary details, benefits) map to Crelate Person records with custom field extensions. We separate active employees (who may be hiring candidates) from historical records, migrating active employees as Crelate People with an employee-specific tag. Salary, benefits, and payroll-related fields do not have Crelate equivalents and are enumerated in a written record for the customer's HR admin to evaluate manual entry or a separate HRIS integration.

Savvy HRMS job postings from the Recruitment module map to Crelate Job records. Job title, department, location, employment type, and description migrate as standard Crelate Job fields. Salary ranges from Savvy HRMS migrate as custom fields in Crelate because Crelate Job records support custom salary fields. Status (open, filled, closed) maps to Crelate Job status with a date-aligned transition at cutover.

Savvy HRMS organizations frequently add custom properties to Employee and Candidate objects. We enumerate all active custom fields during scoping, map each to an equivalent Crelate custom field (text, number, date, picklist, or checkbox), and create the destination schema before any data load. Fields with no Crelate equivalent are documented in a custom field inventory delivered with the migration output.

Employee documents such as offer letters, ID copies, and contracts are stored in Savvy HRMS as binary files associated with employee records. We extract the files and attach them to the corresponding Crelate Person record using Crelate's document management or note attachment capability. The association is made via employee-to-person record mapping resolved at migration time. File naming conventions are preserved for audit traceability.

Savvy HRMS payroll runs (earnings, deductions, net pay, tax values, pay periods) have no Crelate equivalent. Crelate is a recruiting platform with no payroll module. We flag payroll data as non-migratable and deliver a written inventory of payroll run records by pay period and employee so the customer's finance team can retain the data in Savvy HRMS read-only or export it to a dedicated payroll system (Rippling, Gusto, ADP) that integrates with Crelate post-migration.

Savvy HRMS leave types, accrual rules, and per-employee balances have no Crelate equivalent. Crelate does not manage time-off or leave. We export leave balances at the agreed cut-off date and deliver them as a structured CSV for the customer's HR admin to evaluate Crelate's third-party time-tracking integrations or a separate leave management system.

Savvy HRMS attendance records (clock-in/clock-out timestamps, overtime, grace period adjustments) have no Crelate equivalent. Crelate has no time-tracking module. We flag attendance data as non-migratable and deliver a structured export of attendance summaries by employee and date range for the customer's HR admin to evaluate third-party time-tracking integrations with Crelate or a standalone attendance platform.

Savvy HRMS review cycles, ratings, competency scores, KRA fields, and custom objectives have no Crelate equivalent. Crelate's talent acquisition focus does not extend to performance management. We flag performance appraisal data as non-migratable and deliver a written record of the last appraisal cycle, ratings, and any open KRA fields per employee so the customer's HR admin can evaluate Crelate's extended ecosystem or a dedicated performance management platform post-migration.

Savvy HRMS L&D records (courses, enrollments, completion statuses, quiz scores, certification expiry dates) have no Crelate equivalent. Crelate does not include a learning management system. We flag L&D completion records as non-migratable and deliver a CSV inventory of certifications and course completion per employee so the customer's L&D admin can evaluate Crelate's third-party integrations or a dedicated LMS platform.

Savvy HRMS contract worker records (contract dates, billing rates, allocation details, vendor assignments) have no Crelate equivalent for ongoing vendor management. Crelate's talent pool can store contractor profiles as People with custom fields, but the contract management and billing tracking features do not exist. We deliver a CSV of contract labor entries for the customer's admin to evaluate manual entry or a vendor management system integration with Crelate.

Savvy HRMS custom objects added by the organization map to Crelate custom fields on the relevant base object (Person, Job, or Candidate) or to Crelate's custom object framework if the customer's Crelate plan supports it. We enumerate all custom object schemas during scoping, map field types to Crelate equivalents, create the destination schema before import, and validate the custom object count and relationship depth during sandbox migration.