Migrate from CatalystOne to BambooHR

CatalystOne Persons map to BambooHR Employees as the primary import. We extract core fields (firstName, lastName, preferredName, workEmail, mobilePhone, dateOfBirth, hireDate, terminationDate, employmentStatus) and map them to the corresponding BambooHR employee fields. Custom properties on the Person object vary by customer tenant — we run a pre-migration schema discovery pass against the specific customer's CatalystOne tenant via the developer portal to enumerate all active custom fields before designing the target schema. Custom fields that align to BambooHR standard fields map directly; those that do not are created as BambooHR custom fields or stored as document metadata.

CatalystOne uses a position-based data model where a Position carries title, department, and hierarchy relationships. BambooHR does not have a separate Position object — job title is a field on the Employee record and department is a separate Department entity. We flatten the position-to-employee relationship by mapping Position.title to the employee's jobTitle field and resolving the Position's department reference to the corresponding BambooHR Department. Manager hierarchy migrates by setting each employee's supervisor in BambooHR to the manager's Employee record, resolved via name or employee ID matching.

CatalystOne Competencies store skills, qualifications, and ratings in a structured many-to-many relationship with Persons. BambooHR does not have a native Competency object. We handle this by mapping competency records to BambooHR custom fields on the Employee record where ratings are structured (for example, language proficiency), or by exporting competency profiles as PDF documents attached to the relevant Employee record. The customer chooses the strategy during scoping based on how competency data is used post-migration.

Succession data in CatalystOne is stored as a structured relationship between a Position and one or more candidate Persons with readiness ratings. BambooHR has no native succession planning object. We export the succession hierarchy and associate candidate readiness ratings as a structured note attached to the relevant Position's mapped employee record, or as custom fields if the succession relationship can be expressed as a finite set of candidate-employee references. We flag this as a gap in BambooHR's feature set and recommend a dedicated succession tool if succession planning is a core ongoing requirement.

CatalystOne Performance Reviews carry effective dates, reviewer assignments, ratings, and free-text responses against configurable review templates. Custom review templates mean field count and naming vary per customer. BambooHR's Performance module (Pro and Elite tiers) supports review cycles and goals but does not have a direct equivalent for historical completed reviews from a previous system. We export completed review records as structured PDFs attached to the relevant employee, preserving the rating data and review period. Active or pending reviews at migration time are migrated as BambooHR performance review records if the customer has the BambooHR Performance module enabled.

CatalystOne maintains a department hierarchy with effective-dated historical structure changes. BambooHR has a flat Department list without native historical versioning. We import the current department hierarchy as BambooHR Departments, using the parentDepartment field to preserve the hierarchy chain. Historical org structure changes (effective-dated records showing past department assignments) are exported and delivered as a reconciliation document for the customer's records — they are not imported as live BambooHR records because BambooHR does not support effective-dated department history on the employee record.

CatalystOne stores employee documents (contracts, certifications, policies, offer letters) as binary files with metadata (type, date, owner). We export file binaries alongside metadata and attach them to the corresponding BambooHR Employee record under the Documents section. Some document types (such as contracts with role-specific fields) require custom document type configuration in BambooHR, which we scope during discovery. Documents without an identifiable employee association are imported as company-level files.

CatalystOne links AD and SSO provisioning data and role or group assignments from HR master data. We export the current state of access records (role, group membership, system access flags) as fields on the BambooHR Employee record or as structured notes. Offboarding automation logic does not migrate because it lives in the identity provider layer, not in CatalystOne's API surface. The identity-to-HR mapping (which HR record corresponds to which AD account) is preserved via a cross-reference table we deliver alongside the data export.

CatalystOne syncs HR data to payroll providers (Visma, SAP, and Nordic payroll systems) via managed Azure-hosted integration logic that is CatalystOne's intellectual property and not handed over during migration. We export the field-to-field mappings and integration configuration as a written inventory document so the customer's payroll admin can re-implement the equivalent logic in BambooHR Payroll or their chosen destination payroll system. This is a manual rebuild scope, not an automated data migration.

CatalystOne approval workflows, automated triggers, and HR process rules are configured inside the application and are not exposed via the API. We do not export workflow logic as code. We document the active workflow configurations during discovery (workflow name, trigger, conditions, actions, affected records) as a written inventory for the customer's admin to rebuild in BambooHR using BambooHR's built-in approval routing and onboarding task sequence tools, or to document as a requirements brief for a BambooHR implementation partner.