Migrate from Sesame HR to BambooHR

Sesame HR Employee records map directly to BambooHR Employee. The primary fields (name, email, hire date, department, job title, manager, employment status) migrate 1:1. We resolve the manager reference to the destination Employee record using a name/email lookup. Any Employee referencing an inactive department is flagged in a pre-import reconciliation report so the customer can map to the correct BambooHR department before insert. Custom properties on Employee (picklist and multi-select types) are read during discovery and mapped using a customer-approved value table before migration.

Sesame HR Contract records (employment type, salary band, start/end dates, contract type) are exported as dated employment history entries and written as custom fields or note attachments on the corresponding BambooHR Employee. BambooHR does not have a standalone Contract object, so we use the Employment Info section and a structured note to preserve contract terms. We handle open-ended, fixed-term, and part-time contract types with separate mapping logic per the customer's approved schema.

Sesame HR clock-in/clock-out records, overtime flags, and break deductions are exported in bulk and written to BambooHR via the time tracking import endpoint. We chunk time entry exports by pay period (typically monthly) to stay under the 1,000 req/min shared rate limit and to align with BambooHR's time tracking period structure. Overtime flags migrate as a custom Time Tracking field or as note text attached to the relevant period.

Sesame HR absence requests and balance records map to BambooHR Time Off entries. We build a leave type mapping table during scoping that converts each Sesame HR leave type (sick, vacation, parental, unpaid) to the corresponding BambooHR Time Off policy. Historical approved absences with dates, approvers, and status migrate as completed Time Off records. Pending or rejected requests are migrated as history but with status preserved for the customer's HR team to reconcile in BambooHR.

Sesame HR Shifts (start/end time, assigned employee, role, location) have no direct BambooHR equivalent. We export the full shift schedule as a structured dataset and attach it as a time period note on each relevant Employee record, or create a custom Employee field group for shift information depending on the customer's BambooHR plan and configuration. Shift conflict rules from Sesame HR are documented in the migration package as a configuration note for BambooHR admin to implement in the Time Tracking module.

Sesame HR candidate and vacancy records map to BambooHR Applicant Tracking System records. We map vacancy status, candidate pipeline stage, source, and notes. If Sesame HR is on Starter (capped at 5 open vacancies), we flag any candidates associated with hidden positions and include them in a manual-handling list. Custom candidate fields are mapped using the same value-table approach as Employee custom properties. BambooHR's job board posting data does not migrate as it is destination-side configuration.

Sesame HR exposes the org chart as a hierarchical tree. We extract it as a flat list of manager-subordinate relationships (employee ID, manager ID, effective date). We detect circular references (where Employee A reports to B who reports to A) during extraction and flag them in a pre-import report. The flat list is then written to BambooHR by setting the Manager field on each Employee record. The BambooHR org chart view is derived from these manager assignments and requires no separate object migration.

Current accrued and available PTO balances per employee are exported from Sesame HR and written to BambooHR as the opening balance for each Time Off policy at migration cutover. We set the effective date to the migration date so that future accruals in BambooHR start from the correct baseline. Balances are validated against Sesame HR's reported totals before insert.

Sesame HR employee tags (custom labels assigned to employees) are exported and mapped to BambooHR Employee Tags. Duplicate tags are merged during transform. Tags used for organizational grouping are evaluated for mapping to BambooHR's department or location fields as a cleaner alternative to tags in the destination.

Sesame HR custom fields on any object (Employee, Contract, Candidate) are read during discovery discovery to capture the full custom field schema including picklist and multi-select options. We pre-create matching custom fields in BambooHR using the custom field builder, matching field type (text, number, date, picklist, multi-select) to the closest BambooHR equivalent. Any picklist values in Sesame HR that do not exist in BambooHR are mapped using a customer-approved value table or appended as text in a separate custom field.

Employee documents (contracts, ID copies, certificates) are exported as binary files from Sesame HR and attached to the corresponding BambooHR Employee record via the BambooHR Files API. We preserve the original filename and document type where possible. Documents exceeding 10 MB are flagged for manual handling due to BambooHR file size limits.