Migrate from Avature to BambooHR

Avature Person records with candidate status (applied to a Job) map to BambooHR Applicants if the customer licenses the BambooHR ATS add-on. Candidates without an associated Job map to a candidate reference table that we deliver as a CSV inventory for the customer's admin to reconcile. BambooHR ATS lacks Avature's talent pool and passive candidate CRM capabilities; we flag this gap during scoping and document which Avature talent pools require manual rebuild or deprecation.

Avature Person records with employee status map directly to BambooHR Employee records. Standard fields (name, work email, department, job title, hire date, employment status) migrate as typed fields. The Person record's unique identifier is preserved in a BambooHR custom field avature_person_id__c for cross-system reconciliation. Employee status (active, inactive, terminated) maps from Avature's status property.

Avature multi-row record tables attached to Person records (such as prior employment history, education, certifications) do not map directly to any BambooHR native object. We flatten each row into a normalized child record with a parent reference to the BambooHR Employee. These land either as structured employment history data in BambooHR's employee file sections or as a delivered CSV reference table if BambooHR's field structure cannot accommodate the schema. The customer chooses the strategy during scoping.

Avature maintains Company records as separate entities that Person records can link to. BambooHR does not have a standalone Company object; company data lives as metadata on Employee records (company name, address, tax ID). We extract Avature Company records and merge them into the BambooHR company configuration, then resolve the Person-to-Company linkage by mapping the company reference onto each migrated Employee. Company associations without an associated Employee are delivered as a standalone reference CSV.

Avature Job records represent open positions with status, department, location, and workflow stage. BambooHR's ATS add-on uses Positions rather than full Job requisitions. We extract all Job metadata and map status (open, filled, closed) to BambooHR Position status. Jobs with associated candidates map as Applicant records attached to the Position. Archived or filled jobs without candidates are delivered as a job history reference CSV. Avature's complex multi-step approval workflows on Jobs do not migrate and are documented for rebuild.

Avature allows unlimited custom fields on Person records. BambooHR has three fixed Custom fields and an Employee fields API for additional structured data. We enumerate all active Avature custom fields during discovery, classify each by data type and cardinality, and map high-priority fields to BambooHR Custom 1/2/3 or Employee fields API. Low-priority or deprecated fields are delivered in a custom field inventory CSV. Custom fields exceeding BambooHR's three-field limit require a prioritization decision from the customer during scoping.

Avature Company custom fields migrate to BambooHR company configuration fields where equivalent fields exist (address, tax ID, benefits carrier). Non-standard Company custom fields are delivered in a reference CSV attached to the company record inventory. The customer reconciles these post-migration.

Avature's tagging and talent pool segmentation does not have a native BambooHR equivalent. Candidate tags migrate as flat label fields on the applicant or employee record. Talent pool membership is delivered as a tag-based membership CSV. The customer's admin rebuilds active talent pools as BambooHR static lists or employee segments manually post-migration.

Notes, ratings, and interview feedback submitted through Avature's hiring manager portal are stored as activity records linked to the Person. We extract these as comment/activity entries and attach them to the corresponding BambooHR Employee file where the BambooHR data model allows note attachment. Feedback tied to candidate records (not employees) is delivered as a reference CSV.

Avature Workflows are configurable sequences for requisitions, onboarding, internal mobility, and events. BambooHR does not support Avature-style configurable workflows. We do not migrate workflow logic as code. We deliver a written inventory of every active Avature Workflow with its trigger, steps, conditions, and actions, plus a recommended BambooHR process equivalent. The customer's HRIS admin rebuilds critical workflows post-migration. This is standard scope for all Avature to BambooHR migrations.