Migrate from Superworks to Recruit CRM & ATS

Superworks Employee records map to Recruit CRM Candidate records. We extract core fields (first name, last name, email, phone, department, job title, hire date, employment status) and write them to the corresponding Candidate fields. Superworks-specific HRMS fields — payroll components, leave balances, loan EMI amounts, attendance logs, performance review ratings — have no equivalent in Recruit CRM's candidate data model and are excluded from migration. We preserve the original Superworks Employee ID in a custom field sw_employee_id__c on the Candidate record for audit and reconciliation.

Superworks custom payroll components (earnings, deductions, reimbursements, tax deductions) have no standard target in Recruit CRM's candidate schema. We export the full salary structure definition from Superworks as a structured JSON schema document during scoping, then work with the customer's admin to decide which components to store as custom fields on the Candidate object or as part of a custom Salary Info section. Compensation fields that Recruit CRM does not natively support require manual field creation in Recruit CRM settings before migration writes begin.

Superworks loan records (principal, interest rate, tenure, EMI schedule) can be written to custom fields on the Candidate record in Recruit CRM if the customer chooses to retain this data. We export raw loan parameters — principal amount, annual interest rate, start date, loan tenure in months — and write them to custom number and date fields. We do not import Superworks-computed EMI totals because multiple G2 reviewers report that Superworks EMI calculations are frequently incorrect. We recommend recalculating EMI schedules from the raw parameters after migration rather than importing Superworks-calculated totals.

Superworks hierarchical org structure (Company > Departments > Sub-departments) with parent-child relationships maps to Recruit CRM Organizations and Teams. We extract the full department tree, resolve the parent references, and write Organization records with the parent-org relationship preserved. Superworks department IDs are stored in sw_department_id__c on the Recruit CRM Organization for reconciliation.

Leave balance, accrual, and utilization data in Superworks has no equivalent target object in Recruit CRM. The Recruit CRM candidate data model does not include leave entitlement or accrual tracking. We document leave balance snapshot data as a CSV export for the customer's HR admin to retain outside of Recruit CRM. Leave transactions that occur between the export date and go-live create a balance delta that requires manual reconciliation post-migration.

Daily attendance records (clock-in, clock-out, overtime, status) in Superworks have no equivalent in Recruit CRM's ATS data model. Recruit CRM is a recruitment system, not a time and attendance platform. Attendance logs are documented as excluded from migration scope and are not written to any Recruit CRM object.

Superworks performance review cycles, rating scores, objectives, and reviewer comments have no equivalent in Recruit CRM. Recruit CRM does not include an employee evaluation or performance review module. We document performance review data as excluded and recommend the customer retain this as a separate HR archive.

Superworks employee documents (offer letters, contracts, ID proofs) cannot be bulk exported. The platform exposes no API endpoint for programmatic file retrieval, and the UI does not provide a batch download mechanism. Each document must be accessed individually through the Superworks UI. We log all document attachment URLs in a separate file and advise the customer to perform a parallel manual file export prior to or after migration. Candidate document attachments in Recruit CRM are managed separately after go-live.

Superworks tenant-specific custom fields on the Employee object (field names, data types, picklist values) vary by organization. We discover the live custom field schema during scoping via the settings export, build a field-mapping matrix against Recruit CRM custom field types, and create matching custom fields on the Candidate object before migration writes begin. Fields with no equivalent in Recruit CRM are flagged for the admin to either drop or reclassify as notes.

Where Superworks is used for project time tracking, billable and non-billable time entries are linked to employees. Recruit CRM is a recruitment ATS and does not include a project time-tracking module. Time entry data is documented as excluded. The customer retains time entry data in the Superworks export if required for billing or payroll purposes.

Recruit CRM Client Contacts represent recruitment agency client stakeholders (hiring managers, procurement contacts) with no equivalent in Superworks HRMS. This object is not migrated from Superworks. The customer's admin creates Client Contacts in Recruit CRM post-migration as part of the new-system setup.

Recruit CRM Client records represent the recruitment agency's client companies with no equivalent in Superworks. This object is not migrated from Superworks. The customer's admin creates Client records in Recruit CRM post-migration.

Recruit CRM Job records represent job requisitions and vacancy postings with no equivalent in Superworks HRMS. This object is not migrated from Superworks. Job records are created in Recruit CRM by the customer's recruitment team post-migration.

Recruit CRM pipeline stages, candidate status values, and workflow automation rules are not migrated from Superworks because Superworks does not use a recruitment pipeline model. The customer's admin configures pipeline stages, candidate status picklists, and any recruitment-specific workflows in Recruit CRM post-migration.