Migrate from ApplicantStack to Zoho Recruit

ApplicantStack Positions map directly to Zoho Recruit Job Opening records. Job title, description, status, and opening count transfer. Job board distribution settings (Indeed, JobTarget, custom branded boards) do not carry forward as configuration — we export the job content only; the customer republishes in Zoho Recruit's job board distribution module. If the source position references multiple hiring managers, we create corresponding Zoho Recruit User assignments on the Job Opening record.

ApplicantStack Candidate records map 1:1 to Zoho Recruit Candidate records. First Name, Last Name, email, phone, address, resume file, source, and application date transfer directly. Zoho Recruit requires Last Name as a mandatory field; we resolve null or blank Last Name values to 'not provided' per Zoho Recruit's import specification. Resume files migrate as attachments linked to the candidate record. We run deduplication logic (email match primary, phone match secondary, normalized name string tertiary) before import and flag probable duplicates for customer review so that duplicates are not multiplied in the destination.

ApplicantStack's configurable pipeline stages (Applied, Screening, Interview, Offer, Hired, Rejected) map to Zoho Recruit's Interview stages. We export the full stage configuration from ApplicantStack and recreate it in Zoho Recruit's pipeline settings. Per-candidate stage history migrates as a structured notes or custom field record so that the hiring manager can see the progression timeline in Zoho Recruit.

ApplicantStack Questionnaire responses are stored as field-value pairs on the candidate record. We extract all custom field responses and map them to Zoho Recruit's custom candidate fields. If Zoho Recruit does not have a corresponding field type, we create a custom candidate field during the migration setup phase. Conditional logic on ApplicantStack questionnaires does not transfer; we document the conditional rules for the customer to rebuild in Zoho Recruit's form builder.

ApplicantStack user roles (Administrator, Recruiter, Hiring Manager) map to Zoho Recruit Users with corresponding roles. We export role assignments and map them to Zoho Recruit's role and profile model. The customer provisions the Zoho Recruit users manually or via CSV import before candidate migration begins so that OwnerId references can be resolved during record import. Note: existing Zoho Recruit accounts with the same email cannot be imported as new users — they must close the separate account first per Zoho Recruit's import documentation.

Resume files, cover letters, and any uploaded documents extract from ApplicantStack candidate records as binary blobs. We preserve the original file names and attach them to the corresponding Zoho Recruit Candidate record. If the resume contains structured data (sections, contact info), we do not parse it into Zoho Recruit fields — the file remains as an attachment reference.

When ApplicantStack Onboard is in scope, I-9 data, tax forms, and onboarding documents are extracted as structured records and separate document blobs. These are delivered as a structured export package rather than migrated into Zoho Recruit's candidate record, because Zoho Recruit's standard ATS module is not an I-9 management system. The customer reimports these documents into their chosen HRIS or onboarding platform post-migration.

ApplicantStack email template content migrates as text into Zoho Recruit's Email Templates. Variable placeholders (candidate name, position title, etc.) are mapped to Zoho Recruit's template variable syntax. Automated trigger logic tied to the templates does not migrate; we deliver a written inventory of every automated sequence identifying its trigger, conditions, and actions for the customer to rebuild in Zoho Recruit's Workflow or Blueprints.

ApplicantStack candidate tags and job labels migrate as flat tag arrays into Zoho Recruit's Tags module. Identical tags on different objects are preserved per record. We run tag merge logic to consolidate any duplicate tags that result from ApplicantStack's flat naming convention.

ApplicantStack custom properties added to Candidates or Jobs beyond the standard schema are captured as key-value pairs. We map them to custom fields in Zoho Recruit, creating the destination custom candidate fields during the pre-migration setup phase. Field type mapping (text, number, date, picklist) is preserved as closely as possible given Zoho Recruit's field type constraints.

ApplicantStack's Reports builder is the migration data source — not a live API. We work with the customer's ApplicantStack admin to generate the necessary reports (Candidate Export, Job Export, Questionnaire Response Export, User Export) in advance of migration. We guide them through building a custom report template that covers all migration objects, or we parse their existing report exports and normalize the flat-file structure into Zoho Recruit's CSV import format.

Job board distribution settings (Indeed sponsored jobs, JobTarget, custom branded boards) are configuration data in ApplicantStack that do not carry forward to Zoho Recruit. The job posting content migrates; the distribution rules and sponsorship status do not. The customer republishes and redistributes jobs through Zoho Recruit's job board integration module post-migration.