Migrate from ClearCompany to BambooHR

ClearCompany Employee records map directly to BambooHR Employee records. Employment details, department assignment, manager reference, start date, and custom properties migrate as field-to-field mappings using BambooHR's published field list. The BambooHR employee ID is generated at insert time; we preserve the ClearCompany employee ID in a custom field cc_employee_id__c for reconciliation. Any inactive or terminated employees migrate with their status preserved as BambooHR hire and termination dates.

ClearCompany Candidates with a status of hired map to BambooHR Employee records with hire date and onboarding trigger. Candidates who were not hired but have interview history migrate as BambooHR Applicants in the ATS module if that add-on is licensed. We extract the full candidate profile including application answers, source, and rating. Applicants with no hire outcome remain in BambooHR ATS as historical records; we flag these for admin decision on whether to retain them.

ClearCompany Job records map to BambooHR Job postings. The job title, department, location, status (open/closed), and description migrate directly. Active jobs are set to open status in BambooHR; closed jobs are set to closed. Job-to-candidate associations are preserved as notes on the BambooHR Job record for reference but are not migrated as linked records since BambooHR ATS handles this relationship natively.

ClearCompany onboarding task checklists and new-hire workflows map to BambooHR onboarding checklist items. Each ClearCompany task definition becomes a separate checklist item in BambooHR. Conditional branching logic and completion dependencies from ClearCompany are flattened into a sequential task list; conditional logic does not migrate as configured rules. We preserve the original task order, description, and assignee role from ClearCompany.

Performance review records, goals, and calibration data from ClearCompany are extracted and mapped to BambooHR Performance Review entries. Review templates and rating scales vary by organization configuration and migrate as structured review records with rating values preserved. Review cycle names and review period dates map to BambooHR review metadata. We flag any performance reviews with rating scales that do not have a direct BambooHR equivalent for admin decision during scoping.

ClearCompany LMS content including courses, learning paths, and completion records is extracted and catalogued. SCORM packages are flagged explicitly and exported as file packages; we do not re-import SCORM as configured learning content in BambooHR because BambooHR has no native LMS. We deliver a written inventory of all SCORM packages with file references and a recommendation to pair BambooHR with a third-party LMS (360Learning, TalentLMS, or similar) if learning content is critical. Completion records migrate as a reference document for the customer's admin to re-enter in the chosen LMS.

Organizational structure including departments, offices, and reporting relationships exports from ClearCompany and maps to BambooHR Departments. Parent-child department relationships are preserved using BambooHR's department hierarchy. We resolve the top-level department root and build the hierarchy down using the ClearCompany org chart data. Department names and IDs map directly.

ClearCompany user accounts including role assignments, permissions, and active/inactive status are exported. We map ClearCompany roles to BambooHR role equivalents (Admin, Super Admin, Employee) where naming conventions differ. Active users are created in BambooHR during migration; inactive users are flagged for admin decision on whether to provision as inactive or omit.

Custom fields on Employees, Candidates, and Jobs vary by ClearCompany module and tenant configuration. We discover all field definitions during scoping, flag any with picklist constraints or validation rules, and apply mapping logic per field type against BambooHR's custom field API. Multi-select picklists from ClearCompany map to BambooHR multi-select fields; date fields map to BambooHR date fields; text fields map to text fields. Fields without a BambooHR equivalent are flagged as candidates for a separate configuration pass or as data to be stored in a custom BambooHR field.

Documents attached to employee records, candidates, and jobs are exported by reference with file content. We upload documents to BambooHR Files and link them to the relevant employee record using BambooHR's file attachment API. We flag any documents exceeding typical size thresholds and confirm with the customer whether oversized files should be migrated or archived separately. Documents attached to candidates that were not hired are flagged for admin decision.