Migrate from RECRU to Zoho Recruit

RECRU Candidate records include parsed CV data (name, email, phone, skills, work history), AI-generated match scores, application history, and custom properties. We map standard fields directly. Zoho Recruit mandates a Last Name value on every Candidate record; any RECRU record where last name is absent or compound (e.g., single 'Smith Jones' name field) must be pre-enriched before import. We detect these gaps during scoping and either split the name or flag them for the customer's RECRU admin to resolve before export.

RECRU Job requisitions carry title, description, department, location, salary range, and hiring pipeline stages. We map these to Zoho Recruit Job Opening fields directly. Pipeline stage order from RECRU maps to Zoho Hiring Pipeline stages, and we create the Zoho pipeline structure before Job Opening import if the customer has more than one active pipeline.

RECRU User accounts (name, email, role, team assignment) map to Zoho Recruit Users. Zoho Recruit requires that migrating users do not already have a separate Zoho Recruit account; we check for email collisions and flag any duplicate Zoho accounts that must be closed before import. We also require at least two users in the destination account before migration can begin; if the customer has only one, we document this and the migration waits on provisioning.

Tenant-configured RECRU custom properties migrate as key-value pairs. We extract the field name and data type from RECRU and create equivalent Zoho Recruit custom fields before data import, falling back to text fields for unsupported types. Zoho Standard allows 50 custom fields per module; Enterprise allows 300. If the RECRU tenant exceeds this limit on a given module, we discuss field prioritization with the customer before migration.

Tags applied to candidates in RECRU migrate as flat label arrays attached to the Candidate record in Zoho Recruit. Tags do not map to Zoho's Topics object because Topics in Zoho are primarily used for content and knowledge-base classification, not candidate segmentation.

RECRU workflow rules are JSON-backed in the database with multi-step conditional branching that has no direct Zoho Recruit equivalent. We export the full rule graph and document each rule's trigger, conditions, and actions in a written inventory delivered to the customer. Zoho Workflow Rules (5 per module on Standard, 50 on Enterprise) use a trigger-action model; Blueprint adds process diagramming. Multi-step RECRU branches may require decomposition into multiple Zoho rules. We do not implement the rebuild; the customer's admin handles this post-migration.

Email threads and message logs attached to RECRU candidate records migrate as flattened activity entries in Zoho Recruit. The original thread structure is not preserved; each message becomes a separate Task record with the full message body. The most recent message is marked as the primary note. We preserve sender, recipient, timestamp, and thread reference ID for reconciliation.

Interview events in RECRU carry date, interviewer, duration, and outcome. These map to Zoho Recruit Interview records linked to the Candidate and Job Opening. If the interview was scheduled via an external calendar integration in RECRU, we note this but do not migrate calendar events directly; the interviewer relationship maps to a Zoho User lookup.

Evaluation scorecards submitted by RECRU interviewers migrate as JSON objects attached to the candidate record. Zoho Recruit's native Assessment feature stores structured evaluations; scorecards that do not conform to Zoho's assessment schema land as custom fields on the Candidate record with the full JSON preserved for admin review.

Pipeline stage names and order from RECRU migrate to Zoho Recruit Hiring Pipeline stages. If the destination Zoho account uses a predefined pipeline structure, we map RECRU stages to the closest equivalent stage name and flag any stages that have no clear Zoho analog for the customer to decide on naming.

RECRU assigns AI-generated match scores as uncalibrated float values tied to the candidate's fit for a role. These have no fixed range and are RECRU-proprietary. We preserve them as a custom float field on the Candidate record in Zoho Recruit but include a data-quality note that they are not comparable to Zia AI scores or any scoring system in the destination platform.

If RECRU tenant uses a client-facing workflow with client records, these map to Zoho Recruit Client records. Client records in Zoho carry company name, contact details, and portal access settings. We resolve the client-contact relationship to the corresponding Zoho User if the client has an existing Zoho account.