Migrate your Avature data

Person records are Avature's core object for both candidates and employees. Built-in fields include name, work phone, email, and custom properties. We map all standard fields and preserve custom field values during import. Files can be attached via URL reference or Base64-encoded payload.

Avature maintains Company records as separate entities that Person records can be linked to. Built-in fields and custom fields are supported. We preserve company-person associations and all company metadata during migration.

Job records represent open positions and include status, department, location, and workflow stage. We map job metadata and link existing candidates to their associated job during migration, preserving workflow step assignments.

Avature workflows are configurable sequences for requisitions, onboarding, internal mobility, and events. Workflow definitions are entity-specific and may require field mapping to replicate logic in destination systems with different workflow engines.

Both Person and Company records support custom fields. The External Import Services API accepts custom field values via CSV headers matching field internal names. We enumerate all active custom fields during discovery and map values 1:1.

Avature supports multi-row record tables attached to Person records (e.g., employment history, education). We flatten these into normalized child records for migration, preserving parent-child relationships in the destination.

Avature attachments can be referenced by online URL or included as Base64-encoded content. URL-based attachments migrate cleanly; Base64 payloads require decoding and re-encoding. We flag any attachments exceeding typical size thresholds before import.

Datasets store bulk reference data used by Avature workflows and forms. Dataset structures vary by implementation. We extract dataset records and map them to equivalent lookup tables or custom objects in the destination platform.

Job templates define reusable requisition blueprints including fields, workflow steps, and approval chains. Template logic often requires re-implementation in destination platforms that use different template constructs.

Pipeline stages are customizable statuses within job workflows. Stage names, order, and automation triggers vary by implementation. We map stages to closest-equivalent statuses in the destination ATS and flag any stages with custom automation that may not transfer.

Avature user accounts represent recruiters, hiring managers, and admins with role-based permissions. User identity and role assignments migrate, but destination permission models differ. We map Avature roles to nearest equivalents and flag admin accounts requiring manual review.

Avature supports tagging candidates and building talent pools. Tags map as flat label fields in most destination systems. Pool membership may require conversion to static lists or dynamic segments depending on destination capability.

Notes, ratings, and interview feedback submitted through hiring manager portals are stored as activity records. We extract these as comment/activity history entries and associate them with the correct Person record in the destination.

Avature onboarding module tracks new hire setup tasks and document collection. Onboarding data models differ significantly between ATS platforms. We map task status and link documents to the employee record but note that full workflow replication requires destination onboarding configuration.