Migrate from Sloneek to BambooHR

Sloneek employee profiles (name, contact, job title, department, location, employment dates) map directly to BambooHR Employee records. Custom fields on Sloneek employee profiles are discovered during scoping, typed using BambooHR's Custom Field Builder (text, number, date, dropdown, checkbox, or employee-dependent types), and imported as BambooHR custom fields. We preserve the employee's status (active, inactive, terminated) and any GDPR consent flags as BambooHR custom fields for compliance continuity.

Sloneek departments, cost centers, and org chart hierarchies export as structured CSV with parent-child relationships. We reconstruct these in BambooHR as Locations (physical work sites) and Departments (cost-center groupings), and restore reporting lines by setting each employee's department and supervisor field against the resolved BambooHR employee records. Org chart order is preserved in a custom ordering field for post-migration reconstruction if needed.

Sloneek trust-box documents migrate as file attachments on the corresponding BambooHR employee record. We flag every non-PDF attachment in the source data (Sloneek accepts PDF only) and alert the customer during scoping that these files require pre-conversion before import; BambooHR accepts multiple formats. E-signature metadata on documents migrates as a note field for the customer's admin to act on in BambooHR's e-sign workflow.

Sloneek absence requests, accrual balances, leave types, and approval statuses map to BambooHR Time Off. We map Sloneek leave categories (vacation, sick, parental, unpaid) to BambooHR's Time Off types, and carry the accrual balance as of the migration date into BambooHR's starting balance field. Approval history and notes migrate as BambooHR Time Off request comments for audit continuity.

Sloneek's ongoing Attendance 2.0 rollout means a single tenant may contain records in both the old and new attendance schema with different field names and structures. We detect which schema each record uses at export time, normalize both schemas into a unified format, and import the combined history into BambooHR Time Tracking. The migration date determines which records qualify for accrual carry-forward versus history-only import. Records are never dropped during this transition window.

Sloneek ATS candidate records (including resumes, notes, GDPR consent flags, and recruitment pipeline stage) map to BambooHR Job Applicants. Candidate sourcing channel, application date, and stage history migrate as BambooHR application status and a custom stage-history field. GDPR consent timestamps and opt-out flags carry forward as BambooHR custom fields on the applicant record. The customer may need to reconfigure BambooHR's hiring pipeline stages to match Sloneek's stage names; we document the mapping in the migration handoff.

Completed Sloneek performance review cycles (360-degree feedback, goals, ratings) migrate as BambooHR Performance Review records. In-progress and draft reviews are migrated as historical data with a status flag but are not set as active BambooHR review cycles; the customer's HR admin activates cycles post-migration. Rating scales are mapped to BambooHR's rating fields, with any non-matching scale values preserved in a custom notes field.

Sloneek salary, bonus, and deduction history migrate as BambooHR Paychange records where available on the customer's plan tier. Paychange entries carry effective date, pay amount, and change reason. Compensation records that Sloneek stores in its payroll module may require separate export confirmation depending on the customer's Sloneek plan tier; we verify payroll module access during discovery and include compensation in scope only when data is confirmed present.

Sloneek custom fields on employee profiles and select modules are discovered during scoping via export analysis. Each custom field's type (text, numeric, dropdown, date, boolean) is inferred from the data values and mapped to an equivalent BambooHR custom field type. We use BambooHR's Custom Field Builder (accessible to admins without a support request per their 2025 product update) to provision destination fields before record import. Fields without a clear BambooHR equivalent are documented as unmapped in the handoff with an explanation of why no target field exists.

Company assets assigned to employees in Sloneek (equipment, licenses, access credentials) migrate as BambooHR Asset records linked to the corresponding employee. Asset ID, name, type, assigned date, and return status transfer as BambooHR asset fields. Any asset with a pending assignment at migration time is flagged in the reconciliation report for the customer's admin to complete post-migration.