Migrate from Zoho Recruit to Crelate

Zoho Recruit Candidates map to Crelate Person records. The required Name field on Crelate Person is satisfied from Zoho First Name and Last Name fields. Email, phone, skills, current employer, and current title map to Crelate Person fields directly. Zoho Candidate Status (Active, Passive, Blocklisted) maps to a Crelate custom Person status field. Custom fields created in Zoho Professional or Enterprise are pre-created as Crelate Person custom fields before migration. Resume files (stored in /Attachments/Candidates/[id]/) are associated as Crelate document records linked to the parent Person record by Crelate's Id lookup pattern.

Zoho Job Openings map to Crelate Jobs. The required Name field on Crelate Job is satisfied from Zoho Job Title. Zoho job status (Open, On Hold, Closed, Cancelled) maps to Crelate Job status. Zoho pipeline stages map to Crelate pipeline stages or tags. Job Openings in Zoho that reference a Client (agency context) map to a Crelate Account reference using the Client Name as the Account lookup value. Active job count limits by Zoho edition (1 on Free, 100 on Standard, 250 on Professional, 750 on Enterprise) are a source-system constraint only; Crelate has no stated active job ceiling.

Zoho Recruit Clients (agency-specific module holding external hiring-company records) map to Crelate Accounts. The required Name field on Crelate Account is satisfied from Zoho Client Name. Client phone, website, address, and industry fields map to equivalent Crelate Account fields. Client-specific custom fields from Zoho Professional or Enterprise are pre-created in Crelate before migration. In Crelate, Accounts serve as the parent for both Persons (contacts at the client) and Jobs (requisitions at the client), so the Account is migrated before any related Job or Person records to satisfy the lookup dependency.

Zoho Recruit Contacts (hiring-manager or candidate-contact records distinct from Candidates) map to Crelate Person records. If a Contact in Zoho is also a Candidate (a common pattern in agency workflows), we evaluate whether to create one Crelate Person with multiple roles or two separate Person records based on the customer's preference. Lookup relationships from Zoho Contacts to Clients map to Crelate Account references. Contact title, email, phone, and address fields migrate directly.

Zoho Recruit User records map to Crelate Person records with an internal owner or assignee role. Zoho's 2,000-record user import ceiling is flagged at discovery. For accounts with fewer than 2,000 users, we migrate Users directly as Crelate Persons. For accounts exceeding the ceiling, we migrate primary owner records (the recruiter users actively assigning work) first as Crelate Persons, and historical assignee references as a Person association rather than a standalone User record, preserving the attribution chain for placements and activity history.

Zoho Recruit Interviews (scheduled time, type, interviewer, feedback) map to Crelate Activity records with an activity type discriminator. Interview-to-candidate associations migrate as Crelate Activity linked to the Person record via Crelate's lookup pattern (Person Id, FirstName, LastName). Interview feedback, rating, and interviewer name from Zoho migrate as custom Activity fields. Scheduled time preserves as the Activity start time. Zoho's interview type field (Phone Screen, Technical, Onsite, etc.) maps to a Crelate Activity category or tag.

Zoho Recruit Notes (attached to Candidates, Job Openings, Clients, and Contacts) map to Crelate Note records. The required Body field on Crelate Note is satisfied from Zoho Note content. Rich-text notes in Zoho preserve as HTML in Crelate if the destination supports it; plain-text notes migrate as-is. Notes are associated to the parent Crelate record (Person, Job, or Account) using Crelate's parent record lookup. Note timestamps migrate as the Crelate Note creation date for audit continuity.

Zoho Recruit Tasks, Events, and Call logs map to Crelate Activity records with type discriminators. Call logs with duration, disposition, and recording URL migrate as Activity records with a call category. Events (interviews, client meetings) migrate with StartDateTime and EndDateTime preserved. Task assignment migrates by resolving Zoho Owner references to Crelate Person records. Zoho's Free edition excludes Tasks and Events; we confirm the source account's edition during discovery and only migrate activity modules present in the source.

Zoho Recruit attachments require strict folder hierarchy reconstruction before import: /Attachments/Candidates/[candidate_id]/, /Attachments/JobOpenings/[job_id]/. We extract attachments from the Zoho export, verify the folder structure matches this pattern, and re-associate each file to its Crelate record by filename match and parent record Id. Zoho's silent disassociation (orphan attachments when folder hierarchy is not preserved) is a known failure mode; we prevent it by reconstructing the tree during pre-flight. Resume files are associated as Crelate document records linked to the parent Person record.

Zoho Recruit Campaigns (sourcing initiatives linked to job boards or job openings) map to Crelate Activity records with a sourcing campaign category or tag. Campaign name, start date, and associated Job Openings migrate. Job board posting history attached to the Campaign in Zoho is documented as a Crelate Activity note rather than a native job board integration record, since Crelate handles job distribution through its own integrations. Custom fields on Zoho Campaigns require pre-creation in Crelate before migration.

Zoho Recruit Assessment results (attached to Candidates) migrate as Crelate Activity records with an assessment category, or as custom fields on the Person record if the assessment has a single summary score. The assessment itself (questions, scoring rubrics, assessment type configuration) cannot be migrated as code and may require manual recreation in Crelate depending on whether Crelate's talent assessment integrations cover the same assessment vendor. We document the assessment type and score for each Candidate during migration so the customer's team can reattach assessment context if needed.

Zoho Recruit custom fields (available in Professional and Enterprise editions; not available in Free or Standard) are pre-created in Crelate before any record data imports. We inspect the source account's edition during discovery to confirm which modules have custom fields. Field types are mapped: Zoho Picklist maps to Crelate picklist or tag; Zoho Multi-select Picklist maps to Crelate multi-select or tag; Zoho Lookup fields (which require Professional or Enterprise) map to Crelate Person, Account, or Job reference fields. Formula fields and auto-number fields require logic recreation in Crelate's formula system.

Zoho Recruit Workflow rules, Blueprint automation, and assignment rules are configuration rather than record data. They do not migrate to Crelate because the automation models are structurally incompatible. We deliver a written inventory of every active Zoho Workflow and Blueprint with its trigger, conditions, actions, and a Crelate equivalent recommendation (manual rebuild guidance). The agency's admin uses this inventory to recreate automations in Crelate Settings post-migration. This is standard scope: we do not rebuild workflows as part of the migration engagement.

Zoho Recruit career site configuration (templates, localized pages, job board posting settings, candidate web forms) is platform configuration, not record data. We do not migrate this. Published job listings themselves are captured as Job records in Crelate, and the agency reconfigures the Crelate-hosted career site and job board integrations independently. We document the list of active Zoho job board integrations during discovery so the agency admin can re-enable equivalent integrations in Crelate.