Migrate from Adapt to Zoho Recruit

Adapt Employee records map to Zoho Recruit Candidate records. The Adapt employee name, email, job title, department, hire date, and any custom employee properties migrate into the corresponding Zoho Recruit Candidate fields. Adapt's email-find enrichment history is stored as a custom field (adapt_email_find_history__c) on the Candidate record because Zoho Recruit does not have a native email-finding audit object. Last Name is mandatory in Zoho Recruit; Adapt records without a last name receive the value 'not provided' per Zoho Recruit migration documentation.

Adapt Contact records map to Zoho Recruit Contacts. The contact name, email, phone, company association, and any custom contact properties migrate to the Zoho Recruit Contact module. The Adapt company association resolves to a Zoho Recruit Client if the company is also migrating, or to a standalone Contact if no Client record exists in scope.

Adapt Company records map to Zoho Recruit Client records. Company name, domain, and industry map to Client Name, Website, and Industry fields. Custom company properties require field-level transformation; if Zoho Recruit does not have a matching standard field, we create a custom field in the Client module during schema setup and note it in the migration inventory.

Adapt Department records do not have a direct Zoho Recruit equivalent because Zoho Recruit organizes candidates by Job Opening and Client rather than by organizational department. We export the full department hierarchy and represent it as Zoho Recruit Tags on the Candidate record (one tag per department level) plus a custom picklist field (candidate_department__c) that preserves the primary department assignment. Department IDs remap to the tag name during transform.

Adapt Job/Position records (job titles stored on employee profiles) do not map directly to Zoho Recruit Job Openings because Zoho Recruit openings represent active requisitions, not historical position records. We create a Zoho Recruit Job Opening for each distinct job title found in the Adapt roster if the customer wants to track historical positions. Alternatively, we document all distinct job titles as a picklist on the Candidate record and treat them as reference data.

PTO balance data from Adapt (current balance and accrual history) does not have a native Zoho Recruit equivalent because Zoho Recruit is an ATS, not an HRMS. We migrate the current PTO balance as a custom number field (pto_balance_days__c) on the Candidate record. Accrual history is documented as a separate CSV export for the customer's HR team to manage in a downstream HRMS or payroll system.

Salary and compensation records from Adapt migrate as custom fields on the Candidate record (most_recent_salary__c, salary_effective_date__c). Full compensation timeline is documented as a separate CSV for the customer's HR team; Zoho Recruit does not support a compensation history object because it is an ATS, not an HRMS. We flag this boundary during scoping so the customer knows to retain the full compensation history separately.

Adapt custom employee properties migrate to Zoho Recruit custom fields on the Candidate module. We preserve the data type (text, date, number, picklist) by matching to the closest Zoho Recruit field type. If Zoho Recruit does not have a matching standard field for a custom property, we create it during schema setup. Custom field names use the Zoho Recruit naming convention and are documented in the migration inventory with their source property name from Adapt.

Adapt Owners (users assigned to employee or contact records) map to Zoho Recruit Users by email match. We resolve each Adapt owner to a Zoho Recruit User during the migration. If a Zoho Recruit User does not exist for an Adapt owner, we hold that record in a reconciliation queue for the customer's admin to provision the User before record import resumes.

Adapt stores enrichment metadata from its browser extension including email-find history and confidence scores. This metadata has no direct Zoho Recruit equivalent. We preserve it as custom fields on the Candidate record (adapt_email_find_status__c, adapt_email_confidence__c) so the recruiting team can see which candidate contacts were found via the Adapt extension and at what confidence level, even after migration is complete.

Employee records in Adapt may have attached documents (resume equivalents, onboarding files, contracts). We extract these attachments and link them to the corresponding Candidate record in Zoho Recruit via the Attachment object. Resume parsing results from Adapt migrate as notes on the Candidate record if no structured resume field exists in the destination schema.

Time-off requests and approval history in Adapt are an HRMS feature with no equivalent in Zoho Recruit's ATS model. We export time-off request data as a CSV for the customer's HR team to handle in their downstream HRMS or payroll system. This is documented in the migration inventory as a separate data package requiring manual import into a non-ATS system.