Migrate from Recruit ATS by HR Cloud to Zoho Recruit

Recruit ATS Job records map directly to Zoho Recruit Job records. We extract title, description, location, department, employment type, and status (open/closed/archived). Custom request fields attached to the job posting migrate as Zoho Recruit custom fields on the Job module. Job owner maps from Recruit ATS Owner to Zoho Recruit Hiring Lead via email match. Status mapping preserves the open/closed/archived state rather than converting to a Zoho pipeline stage.

Recruit ATS Candidate records map to Zoho Recruit Candidate. We extract first name, last name, email, phone, work history, education, and source channel. Resume files migrate as binary attachments preserved with original filename and MIME type. Zoho Recruit requires Last Name as a mandatory field; candidates without a last name in Recruit ATS receive 'Not Provided' as a placeholder value per Zoho's import specification. Knock-out question responses migrate as custom fields on the Candidate record.

Recruit ATS Application records represent the junction between a Candidate and a Job, storing applied date, current stage, source channel, and rejection reason. Zoho Recruit does not use a standalone junction object; instead, Candidates are linked to Jobs through the hiring pipeline. We create the association by resolving the Candidate ID and Job ID at migration time, setting the candidate's pipeline stage to match the Recruit ATS application stage. The applied date and source channel migrate as fields on the Candidate record tied to that specific Job.

Recruit ATS Pipeline Stages are fully custom and ordered by ordinal position in the Kanban view. We extract stage names and their ordinal position during scoping. In Zoho Recruit, we configure the hiring pipeline with matching stage names and probabilities, preserving the Kanban column order. Stage IDs in Recruit ATS are system-generated and must be remapped; we produce a stage mapping table that your admin applies during Zoho pipeline setup.

Recruit ATS Tags are string labels applied to Candidates and Jobs. We export the full tag set and apply them identically in Zoho Recruit as Tag records. Multi-tag records migrate as arrays and expand to individual Tag assignments per Zoho's tag structure.

Standard custom fields on Candidate, Job, and Application records migrate as Zoho Recruit custom fields of equivalent type. Text fields map to Zoho Text, date fields to Date, picklist fields to Picklist, and checkbox fields to Checkbox. We pre-create the destination custom fields via Zoho Recruit's setup API before any data import begins.

Recruit ATS entity-type custom fields create cross-object links between Candidate-to-Candidate or Candidate-to-Job records. Zoho Recruit does not have a native entity-to-entity lookup field type, so we migrate these as custom fields storing the original Recruit ATS linked-record ID as a text string. Post-migration, your admin uses our re-linkage guide to reconnect records manually in Zoho Recruit using its lookup field capabilities. We flag these dependencies in the pre-flight audit and exclude them from automated import until schema is confirmed.

Resume files, cover letters, and uploaded documents attached to Candidates and Jobs migrate as binary attachments in Zoho Recruit. We preserve the original filename and MIME type. Attachments larger than 5 MB are chunked for Zoho's API upload limits. GDPR-aware data retention configuration from HR Cloud does not transfer; we recommend reviewing Zoho Recruit's data retention settings post-migration.

Notes attached to Candidates in Recruit ATS migrate as Zoho Recruit Notes on the Candidate record. We preserve the original author and timestamp as Note metadata. Thread structure (nested replies) does not transfer; all notes land as flat entries in the destination. If note threads are business-critical, we recommend PDF export of the thread view from Recruit ATS UI before the migration cutover.

Recruit ATS SMS interview invite sequences are stored as automation configurations, not as message records. The API does not expose sequence bodies or step definitions. We document each active SMS sequence in the automation registry with its trigger, steps, and message content so your team can rebuild using Zoho Recruit's Workflow automation or a third-party SMS tool integrated via Zoho's extension framework.

Recruit ATS automation rules and knock-out question configurations are not exposed via the public API. We cannot migrate them as structured data. During pre-flight, we audit every active rule and produce a written automation registry listing the trigger, conditions, actions, and recommended Zoho Recruit Blueprint or Workflow equivalent. Your admin uses this registry to rebuild in Zoho Recruit's workflow builder post-migration.

Interview scorecards and evaluation templates in Recruit ATS are not exposed via the public API. We do not migrate structured evaluation data. We recommend exporting scorecard responses as PDF exports from the Recruit ATS UI before migration as a manual workaround. Zoho Recruit supports evaluation forms on the Standard plan and above, which your admin can configure post-migration using the exported scorecard content as reference.