Migrate from Superworks to Zoho Recruit

Superworks employee records map to Zoho Recruit Candidates. The mapping covers first name, last name, email, phone, current department, job title, date of hire, employment status, and reporting manager. Superworks does not have a separate candidate concept — all employee records become Candidates in Zoho Recruit. The customer's admin decides whether to mark migrated records with a status of Hired (to reflect they are existing employees being onboarded into the recruiting tool) or to use a custom Candidate status. We preserve the original Superworks employee ID as a custom field superworks_employee_id__c for audit traceability.

Superworks department hierarchy (Company > Departments > Sub-departments) maps directly to Zoho Recruit Departments. We export the full parent-child relationship and map it to the flat department structure in Zoho Recruit. Reporting manager relationships from Superworks (stored in the employee record) can be preserved as a custom lookup field on the Candidate record or handled through Zoho Recruit's Assignment Rules, depending on the customer's preference during scoping.

Superworks supports custom fields on employee and payroll objects with tenant-specific names, data types, and picklist values. Zoho Recruit supports custom fields per module (50 per module on Standard, 300 per module on Enterprise) with types including single-line text, picklist, date, lookup, multi-line, and checkbox. We discover the live Superworks custom field schema during scoping, map each to a typed Zoho Recruit custom field, and create the fields via the Zoho Recruit UI before migration. Picklist values migrate verbatim; text fields migrate as-is; date fields require format normalization to YYYY-MM-DD.

Superworks performance review cycles, rating scores, reviewer comments, and objectives map to Zoho Recruit Assessments linked to the Candidate record. Review cycle dates migrate as assessment dates; rating scores migrate as the primary score value; reviewer comments migrate as notes. Custom rating scales used by the customer's Superworks instance are preserved as custom fields on the Assessment or as a custom picklist. This mapping requires the customer's Zoho Recruit admin to create the Assessment form structure that matches the Superworks review template before migration begins.

If the customer has defined custom modules in Superworks, we map them to Zoho Recruit Custom Modules. We pre-create the destination module schema (module name, custom fields, field types, picklist values) via Zoho Recruit's Create New Module interface during the schema design phase, then import records during the main migration phase. Any lookup relationships between custom modules and standard objects (Employees, Departments) are resolved before insert using parent-record ID lookup.

Superworks attendance logs (clock-in/clock-out timestamps, overtime flags, attendance status per day per employee) have no equivalent object in Zoho Recruit. Zoho Recruit does not track daily employee attendance. We export attendance records as a dated CSV for the customer's reference, but they cannot be imported into Zoho Recruit as a native record type. The customer must manage attendance in a separate HRMS tool or a Zoho ecosystem product like Zoho People after migration.

Superworks leave entitlement, accrual, and utilization per employee per leave type (opening balance, earned leave, used leave, closing balance, effective dates) has no Zoho Recruit equivalent. Zoho Recruit does not maintain leave balance records. We export the full leave balance snapshot as a dated CSV for the customer's records. Leave management must be handled in a dedicated HRMS post-migration, either in a Zoho ecosystem product like Zoho People or another leave management tool.

Superworks loan accounts with principal, interest rate, tenure, EMI schedule, and repayment history have no Zoho Recruit equivalent. Zoho Recruit is an ATS and does not track financial accounts, loans, or amortization schedules. We export raw loan principal, interest rate, start date, and tenure terms as a dated CSV reference file. Given that Superworks EMI calculations are frequently incorrect (a known platform issue cited by multiple reviewers), the customer should not import Superworks-computed balances. Loan and EMI tracking must be migrated separately to a dedicated payroll or financial tracking system.

Superworks custom payroll components (earnings, deductions, reimbursements, tax deductions) with customer-specific names and calculation rules have no Zoho Recruit equivalent. Zoho Recruit does not store salary structures or payroll component definitions. We export the full salary structure definition table as a reference document, but it cannot be imported into Zoho Recruit. The customer's payroll configuration must be rebuilt in a dedicated payroll tool post-migration.

Superworks stores document attachments (offer letters, contracts, ID proofs) linked to employee records with no bulk download mechanism. Zoho Recruit supports document attachments on Candidate records via the Document Library feature, but the source attachments cannot be retrieved programmatically from Superworks. We log all document attachment URLs visible in the Superworks UI and advise the customer to perform a parallel manual file export of employee documents prior to migration. We do not migrate document files as part of the standard scope.

Where Superworks is used for project time tracking (billable and non-billable hours logged per employee per date), these records have no equivalent in Zoho Recruit's ATS data model. We export time entry records as a dated CSV reference file. Time tracking must be handled in a project management tool or a Zoho ecosystem product like Zoho Projects post-migration.

Superworks does not have a native job opening or requisition object, but if the customer has stored job postings or requisitions as custom objects or linked records in Superworks, we map them to Zoho Recruit Job Openings. This mapping is only applicable if the customer has structured job data in Superworks; if not, the Zoho Recruit Job Opening records are created fresh post-migration by the customer's recruiting team as part of the ATS go-live workflow.