Migrate from Superworks to Bullhorn ATS & CRM

Superworks Employee records map to Bullhorn Candidate. Name, email, phone, department, job title, and date of hire transfer to standard Candidate fields. Superworks org structure assignments (department hierarchy) map to Bullhorn CustomField text fields or Corporate custom fields. Date of hire becomes dateAdded. We flag any Superworks custom fields discovered during scoping and provision matching Bullhorn custom fields before import.

Superworks department hierarchy (Company > Departments > Sub-departments) maps to Bullhorn Corporate records. We extract the org tree, create a Corporate record per Superworks department, and set parent-child relationships via the corporateID reference. The top-level Superworks company becomes the primary Corporate record; sub-departments become child Corporate records.

Superworks daily attendance records (clock-in/clock-out timestamps, overtime flags, status: Present/Absent/Half-Day/Holiday) have no standard Bullhorn equivalent. We create a Bullhorn Custom Object named Attendance with fields for candidateID (lookup), date, clockIn, clockOut, status, and overtimeHours. Bullhorn ATS Growth and above support at least 2 Custom Objects; customers with additional objects (loans, leave) may need Enterprise.

Superworks leave entitlement, accrual, and utilization per employee per leave type (opening balance, earned leave, used leave, closing balance with effective dates) has no Bullhorn standard object. We create a LeaveBalance Custom Object with fields for candidateID, leaveType, accrualYear, openingBalance, earned, used, closingBalance, and effectiveDate. The Bullhorn Custom Object limit (2 on ATS Growth, 10 on Enterprise) applies; we prioritize Custom Objects in this order: LeaveBalance, LoanAccount, and custom payroll fields on Candidate.

Superworks loan accounts (principal, interest rate, tenure, EMI schedule) migrate as a LoanAccount Custom Object. Critically, we export raw parameters (principal amount, annual interest rate, tenure start date, loan tenure in months) rather than Superworks-computed EMI and balance figures, because G2 reviews document consistent EMI calculation errors. We create a Bullhorn LoanAccount Custom Object with fields for candidateID, principal, interestRate, tenureStart, tenureMonths, and monthlyEMI. Bullhorn recomputes EMI from the raw parameters or the customer reconciles post-migration.

Superworks custom payroll components (earnings, deductions, reimbursements, tax deductions) vary by tenant with no standard taxonomy. We export the full salary structure definition table during scoping, then map each component to Bullhorn custom fields on Candidate (baseSalary, hra, conveyanceAllowance, professionalTax, pfDeduction, etc.) or a PayrollComponent Custom Object if the component count exceeds available Candidate custom fields (Bullhorn allows multiple custom fields per entity). The custom field naming follows Superworks component labels with alphanumeric sanitization.

Superworks review cycles, rating scores, reviewer comments, cycle dates, objectives, and final ratings per employee migrate as a Note attached to the Candidate record or as a PerformanceReview Custom Object. Custom rating scales are preserved as-is. We flag the chosen approach during scoping based on the number of review records and whether the customer needs searchable structured data versus narrative notes.

Superworks supports custom fields on employee and payroll objects with tenant-specific names, data types, and picklist values. We discover the live schema via the Superworks settings export, then provision matching Bullhorn custom fields on Candidate (or the relevant Custom Object) via Bullhorn's Field Mappings admin panel before migration. Picklist values map directly; multi-select picklists in Superworks map to Bullhorn multi-select custom fields.

Superworks stores employee documents (offer letters, contracts, ID proofs) as individual file attachments with no bulk export mechanism. Bullhorn supports bulk document import via REST API once files are present. We log every document attachment URL during the Superworks export session, advise the customer to perform a parallel manual file export (or use a browser-based batch download tool), and then link the downloaded files to the corresponding Bullhorn Candidate record by candidate ID. FlitStack AI cannot programmatically retrieve files without an exposed download endpoint.

Where Superworks is used for project time tracking, billable and non-billable hours logged per employee per date migrate as a TimeEntry Custom Object. These are separate from attendance logs (which track clock-in/clock-out). We create a TimeEntry Custom Object with candidateID, date, projectCode, hoursWorked, billable (boolean), and description. This requires a Custom Object slot beyond what LeaveBalance and LoanAccount consume.

Superworks tracks employee status (Active, On Leave, Terminated, Resigned). We map Active and On Leave to Bullhorn Candidate status values of 'Active' or a custom status picklist value. Terminated and Resigned map to 'Inactive' or a custom status. The exact mapping depends on the Bullhorn edition's picklist configuration and is set during scoping.

Superworks leave transactions (leave taken, leave credited, leave lapse) are effective-dated rows that affect closing balance. We capture a balance snapshot at export time. Any transactions occurring between export and go-live create a delta that we re-import as adjustment entries to the LeaveBalance Custom Object or communicate to the customer's HR admin for manual reconciliation.