Migrate from Superworks to Crelate

Superworks Employee records map to Crelate Person records. Core fields (first_name, last_name, email, phone, job_title, department, date_of_hire) migrate 1:1. We extract Superworks employee records through an authenticated UI session, parse the exported CSV, and map each row to the Crelate Person API endpoint. We use email as the dedupe key on insert. Any Superworks custom fields on the Employee object are discovered during scoping and mapped to Crelate custom fields (Text, Number, Date, or Picklist) which we pre-create in the destination tenant.

Superworks maintains a hierarchical org tree (Company > Departments > Sub-departments) with parent-child relationships. We export the full structure and map each Superworks department to a Crelate Organization record. The top-level company maps to a Crelate Organization of type Company; sub-departments map to Organization records of type Organization with the parent reference resolved via Crelate's parent_org_id field. Org hierarchy ordering is preserved through the migration sequence.

Superworks Performance Reviews (review cycles, rating scores, reviewer comments, objectives, final ratings per employee) have no direct Crelate equivalent object because Crelate is an ATS and does not store HR performance data. We migrate review history as Crelate Activity Note records linked to the corresponding Person record, with the review date, cycle name, rating, and reviewer comments preserved in the note body. Custom rating scales used in Superworks are preserved as text in the note for audit completeness.

Superworks Attendance Logs (clock-in/clock-out timestamps, overtime flags, attendance status: Present, Absent, Half-Day, Holiday) have no Crelate ATS equivalent. Crelate's schema does not include attendance or time-tracking objects. We flag attendance data as out-of-scope and document the full attendance schema (field names, data types, values) in the migration inventory for the customer's admin to evaluate for a separate time-attendance platform or manual reference.

Superworks Leave Balances (entitlement, accrual, utilization per employee per leave type, opening balance, earned leave, used leave, closing balance with effective dates) have no Crelate ATS equivalent. Crelate does not store leave or time-off data. We export the full leave balance snapshot with effective dates as a CSV and deliver it as a reference document. The customer's HR admin must configure leave management in a dedicated HRMS or payroll platform post-migration.

Superworks Loan Accounts (principal, interest rate, tenure, EMI schedule linked to employees) have no Crelate ATS equivalent. Crelate is a recruiting platform and does not store financial obligation data. Reviewers report Superworks EMI calculations are frequently incorrect, so we export raw loan parameters (principal amount, interest rate, start date, tenure in months) as a separate CSV for the customer's admin to import into their payroll platform of choice. We explicitly do not import Superworks-computed EMI totals due to the known inaccuracy.

Superworks custom payroll components (Earnings, Deductions, Reimbursements, Tax deductions with customer-defined names and calculation rules) have no Crelate ATS equivalent. Crelate does not store compensation data. We export the full salary structure definition table as a CSV during scoping, document the custom component schema (names, types, formulas), and deliver it as a reference for the customer's payroll platform administrator. Any Superworks custom fields on payroll objects are documented with data types for manual mapping.

Superworks supports custom fields on Employee and payroll objects with tenant-specific field names, data types, and picklist values. We discover the live custom field schema during scoping via the settings export, export the full field definition table, and pre-create matching Crelate custom fields on the Person object before migration. Mapping type depends on data type: Superworks text and number fields map to Crelate Text and Number custom fields; Superworks picklist fields map to Crelate Picklist custom fields with values preserved.

Where Superworks is used for project time tracking (billable and non-billable hours logged per employee per date separate from attendance), these records have no Crelate ATS equivalent. Crelate tracks candidate and placement activity, not employee time against projects. We export time entries as a reference CSV and document the schema for the customer's project management or payroll administrator to evaluate.

Superworks stores document attachments (offer letters, ID proofs, contracts, employment agreements) linked to employee records with no bulk export mechanism. Each file must be downloaded individually through the UI. We log all document attachment URLs identified during the scoping session and advise the customer to perform a parallel manual file export using a browser-based batch download tool or the platform's native export function prior to the record migration. FlitStack AI cannot programmatically retrieve unlinked file attachments from Superworks.

Superworks maintains a multi-level org hierarchy (Company > Department > Sub-department) with parent-child relationships. We export the full tree, resolve each department's parent reference, and map it to Crelate's Organization hierarchy using parent_org_id on each Organization record. The resolution order ensures parent organizations are created before child organizations so that the foreign key reference is satisfied at insert time.

Superworks employee status (active, inactive, on leave, terminated) maps to Crelate Person status. We export the status value per employee record and map it to the corresponding Crelate Person status field. Terminated employees from Superworks can be migrated as inactive Person records or excluded based on the customer's preference documented during scoping.