Migrate from Superworks to BambooHR

Superworks employee records (name, email, department, job title, date of hire, employment status, reporting manager, and address fields) map directly to BambooHR Employee records. The employee email address serves as the dedupe key during import. We preserve the Superworks employee ID as a custom field sw_employee_id__c for cross-system reconciliation. Any custom fields on the Superworks employee record are discovered during the schema phase and mapped to BambooHR custom fields of matching type (text, date, dropdown, checkbox).

Superworks attendance records (clock-in timestamp, clock-out timestamp, overtime flag, status: Present/Absent/Half-Day/Holiday) map to BambooHR Time Tracking entries. BambooHR tracks time off separately from worked hours; attendance clock-in/clock-out data migrates as a custom time tracking record type if the customer’s BambooHR plan includes the Time Tracking module. Historical attendance spanning more than 12 months is chunked in monthly batches to avoid export-session timeouts inherent to Superworks’s UI-based export.

Superworks leave balance schema (opening balance, earned leave, used leave, closing balance, effective dates per leave type) does not map directly to BambooHR’s accrual-based Time Off model. BambooHR stores accrual policy rules (accrual rate, carryover limit, cap) rather than running balances. We handle this by migrating the Superworks closing balance snapshot as a static custom field (sw_leave_balance_snapshot__c) on each Employee record, then configure BambooHR accrual policies that produce the same forward balance. The customer reconciles any delta between the snapshot date and go-live through BambooHR’s balance adjustment feature.

Superworks loan accounts (principal amount, interest rate, tenure, EMI schedule, current balance, loan status) migrate to a BambooHR custom object that we create during the schema phase, or to custom fields on the Employee record for simpler loan structures. Because Superworks’s EMI calculation is documented as unreliable, we export raw loan parameters only and recommend the destination recalculate EMI schedules from source parameters. We do not import Superworks-computed totals for balance or interest, as these have been flagged as incorrect by multiple G2 reviewers.

Superworks allows organizations to define arbitrary payroll components (earnings, deductions, reimbursements, tax deductions) with custom names and calculation rules. There is no standard component taxonomy. During scoping, we export the full salary structure definition table from Superworks, map each component to a named custom field in BambooHR (e.g., sw_hra_component__c, sw_conv_allowance__c), and preserve the calculation rule as a field description. If the customer uses BambooHR Payroll add-on, component mapping targets the native Earnings and Deductions fields; otherwise, components migrate as custom fields.

Superworks stores a hierarchical org tree (Company > Departments > Sub-departments) with parent-child relationships. BambooHR uses a flat Departments list where each Department record can have a Parent Department to recreate hierarchy. We export the full org tree from Superworks, preserve the parent_department_id relationship, and reconstruct the hierarchy in BambooHR’s Department structure. The top-level company entity from Superworks maps to the BambooHR company name field.

Superworks review cycles, rating scores, reviewer comments, objectives, and final ratings migrate to BambooHR Performance Management as completed review records. Custom rating scales used in Superworks do not map to BambooHR standard rating types, so we create a custom field (sw_rating_scale__c) to preserve the original scale values. Review dates, reviewer names, and comments migrate to BambooHR’s review history fields.

Where Superworks is used for project-level time tracking beyond attendance clock-in/clock-out, billable and non-billable hours logged per employee per date migrate to BambooHR Time Tracking as time entries. Project and task association from Superworks time entries migrates to a custom field (sw_project_name__c, sw_task_description__c) on the BambooHR time entry since BambooHR Time Tracking does not natively support project/task linkage without a third-party integration.

Superworks supports custom fields on employee and payroll objects with tenant-specific names, data types, and picklist values. We discover the live custom field schema via Superworks settings export, then configure equivalent BambooHR custom fields during the destination schema phase. Picklist values are remapped verbatim; text fields use matching length limits. Custom field mapping is validated during sandbox migration before production import.

Superworks document attachments (offer letters, contracts, ID proofs) linked to employee records cannot be migrated programmatically because Superworks exposes no bulk file export API. We log every document attachment URL identified during scoping, advise the customer to perform a parallel manual export of files through the Superworks UI prior to migration, and provide a mapping table of employee ID to document filenames. The customer manually uploads files to BambooHR’s Files tab post-migration. FlitStack AI cannot programmatically retrieve unlinked files from Superworks.