Migrate from Adapt to Crelate

Adapt Employees map to Crelate People (the primary ATS candidate record). We preserve name, email, phone, job title, hire date, and department assignment as standard fields. Custom employee properties migrate as Crelate custom fields, preserving data type (text, date, number, picklist) where the Crelate plan supports the equivalent field type. The Adapt employee status (active, inactive) maps to the Crelate Person status field. Department assignment resolves to a Crelate Department or custom picklist field.

Adapt Departments are an organizational hierarchy that maps to a Crelate Team (if using Teams functionality) or to a custom picklist or text field on the Person record. We preserve the full department hierarchy as a delimited path or flat list depending on how Crelate's schema is configured. If the customer uses department-specific reporting in Adapt, we recommend a custom Department field on Person rather than relying on a loose text match.

Adapt Contact records (the contact enrichment layer) map to Crelate Contact (the client-facing relationship record distinct from Person). We map name, email, company association, and phone directly. Extension metadata from Adapt's browser extension (email-find history timestamps, confidence scores) migrate as custom fields on the Crelate Contact. If the customer uses the same record as both an Employee and a Contact, we create a Person record in Crelate and link it to the Contact.

Adapt Company records map to Crelate Client. We preserve company name, domain, and industry fields. Custom company properties migrate as Crelate custom fields. Client is created before any Person import so that the Client lookup relationship on Person is satisfied at insert time.

Adapt job title and position records map to Crelate Job (the ATS placement record). Position titles from Adapt may require value normalization if the destination uses a different job taxonomy. We map the most recent title and any position history as custom fields on the Crelate Job or as a note attachment if the position history is too unstructured to fit a standard field.

PTO balances in Adapt (current balance and accrual history) cannot be mapped to native Crelate fields because Crelate does not include a native PTO accrual object. We export the current PTO balance snapshot as a custom number field on the Person record and note the accrual history as a structured note attachment for HR reference. If the customer requires ongoing PTO tracking in Crelate, we recommend adding a third-party integration or a dedicated HRIS plugin post-migration.

Adapt compensation records (salary, bonuses, equity if available in the customer's tier) migrate as custom fields on the Crelate Person or Job record. We preserve the most recent compensation value as a number field and any compensation change timeline as a structured note. Mapping to Crelate's placement compensation fields requires a pre-migration field mapping session because compensation structures vary significantly by organization.

Adapt supports custom fields on the Employee object at the Enterprise tier. We pre-create equivalent custom fields in Crelate (text, date, number, picklist) during the schema design phase, matching the Adapt field data type to the nearest Crelate field type. Lookup relationships in Adapt (e.g., Employee to Department) require custom field creation in Crelate with a lookup or reference field type if available on the customer's plan.

Adapt's browser extension generates email-find history, enrichment timestamps, and confidence scores that are not native Crelate fields. We export this metadata as custom fields (enrichment_last_found__c, enrichment_confidence__c, enrichment_source__c) on the Crelate Person or Contact record. This preserves the audit trail of where contact data originated without losing the enrichment signal during migration.

Adapt Owners map to Crelate Users by email match. We extract every distinct Owner referenced on Employee, Contact, and Company records and match by email against the Crelate destination User table. Owners without a matching Crelate User go to a reconciliation queue for the customer's admin to provision before record import resumes.

Adapt employee files (resumes, offer letters, HR documents stored as attachments) migrate as document attachments linked to the Crelate Person record via ContentDocumentLink. We preserve the original file name and content type. Binary file migration requires confirming Crelate's storage limits on the customer's plan before migration.

Adapt user accounts (the HRMS login credentials for employees who are also system users) do not map directly to Crelate Users because Crelate User seats are recruiter licenses, not employee records. We flag this distinction during scoping: the customer's admin provisions Crelate Users separately from the Employee-to-Person migration. Former Adapt users who do not use Crelate as recruiters are migrated as Person records only, not as Crelate Users.