Migrate from Avature to Crelate

Avature Person records (the core object for both candidates and employees) map to Crelate Contact records. Built-in fields including name, work phone, email, and address transfer directly. Custom fields on Person require enumeration against Avature's internal field names before mapping to Crelate's custom Contact fields. Record table rows (employment history, education, certifications) attached to Person records flatten into normalized child records linked to the Contact parent via Crelate's relationship model.

Avature Company records map to Crelate Company records. The company name becomes the Company Name field, and any domain or web presence data transfers to the website field. Avature Person-Company associations migrate as Crelate Contact-Company relationship records. All active custom fields on Company are enumerated and pre-created in Crelate before Company import begins.

Avature Job records (position, status, department, location, workflow stage) map to Crelate Job records. Candidate-job associations migrate as Crelate submission or candidate-to-job link records, preserving the original Avature candidate-to-job linkage and workflow stage at time of association. Job templates do not migrate as templates; we document the template structure for the customer's admin to rebuild as Crelate Jobs.

Avature workflows are configurable sequences with conditional logic, delays, and multi-step actions that have no direct Crelate equivalent. We do not migrate workflow definitions. We deliver a written inventory of every active Avature workflow with its trigger conditions, steps, and action types for the customer's admin to configure in Crelate's workflow builder post-migration.

Avature record tables (multi-row nested structures attached to Person records, such as employment history, education, certifications, and skills) flatten into normalized child records during migration. Each row becomes a separate record linked to the parent Contact via a relationship field. We preserve the parent-child ordering and row sequence from Avature as a sort field in Crelate.

Avature custom fields on Person and Company are enumerated against the External Import Services CSV schema using internal field names during the discovery phase. We create matching custom fields in Crelate with corresponding logical names before import begins. Custom field types (text, number, date, checkbox, picklist) are mapped to Crelate field types. Any picklist-style custom fields require value set mapping between Avature enumerated values and Crelate options.

Avature datasets store bulk reference data used by workflows and forms, with structures varying by implementation. We extract dataset records and map them to Crelate reference data objects, custom lookup tables, or static lists depending on how the data is used. Complex datasets with conditional logic may require redesign in Crelate; we document the dataset structure and recommend a Crelate-native approach.

Avature pipeline stages (customizable statuses within job workflows) map to Crelate Job stages. We preserve the stage order, stage names, and any automation triggers or required fields attached to each stage. Stage probability values migrate where available.

Avature URL-based attachments migrate cleanly to Crelate document attachments linked to the corresponding Contact, Company, or Job record. Base64-encoded attachments require decoding, re-encoding, and re-upload to Crelate's document store. We flag any attachment that cannot be resolved as a valid URL during the enumeration pass.

Avature candidate tags migrate as flat label fields in Crelate's tag system. Talent pool memberships migrate to Crelate talent pools or static candidate lists depending on whether the source pool was static or dynamic. Pool membership criteria for dynamic pools cannot migrate as logic; we document the criteria for admin review.

Notes, ratings, and interview feedback submitted through Avature's hiring manager portal are stored as activity records. We extract these entries and migrate them as comment or activity history entries associated with the correct Contact record. The original submission timestamp and submitting user are preserved as activity metadata.

Avature user accounts representing recruiters, hiring managers, and admins with role-based permissions are enumerated for mapping purposes. Crelate uses a different permission model. We deliver a role mapping table showing each Avature role and its recommended Crelate equivalent; the customer's Crelate admin provisions user accounts and assigns roles post-migration.

Avature onboarding module tracks new hire setup tasks and document collection. Onboarding data models differ significantly between platforms. We migrate task status and link documents to the employee Contact record. The onboarding workflow itself does not migrate; we deliver a written description of the Avature onboarding sequence for the customer's admin to re-implement in Crelate's task management or through a dedicated onboarding tool.