Migrate from Savvy HRMS to Recruit CRM & ATS

Savvy HRMS stores candidate profiles, application stages, interview scores, and offer details in its Recruitment module. These map directly to Recruit CRM Candidate records. Stage history from Savvy HRMS (Applied, Screening, Interview, Offer, Hired) migrates to Recruit CRM's Candidate Status pipeline, and interview scores migrate as custom numeric fields on the Candidate record. We preserve the full application timeline as a note attachment for audit. If Savvy HRMS tracks source attribution (referral, job board, direct), that field maps to the Candidate.source property in Recruit CRM.

This mapping requires a scoping decision upfront. If the customer is a recruitment firm migrating internal employee records, those employees may map to Recruit CRM User records (for internal staff who will use Recruit CRM as a team) or to Candidate records (if the organization places its own employees into roles tracked in the system). If the customer is an HR team migrating their own workforce to an ATS, the employee records are out-of-scope for Recruit CRM unless converted to a candidate format. We confirm the intended use during discovery and apply the appropriate mapping.

Employee job history from Savvy HRMS (employer name, job title, start date, end date, description) migrates to Recruit CRM Candidate work history records attached to the corresponding Candidate object. Each job history entry becomes a separate work experience record under the Candidate profile, preserving the chronological ordering. Current employment status in Savvy HRMS maps to a custom field on the Candidate record.

Savvy HRMS leave policies and per-employee accrual balances have no equivalent object in Recruit CRM, which does not function as a time-off management system. We extract leave balances as of the agreed cut-off date and deliver them as a structured CSV reference file alongside the migration. The customer's HR admin or payroll system retains responsibility for leave balance accuracy post-migration. We flag this clearly during scoping so it is not treated as a silent gap.

Time and attendance data (clock-in/clock-out timestamps, overtime, grace period adjustments) has no native storage location in Recruit CRM. We extract attendance as structured CSVs at the migration cut-off date and hand them to the customer's HR or payroll team for re-entry in their timekeeping system of record. If the customer uses a separate payroll platform post-migration, we provide attendance in a format compatible with that system's import requirements.

Payslip records containing earnings, deductions, and net pay tied to specific pay periods are out of scope for Recruit CRM. We do not migrate payroll data into Recruit CRM's candidate or client objects. If the customer needs historical payroll as a reference document, we export the payslips as PDFs and attach them to the corresponding employee Candidate record or deliver them as a structured archive alongside the migration. Tax codes and deduction naming conventions do not map because Recruit CRM does not process payroll.

Savvy HRMS stores review cycles, ratings, and competency scores in its Performance module. Recruit CRM has no native performance review object. We extract the most recent appraisal ratings as custom fields on the Candidate record if the customer wants historical performance data visible in Recruit CRM. We flag that Recruit CRM is not a performance management tool and recommend the customer's HR team maintains a separate performance record system.

Savvy HRMS contract worker records (contract dates, billing rates, allocation details) can map to Recruit CRM Candidate records if the contract workers are tracked as talent pool entries, or to Client records if the organization treats the contract vendor as a client. We confirm the intended classification during discovery. The billing rate and contract end date migrate as custom fields on the destination record.

Employee documents such as offer letters, ID copies, contracts, and certifications stored in Savvy HRMS are extracted as binary files. We associate each document with the corresponding migrated Candidate record in Recruit CRM as a file attachment. We preserve the original filename and document type classification (offer_letter, id_proof, contract, certification) in the attachment metadata. Documents without an associated Candidate record are archived in a structured folder for manual assignment post-migration.

Savvy HRMS organizations frequently add custom properties to standard employee and candidate objects. We enumerate all active custom fields during scoping, map them to equivalent Recruit CRM custom fields on the Candidate, Job, or Client objects, and handle type conversion (date, number, text, picklist) explicitly. Any custom fields on objects that have no Recruit CRM equivalent (payroll, leave, attendance) are exported as reference data alongside the migration.