Migrate from Avionté Staffing and Recruiting Software to BambooHR

Avionté Candidates with a Placement record map to BambooHR Employee. We preserve contact information, emergency contacts, and resume data. Candidates without a Placement (unhired applicants) map to BambooHR Job Applicants if the BambooHR Hiring module is active, or to a separate tracking spreadsheet if no ATS feature is purchased. Historical candidate status (active pipeline stage) is preserved as a custom Employee field because BambooHR does not have a candidate pipeline object.

Avionté Placement records (active hire connecting Candidate to Job) become BambooHR employment history entries on the Employee record. We map start_date, termination_date, pay_rate, and bill_rate. Placements can recur for the same Candidate across multiple Jobs, creating multiple employment history entries in BambooHR. If the same Candidate has been placed multiple times, we create one BambooHR Employee per placement and link them via a custom employee_id field, or we consolidate under a single Employee with multiple Employment History entries if BambooHR supports that structure in the destination tier.

Avionté Assignments (active work periods for placed candidates with schedule details and assignment-specific rates) do not have a direct BambooHR equivalent because BambooHR is an HRIS, not a staffing platform. We convert Assignment data to BambooHR custom Employee fields (e.g., current_assignment_rate, current_assignment_start) and Employment History notes. Assignment termination and new assignment records update the Employee custom fields and create new Employment History entries. We flag this as a partial-loss scenario if BambooHR does not support the required number of custom fields or nested employment history records in the purchased tier.

Avionté Job records (open requisitions linked to Companies) map to BambooHR Job Openings in the Hiring module. We map job title, department, location, and requirements. Avionté's pipeline stage status migrates as a custom Job Opening field or as a BambooHR Job Stage value if the customer uses BambooHR Hiring. Job order requirements and position categories from Avionté attach as job opening custom fields.

Avionté Companies (staffing firm's client organizations with billing profiles) have no direct BambooHR equivalent because BambooHR is employee-centric rather than client-centric. Client company information from Avionté is preserved as a custom Employee field (e.g., last_placement_client) or as a Job Opening metadata field on the most recent job linked to that client. The customer chooses the representation during scoping. Dedicated VMS client management remains in the customer's vendor management system and is not migrated.

Avionté Time Entries (hours worked on Assignments) require BambooHR Time Tracking to be active. If BambooHR Time Tracking is configured, Time Entries map to historical time-off requests or timesheet records. If BambooHR Time Tracking is not purchased, Time Entry data is preserved as a custom Employee field or documented in the written handoff as a BambooHR gap. Time Entry approval status and batch grouping from Avionté do not transfer because BambooHR lacks an equivalent approval workflow for time entries.

Avionté User records (recruiters, account managers, administrators) map to BambooHR User accounts. We match by email address and map the user name. Active Avionté users receive BambooHR user accounts; inactive users are flagged in a reconciliation queue for the customer to provision or deactivate. Owner assignment on migrated records is resolved via this user mapping.

Avionté's shared Position & Skills taxonomy is a lookup table used by both Jobs and Candidates. We extract the full taxonomy as a separate migration artifact, remap each tag ID to a BambooHR custom Employee field or Job Opening category, and reattach tag associations to each migrated Employee and Job Opening. Skill tags used for candidate-to-job matching in Avionté become static metadata in BambooHR; matching functionality is not preserved.

Avionté Activity logs (recruiter touchpoints including calls, emails, meetings, and notes) map to BambooHR Employee Notes with timestamps. The Who (Candidate) and What (Job, Placement) context is preserved in the Note body. High-volume activity histories may require chunked migration due to BambooHR API write limits. Activity data is migrated as notes only; BambooHR does not have a native engagement timeline feature.

Avionté custom fields on core objects (configured via Table Editor in BOLD) are audited during discovery and mapped to BambooHR custom Employee fields. BambooHR supports custom fields on Pro and Elite tiers. We pre-create the destination schema in BambooHR during the sandbox phase, including all field types, before any data import. Fields that have no BambooHR equivalent are documented in the migration handoff with recommended workarounds.

Avionté's configurable recruiting pipeline stages (stage names and count vary by agency configuration) do not map directly to BambooHR's Hiring stage values. We extract the customer's active pipeline definition during discovery, document each stage, and map it to BambooHR Job Stages or a custom Job Opening field. Multi-pipeline configurations in Avionté become multiple Job Opening category sets in BambooHR if the customer has the Hiring module.