Migrate from Sage HRMS to Crelate

Sage HRMS Employee records map to Crelate Person records. We extract biographical data (name, email, phone, address, hire date, termination date, job title, department, and employee status) via CSV export and transform it to Crelate's Person import template. Active employees become Crelate Persons tagged as potential candidates; terminated employees migrate as talent pool or alumni records. Custom employee fields migrate to Crelate custom fields which we pre-create via the Crelate Settings API before import. Note that Sage HRMS compensation, benefits, and tax withholding data have no Crelate destination object and are not migrated.

If the Sage HRMS ATS module is active, candidate profiles (name, contact information, application status, source, and resume reference) migrate to Crelate Person records tagged as candidates. We map Sage HRMS application status values to Crelate pipeline stage values during transformation. Resume files export as document attachments keyed by candidate ID and are delivered alongside the data migration for manual re-upload to Crelate's document attachment UI. Any custom candidate fields in Sage HRMS pre-create as Crelate custom fields before import.

Sage HRMS job requisitions map to Crelate Opportunity records representing open job orders. We extract job title, department, position type (full-time, part-time, contract), location, and status. Crelate Opportunity custom fields capture additional requisition attributes. The Opportunity in Crelate serves as the parent record for candidate submissions, replacing the linking structure in Sage HRMS ATS.

Sage HRMS application records (candidate linked to job requisition with submission date and status) map to Crelate submission records tied to the Opportunity (job order) and Person (candidate). We preserve the application status, submission date, and any recruiter assignment from Sage HRMS during transformation.

Sage HRMS Positions define job titles, grade levels, and pay ranges. Crelate has no native position or job-grade object. We map positions to Crelate Tags on Person records and to a custom multi-select picklist field on Opportunity for job classification. The customer selects the preferred strategy during scoping.

Sage HRMS Departments are organizational units used in payroll allocation and reporting. Crelate tracks departments as Tags on Person records and as Opportunity classification fields. We extract the full department tree and apply it as Tags during migration.

Sage HRMS stores employee documents as file attachments. We export these as a file bundle keyed by employee ID and deliver them alongside the migration data package for the customer's admin to re-upload manually to the corresponding Crelate Person record. Crelate's document attachment UI does not support programmatic bulk upload in the standard migration scope.

Sage HRMS Pay Groups define pay frequency, deduction priorities, and tax jurisdiction. Crelate has no payroll module and no pay-group object. We export the Pay Group table as a reference document delivered to the customer's admin as part of the non-transferable inventory.

Sage HRMS payroll history (earnings, deductions, tax withholdings across fiscal-year tables) has no Crelate equivalent. We do not migrate payroll history. We export a summary reference file keyed by employee ID for the customer's admin to retain for compliance and audit purposes.

Benefit plan definitions, carrier assignments, and active enrollments have no Crelate object. We export benefit data as a reference document delivered alongside the migration for the customer's admin to retain or import into a dedicated benefits administration platform.

Accrual rules and current time-off balances are Sage HRMS payroll data with no Crelate equivalent. We export balance summaries as of the migration date as a reference document; the destination HRMS handles accrual reset post-migration.

Federal, state, and local tax codes, rates, and agency filing configurations are Sage HRMS payroll-compliance data. We export the tax agency table as a reference document. The customer's next HRMS or payroll platform re-enters tax configurations as part of its own setup.