Migrate from Roubler to BambooHR

Roubler Employee records map to BambooHR Employee. Core fields (first name, last name, date of birth, contact details, employment type, start date, termination date) are stable and exportable via API. We migrate all active and terminated employees with full employment history dates preserved. Custom fields on employee profiles migrate as BambooHR custom fields; we pre-create these in BambooHR during schema design with equivalent field types (text, date, dropdown) before import.

Roubler Positions (roles allocated a set of tasks and an FTE value) flatten into BambooHR Job Title on the employee profile. Roubler's FTE fraction (e.g., 0.8 for part-time) maps to a BambooHR custom field fte_value__c since BambooHR does not have a native FTE field. Where Roubler uses headcount-to-hours conversion for casual workers, we set employment type to Casual in BambooHR and preserve the hours-per-week expectation in a custom field.

Roubler roster and shift history migrates as a structured timesheet import into BambooHR. Demand-based rostering linked to POS sales data cannot transfer meaningfully since BambooHR has no equivalent scheduling engine; we document the demand-rostering pattern in a written handoff for the customer's HR admin to configure as manual schedule rules in BambooHR. Open shifts and provisional assignments are flagged in the extraction report for manual review before import.

Roubler leave entitlements, accrual history, and current balances migrate to BambooHR Time Off. We preserve the leave type name (Annual, Sick, Personal), accrual rate, accrual frequency, and balance as of the migration effective date. Note that Roubler's award-linked accrual rules (built for Australian employment law) cannot migrate as rule logic; we document each rule in a written leave configuration guide for the customer's admin to rebuild in BambooHR's Time Off policy setup.

Roubler timesheet records (linked to rostered shifts and clock-in/out events) migrate to BambooHR time tracking entries. We extract hours worked by employee by date, map to the appropriate pay period, and import as hour-based entries. Timesheets linked to locked payroll runs are flagged in the extraction report; locked records migrate as read-only history and cannot be modified in Roubler before extraction.

Roubler payroll runs (run summaries, gross/net amounts, pay period summaries) are not migrated to BambooHR because BambooHR Payroll is a separate add-on product with its own payroll run model. We export a payroll summary report for the customer's finance team to use as a reference document. Employees, employment type, and pay frequency migrate so that BambooHR Payroll can be configured post-migration with matching pay schedules.

Roubler onboarding workflow state migrates to BambooHR Onboarding. We extract the current state of each onboarding checklist, task status, and document collection progress for each employee. In-progress tasks flagged as incomplete in Roubler are imported as pending items in BambooHR with a note that the task originated from the previous system. Completed tasks are recorded as done.

Roubler integration configuration (Xero, MYOB, QuickBooks Online, Workable, POS webhook URLs, credentials, and mapping rules) is not exportable via API and must be reconfigured manually in each destination system. We deliver a written integration inventory listing every active Roubler integration with its connection type, field mapping, and recommended reconfiguration steps for BambooHR or the destination platform.

Roubler custom fields on employee and position objects export as flat key-value pairs. We pre-create matching custom fields in BambooHR during schema design, aligning field names and data types (text, date, number, dropdown). Note that custom fields in BambooHR do not sync with integrations; if the customer uses BambooHR integrations downstream, those integrations will not receive custom field values without additional mapping work.

Employee documents (contracts, certifications, IDs, attachments) uploaded to Roubler are not accessible via the public API, so we cannot migrate them automatically. We alert customers during discovery to export documents manually via screen capture or direct download before the migration window closes and provide a document mapping table listing each employee record with the document types on file for manual re-upload to BambooHR.