Migrate from Avionté Staffing and Recruiting Software to Crelate

Avionté Candidate records (applicants, talent profiles) map to Crelate Person records. We extract contact info, skills, position categories, resume data, and custom applicant properties. Since Crelate uses a unified Person object (no separate Contact vs Candidate split), any Avionté candidate lifecycle stage or applicant status maps to a custom Person field for segmentation. Avionté bulk import CSV format for candidates is used as the extraction layer when API access is restricted. Post-migration, Crelate Person IDs are reconciled against the Avionté candidate ID mapping table for reference.

Avionté Company records (client companies with billing profiles) map to Crelate Organization records. We map company name, contact details, address, and custom company fields. Organization is created before any Person import so that the Crelate Organization lookup relationship is satisfied at the moment of Person insert with a Company assignment. Historical company IDs are preserved in a custom field for reporting continuity.

Avionté Job records (open requisitions linked to Companies) map to Crelate Job records. We migrate job title, requirements, position categories, skill tags, and pipeline stage status. Avionté's bulk import CSV format for Jobs is used as the extraction basis. Crelate Job records are created with the mapped Organization (Company) lookup already resolved. Pipeline stage names are remapped according to the customer's active Avionté workflow configuration.

Avionté Placement records (active hire connecting a Candidate to a Job at a Company) map to Crelate Job records with a placement status indicator. We preserve start dates, termination dates, pay rates, and bill rates in Crelate custom fields since Crelate's Job model handles both job orders and placed assignments. Placements must be established before Assignments; we validate the ID mapping table before proceeding to the Assignment import phase. Closed or terminated placements retain their historical status as Crelate custom field values.

Avionté Assignments (work periods for placed candidates) map to Crelate as custom activity records linked to the corresponding Crelate Job (representing the Placement). Since Crelate does not have a native Assignment object, we create a custom Activity type in Crelate that captures schedule details, assignment-specific pay rates, and work period dates. Assignment structures vary based on Avionté configuration and staffing vertical; we audit the customer's assignment field configuration during discovery. Foreign key dependency: Assignments require a valid Placement ID in Avionté; we enforce the same dependency in Crelate by resolving the parent Job record before assignment records are created.

Avionté Time Entry records (hours worked by placed candidates) map to Crelate custom activity records linked to the Assignment. We export hours, dates, and approval status. Time Entry batches in Avionté must be associated with a valid Assignment ID; we enforce the same parent resolution in Crelate before ingestion. Note: Crelate has no native payroll module, so time entry financial approval workflows do not migrate; we document the approval state as a custom field for the customer's payroll team to reference.

Avionté's shared Position Categories and Skill Tags taxonomy is a lookup table used by both Jobs and Candidates. A single tag like 'E-Commerce' or 'Retail' can appear on multiple records. We extract the full taxonomy separately, create corresponding Tags in Crelate, then reattach tag associations to each migrated Person and Job record during import. The Avionté Positions & Skills table 'Talent Facing' flag maps to a Crelate Tag visibility or category field if the customer's workflow uses candidate-facing skill visibility.

Avionté's recruiting pipeline stages are configurable per workflow, meaning stage names and counts vary by agency configuration. We extract the customer's active pipeline definition from Avionté, map it to Crelate's pipeline stages, and configure the stage values in Crelate before any Job or Person import. Stage probability percentages migrate as Crelate pipeline stage weights if applicable.

Avionté Activity logs (calls, emails, meetings, notes) map to Crelate Activity records linked to the parent Person or Organization. We migrate activity history where the destination system supports engagement logging. High-volume activity exports are batched and chunked to avoid API timeouts. The Avionté activity type (call, email, meeting, note) maps directly to Crelate's activity type enum. Activity timestamps and owner assignments are preserved during migration.

Avionté User records (recruiters, account managers, administrators) map to Crelate User accounts. We map active users to destination Crelate user records by email match, handling owner assignment on migrated Person, Organization, and Job records. Inactive Avionté users are flagged for the customer's admin to decide whether to provision a Crelate account or archive the owner reference. Avionté role-based permissions map to Crelate permission sets and team structures during configuration.

Avionté's payroll module processes earnings, deductions, and tax withholdings tied to Assignments. Crelate has no payroll module. Full payroll history cannot land as functional records in Crelate. We extract the payroll data as a structured export (CSV or JSON) with field mapping to a payroll-specific format, so the customer's payroll team or external payroll provider can use it. This is a migration scope item that requires customer sign-off before extraction begins.

Avionté generates invoices through a billing batch process tied to Time Entries and Placements. We export posted invoice records and line items as a structured financial export. The billing batch workflow state (draft vs. posted) is scoped: only posted invoices represent closed financial records and are included in the export. Draft or error-state batches are flagged for the customer to resolve or discard before migration. Invoice exports are delivered as CSV with line items preserved for the customer's accounting team to reconcile.

Avionté supports custom fields on core objects via the Table Editor. Crelate supports full custom field configuration with field mapping from custom forms to parent record columns. We audit the customer's Avionté custom field configuration during discovery, map each to the corresponding Crelate custom field (creating the destination schema before import), and flag any Avionté custom field types that have no Crelate equivalent. Multi-select picklists, date fields, currency fields, and free-text fields all map directly; lookup relationships are recreated as Crelate reference fields.