Migrate from AgileATS to Zoho Recruit

AgileATS Candidates map directly to Zoho Recruit Candidates. We preserve first name, last name, email, phone, address, status, and clearance level as typed fields. Zoho Recruit requires Last Name as a mandatory field — candidates with no last name in the AgileATS export are flagged and assigned 'Not Provided' as a placeholder value per Zoho Recruit's import specification. Clearance level migrates as a custom picklist field (clearance_level__c) on the Candidate module because Zoho Recruit does not have a native clearance field.

AgileATS Job records (requisition title, location, clearance requirements, job category) map to Zoho Recruit Job Openings. The AgileATS job status (Open, On Hold, Closed, Filled) maps to Zoho Recruit's Opening Status field. Active jobs are migrated first; closed or filled jobs can be migrated as inactive records per customer preference.

AgileATS structured Agile Recruiting stages are reconstructed in Zoho Recruit's visual pipeline builder. Stage names and sequence are extracted from the AgileATS export during scoping, mapped to Zoho Recruit pipeline stages, and the ordering is preserved. If the customer uses non-standard stage counts per job, we create multiple Zoho Recruit pipelines with per-job assignments.

AgileATS Offer records (compensation details, start date, offer status) migrate as a linked sub-section under the candidate record. We preserve the offer-to-candidate relationship by matching on candidate email as the dedupe key. Offer status (Accepted, Declined, Pending, Withdrawn) migrates to a custom picklist field offer_status__c on the candidate record.

AgileATS custom fields are extracted during scoping and mapped to Zoho Recruit custom fields. Zoho Recruit requires the data type to be chosen at field creation — we flag any AgileATS custom fields where the implied type (picklist, date, currency, text) is ambiguous from the source data and resolve with the customer before field creation. Zoho Recruit does not allow custom fields in the Call module; any AgileATS call-related custom fields are stored on the parent Candidate record instead.

AgileATS candidate attachments (resumes, certifications, security clearance documents, background forms) are exported from the file store alongside record data. We re-associate attachments to the corresponding Zoho Recruit Candidate record during import. Large attachment volumes require file size validation — Zoho Recruit enforces attachment size limits per the account tier. We flag any files exceeding limits before ingestion.

AgileATS OFCCP, DoL, and EEO reports are generated exports rather than stored data objects. The underlying candidate fields used to generate these reports (EEO flag values, hire dates, job categories, pay ranges) migrate as Zoho Recruit custom fields on Candidate records. Compliance report reconstruction is outside migration scope — we document which migrated fields correspond to which report line items so the customer's compliance team can validate output in Zoho Recruit's reporting module or a third-party compliance tool.

AgileATS User records (recruiter seats, role, org assignment) map to Zoho Recruit Users. Resolution is by email match. If a migrating User already has an active Zoho Recruit account, Zoho Recruit's import documentation requires closing that account before the user can be imported into the organization's Recruit instance. We flag any pre-existing Zoho Recruit accounts during scoping and coordinate closure before the user migration phase.

AgileATS Partner Users are a separate billing class at $20 per seat with restricted permissions. Zoho Recruit does not have a native partner-user concept. We migrate Partner Users as standard Zoho Recruit Users and flag them for permission review during the handoff — the customer's admin sets access levels appropriate to the partner role (limited candidate visibility, read-only access, or client-portal access depending on Zoho Recruit plan tier). Partner assignment on candidate records is preserved as a custom picklist field.

Security clearance level and status stored as structured fields on AgileATS candidate records migrate to a Zoho Recruit custom picklist field. We preserve clearance level (Confidential, Secret, Top Secret, TS/SCI, or none) and clearance status (Active, Expired, Pending) explicitly. Expired or pending clearance values are flagged for the customer to review post-migration because Zoho Recruit does not enforce clearance expiration logic natively.

AgileATS recruiter notes and activity timestamps are exported and mapped to Zoho Recruit Notes (free-text notes attached to Candidate records) and Tasks (recruiter activity log entries). Activity ordering is preserved where the destination supports timestamp-based sorting. Call and meeting activity from AgileATS maps to Zoho Recruit Tasks with Call or Meeting subtypes where applicable.

AgileATS tracks which candidates applied to which jobs as part of the candidate record. In Zoho Recruit, candidate-to-job associations are tracked via the Candidate sub-form on the Job Opening or via the Apply link tracking module. We map the source job association to the destination Job Opening using job title and location as the matching key, reconstructing the candidate pipeline for each active job.