Migrate from Adapt to Recruit CRM & ATS

Adapt Employee records map to Recruit CRM Candidate records. Standard fields including name, email, job title, phone, and hire date migrate directly. We preserve any custom employee properties as custom fields on the Candidate record, maintaining data type where Recruit CRM supports the equivalent type (text, date, number, picklist). Enrichment metadata from Adapt's browser extension history migrates to a custom long-text field on Candidate capturing the email-find history, source, and confidence score so recruiters retain context on data provenance.

Adapt Department records map to Recruit CRM Teams if the customer's plan supports team-based assignment, or to a custom picklist field on Candidate. We preserve the full department hierarchy as a hierarchical picklist or as separate custom fields (department, division, cost_center) based on how the customer organizes reporting in Recruit CRM. Department-to-team mapping is confirmed during the scoping session.

Adapt Contact records tagged as candidate-facing migrate to Recruit CRM Candidate; those tagged as client-facing migrate to Recruit CRM Client. We use a contact_type or category field from Adapt as the split key. Any Contact without a type designation is flagged in the extraction audit for manual classification before import.

Adapt Company records map to Recruit CRM Client records. Company name, domain, industry, and address fields migrate directly. Custom company properties require field-level transformation during migration; we map these to Recruit CRM custom fields on the Client object. The client's domain becomes the Client Website field and serves as the dedupe key during import.

Adapt Job or Position records map to Recruit CRM Job records. Job title, status (open/closed/filled), and job description migrate directly. If Adapt stores job requirements or skills as structured fields, we map them to Recruit CRM's Skills picklist or custom fields. Job status workflow (opening to placement) maps to Recruit CRM's job stage pipeline.

Adapt PTO balance records (current balance and accrual history) have no equivalent in Recruit CRM's ATS+CRM data model. Recruit CRM is a recruiting platform and does not include HR or time-off management modules. We export PTO balances as a CSV snapshot that the customer's HR team retains separately and recommend migrating to a dedicated HRMS if PTO tracking is required post-switch.

Adapt compensation and salary records (available in higher tiers) have no standard equivalent in Recruit CRM's Candidate object. If the customer uses Recruit CRM's Custom Fields feature, we map the most recent compensation value to a custom currency field on Candidate as a reference snapshot. Full compensation timeline does not migrate to Recruit CRM and should be archived in the customer's HRIS.

Adapt supports custom fields on the Employee object. We migrate these as custom fields in Recruit CRM, preserving data type where the destination supports the equivalent (text, date, number, picklist). We pre-create the destination custom field schema in Recruit CRM before any data import. Custom field naming follows Recruit CRM's field-naming conventions and is validated against their field-type restrictions during the scoping phase.

Adapt Owners referenced on Employee, Contact, and Company records map to Recruit CRM Users by email match. We extract every distinct Owner from the Adapt export and reconcile against the Recruit CRM User list. Owners without a matching Recruit CRM User are held in a reconciliation queue for the customer's admin to provision before Candidate import resumes.

Adapt workflows, sequences, and automations do not migrate to Recruit CRM because the two platforms use different automation models with incompatible trigger types, conditions, and actions. We deliver a written inventory of every active Adapt automation with its trigger, conditions, and actions, plus a recommendation for the equivalent Recruit CRM automation. The customer's admin rebuilds these post-migration. This is standard scope for all FlitStack AI migrations and is not a pair-specific limitation.