Migrate from Aotal to Crelate

Aotal candidate records map to Crelate Person. We resolve the full name split (FirstName, LastName), email address (as primary Contact field), phone, and address fields. Any role history or previous placement records held on the Aotal candidate are preserved as a reference field or imported as a linked Placement history entry. Aotal's competency profile fields migrate to custom text or multi-select fields on Person unless Crelate's Skills and Certifications entity is enabled.

Aotal organization records map to Crelate Organization. Company name, website, industry classification, address, and billing contact fields transfer directly. Organization is imported before any Person records so that the Organization lookup on Person is satisfied at insert time. If Aotal stores parent-company hierarchies, we map them to Crelate's parent Organization relationship.

Aotal job orders map to Crelate Job. Job title, description, employment type (full-time, part-time, contract), location, and status fields transfer directly. Aotal's job pipeline stages map to Crelate Job status values (Open, Placed, Closed). If Aotal uses custom job stage values, we create matching status options in Crelate before migration.

Aotal placement records map to Crelate Placement. The Placement links a Person (candidate) to a Job and an Organization (client). Start date, end date, placement status, fee, and bill rate transfer directly. Placement fee calculations from Aotal migrate to Crelate's billing fields. We resolve the Person, Job, and Organization foreign keys during the transform phase before inserting Placements.

Aotal role history records represent a candidate's previous placements or employment. These do not map to a single Crelate entity. We split active or most-recent roles to Crelate Placement records and archive historical role entries as a custom Role_History__c object with a Person lookup. Effective dates and employment type preserve through the split.

Aotal competency profiles containing skills, certifications, and ratings vary widely in structure. We evaluate the schema during discovery. If Crelate's built-in Skills and Certifications entity covers the competency types, we map directly. If Aotal stores weighted competency scores or matrix ratings, we create a custom Competency_Profile__c object with a Person lookup and replicate the rating structure.

Aotal's custom talent fields (module-specific configurations, weighted scoring, or talent-acquisition specific fields not in the standard schema) require evaluation during discovery. We create matching custom fields in Crelate before migration. Field types are mapped: Aotal numeric ratings to Crelate number fields, free-text competencies to text fields, and multi-select lists to picklist or multi-select picklist depending on Crelate's supported type.

Aotal onboarding records (checklist items, document completion status, I-9 or equivalent NZ onboarding forms) do not migrate as live records because Crelate is a recruiting ATS without an onboarding module. We export onboarding records as a JSON archive and deliver a written inventory of active onboarding workflows for the customer's admin to configure in Crelate's workflow builder or a complementary onboarding tool.

Aotal performance review cycles, ratings, and goals do not migrate to Crelate. Crelate does not have a native performance management module. We export review history as a JSON archive, flag any performance-linked competency data that should be preserved on the Person record, and deliver a written inventory of active review cycles requiring rebuild in a performance management platform.

Aotal learning module records (training completions, certifications, course enrollments) do not migrate to Crelate. Crelate is a recruiting ATS, not an LMS. We export training history as a JSON archive linked by Person ID and deliver a written inventory of active learning modules and certification expiry tracking requiring rebuild in a dedicated learning platform.

Aotal user accounts (internal staff, recruiters, hiring managers) map to Crelate User records by email address match. User role and permission set assignments from Aotal are documented in the migration scope and handed off to the customer's admin for reassignment in Crelate because permission models differ between platforms.

Binary documents (resumes, signed agreements, compliance forms) attached to Aotal records migrate as Crelate ContentDocument records linked via ContentDocumentLink to the parent Person, Organization, or Job. We flag attachments with proprietary or non-standard internal formats for manual review before import because document rendering is destination-environment dependent.