Migrate from Avionté Staffing and Recruiting Software to Bullhorn ATS & CRM

Avionté Candidate records map to Bullhorn Candidate. We extract the full contact profile, resume data, skills (from the shared Positions & Skills table), and custom applicant properties. Avionté's candidate-specific skill tags are resolved from the taxonomy lookup and reattached as Bullhorn CandidateSkill records. Custom applicant properties map to Bullhorn custom fields on Candidate. Avionté's VMS status fields and availability indicators map to Candidate custom fields.

Avionté Company records map to Bullhorn ClientCorporation. The Avionté billing profile and client contacts migrate as separate Contact records under the ClientCorporation. Post-migration, existing Avionté Company IDs are referenced by migrated Job and Placement records through Bullhorn's ClientCorporationId foreign key. Any custom fields on Company map to Bullhorn custom fields on ClientCorporation.

Avionté Job records map to Bullhorn JobOrder. Job requirements, position categories, and skill tags are resolved from the shared taxonomy table and reattached as Bullhorn JobOrderSubmissionSkill records linked to the JobOrder. Avionté's pipeline stage status maps to the Bullhorn JobOrder status field. Avionté's bulk CSV import format for jobs provides the extraction template when API access is restricted.

Avionté Placement records (the active hire connecting a Candidate to a Job at a Company) map to Bullhorn Placement. Start dates, termination dates, pay rates, and bill rates migrate directly. The Avionté Placement ID is preserved in a custom field for audit traceability. Bullhorn's Placement object is created before any Assignment or Time Entry import to satisfy foreign-key constraints.

Avionté Assignments track work periods for placed candidates with schedule details and assignment-specific rates. Bullhorn does not have a separate Assignment object; work period details attach to the Placement record. We extract Avionté Assignment records, merge schedule and rate data into Bullhorn Placement fields, and flag any multi-assignment scenarios (concurrent work periods for the same Placement) for manual review during scoping.

Avionté Time Entry records (hours, dates, approval status) map to Bullhorn Timecard records linked to the Placement. We validate the Assignment ID against the Placement mapping table before ingestion. Avionté's time entry batch state (draft vs approved vs posted) maps to Bullhorn Timecard status. Only approved or posted time entries migrate; draft batches are flagged for the customer to finalize or discard before migration begins.

Avionté's shared Positions & Skills lookup table is extracted as a standalone taxonomy export. Each Avionté skill tag receives a Bullhorn equivalent (by name match) or is created as a Bullhorn Skill record. The taxonomy is loaded first, then tag associations are reattached to migrated Candidate and JobOrder records as Bullhorn CandidateSkill and JobOrderSubmissionSkill records respectively, preserving candidate-to-job matching functionality.

Avionté invoices generated through billing batches migrate to Bullhorn Invoice records. Only posted billing batches (Avionté's closed financial state) are in scope; draft, processing, and error-state batches are flagged for the customer to resolve or discard before migration begins. Line items and totals are preserved. Invoice-to-Placement relationships are resolved through the Placement ID mapping table.

Avionté's configurable recruiting pipeline stages (which vary by agency configuration) are extracted as the customer's active stage definition. Each Avionté pipeline stage maps to a Bullhorn JobOrder status value. If the customer uses multiple Avionté pipelines, Bullhorn Record Types are configured to scope status sets per line of business. The stage probability and order migrate as JobOrder custom fields.

Avionté activity logs (calls, emails, meetings, notes) migrate to Bullhorn Note and Task records linked to the parent Candidate, ClientCorporation, JobOrder, or Placement. High-volume activity migrations use Bullhorn's Bulk API with batch chunking. Bullhorn's Activity timeline renders Notes and Tasks in reverse-chronological order using the original timestamp preserved from Avionté.

Avionté user records (recruiters, account managers, administrators) map to Bullhorn User accounts. We resolve users by email match against the Bullhorn destination instance. Any Avionté user without a matching Bullhorn User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignments on migrated records are set after the User mapping is validated.

Avionté's Table Editor custom fields are audited during discovery and mapped to Bullhorn custom fields on the equivalent object. Bullhorn custom fields are created via the Custom Object Setup Sheet submitted to Bullhorn Support before migration. Custom field types (text, drop-down, checkbox, date, number) are matched to the nearest Bullhorn field type. Avionté has no native custom object equivalent, so any custom data beyond object-level fields becomes custom fields on the standard Bullhorn object.