Migrate from Aperio to BambooHR

Aperio employee records map directly to BambooHR Employee. We extract standard fields (first name, last name, email, title, department, manager, hire date, employment status) from the Aperio CSV export and load via BambooHR API or bulk CSV import. Employee ID from Aperio maps to employeeNumber in BambooHR for deduplication. Any Aperio employee record missing a work email is flagged before import because BambooHR requires a valid work email for API-based provisioning.

Organizational structure exports from Aperio as department records with optional parent-department relationships. We map department names directly to BambooHR's Department table, preserving hierarchy where present. Departments must exist in BambooHR before employee import so that the department assignment on each Employee record is valid at insert time.

Job titles export from Aperio and map to BambooHR's Job Title field on the Employee record. BambooHR stores job titles as a flat list associated with the Employment Info tab; there is no separate job title object. Titles used in Aperio review templates as rating criteria are preserved as-is and will need to be re-established in BambooHR's review structure if the Elite Performance add-on is active.

Aperio performance reviews are cycle-based records with ratings against competencies and goals, reviewer comments, and overall scores. BambooHR's Elite Performance add-on supports review cycles but does not replicate Aperio's exact review schema. We extract all review data from Aperio CSV and store ratings, scores, and reviewer comments in BambooHR custom fields on the Employee record. The Aperio review cycle name and period map to a custom text field so that historical review context is preserved. If the customer activates BambooHR Performance, review cycles are rebuilt manually by the admin.

Aperio review cycles define the temporal window for batches of reviews including start and end dates, status, and associated templates. We export cycle metadata and store cycle names and periods as custom fields on the Employee record alongside the review ratings. BambooHR's native Performance module (Elite tier) uses its own review cycle concept that is not automatically populated from this data; the customer rebuilds cycles in BambooHR Performance if that module is active.

Aperio review templates define the structure of reviews including competency sections, rating scales, and mandatory field requirements. Templates are configuration artifacts rather than data records. We do not migrate templates as code because they reference Aperio-specific competency libraries and rating logic that do not map directly to BambooHR's template builder. We deliver a written inventory of all active Aperio templates with their section breakdown and rating scales for the customer's admin to rebuild in BambooHR Performance.

Aperio competency libraries define the rating criteria used within reviews and templates. Competencies are reference data with no direct equivalent in BambooHR's standard schema. We extract competency definitions and ratings as part of the review data migration and store them in custom fields. Any custom competencies require manual reconfiguration in BambooHR Performance if the customer uses the Elite add-on.

Aperio goals export as flat CSV records with goal_id and parent_goal_id columns representing the hierarchy. We extract all goal records, reconstruct parent-child links by pairing goal_id with parent_goal_id, and store goal text, status, due date, and the parent goal reference as custom fields on the Employee record. Orphaned goals (where the parent_goal_id does not exist) and circular references are flagged for customer resolution before loading.

Aperio's nested goal structure flattens in CSV export to parent_id fields. We process the export to extract all goal_id and parent_goal_id pairs, validate that each parent reference resolves to an existing goal, and reconstruct the hierarchy by storing parent goal text in a custom field on each child goal. The goal hierarchy cannot be represented natively in BambooHR because there is no parent-child goal object; the flattened representation in custom fields preserves the relationship for reference.

Aperio development plans track growth actions linked to employees, often tied to review outcomes, with milestones and timelines. BambooHR has no native development plan object. We extract development plan records and their associated milestones, storing plan text and key milestone dates as custom fields on the Employee record. Supporting detail documents are attached as file uploads to the employee profile.

Aperio custom fields on Reviews, Goals, and Development Plans contain picklist and multi-select values that differ from Aperio defaults. These do not self-document in the CSV export. We identify all active custom fields during discovery, export sample values, and map them to BambooHR custom fields by type. Where value sets differ significantly between Aperio and BambooHR picklists, we flag the discrepancy for customer resolution before loading and document the value mapping in the migration spec.