Migrate from Rival Recruit to Zoho Recruit

Rival Recruit candidate profiles (name, email, phone, work history, resume attachment, source attribution, stage status) map directly to Zoho Recruit Candidates. The candidate_id in Rival becomes the Zoho CandidateID. Resume files are extracted as binary attachments and reattached to the Zoho Candidate record. Stage names are mapped to Zoho Hiring Pipeline stages during configuration. Custom fields on candidates are discovered via API schema audit before migration and mapped explicitly.

Rival Recruit positions (title, department, location, hiring manager, open/closed status, associated pipeline stages) map to Zoho Recruit Job Openings. The position hierarchy and approval workflow state migrate as job opening metadata. Zoho requires at least one Job Opening to exist before candidate import can reference it. We create Job Openings first in dependency order and resolve the job opening reference on candidate records during import.

Rival Workflow onboarding journeys tied to new hires are mapped to Zoho Recruit's Candidate onboarding section. The Onboarding Web Service Guide (v2020.2.1) documents a subset of endpoints; we perform schema discovery against the customer's live environment to enumerate active onboarding fields. Active onboarding journeys with pending start dates receive priority sequencing in the cutover to prevent hiring disruption. Zoho People onboarding for post-hire employee setup is documented separately for the customer's admin.

Rival Recruit employee records (personal info, job title, department, manager, start date, employment status) map to Zoho People as a separate integration scope. We extract employee records and map them to Zoho People Employee module. Effective-dated employment history migrates with timestamps preserved. The employee record references a Manager lookup that is resolved against the Users table.

Both Rival Recruit and Zoho Recruit support custom fields on Candidates and Job Openings, but the set of active custom fields is entirely customer-specific. We perform a pre-migration schema audit via the Rival Recruit API to enumerate every active custom field name, type, and required status before generating the mapping table. We then pre-create matching custom fields in Zoho Recruit (via Setup > Fields > Custom Fields) before candidate and job opening import begins.

Rival platform users (name, email, role, team assignment) map to Zoho Recruit Users. We resolve by email match. Zoho requires that any user being imported does not already have a separate Zoho Recruit account; those users must close their existing accounts before migration import. Users without a matching Zoho account go to a reconciliation queue for the customer's admin to provision. Owner assignment on Candidate and Job Opening records resolves via the User mapping.

Tags applied to candidates in Rival Recruit for segmentation and sourcing campaigns are extracted as a flat lookup table (CandidateID, TagName). Tags are re-created in Zoho Recruit and re-applied to Candidate records during import. If the customer uses a high volume of tags, we assess whether to migrate all or a top-frequency subset based on business impact.

Uploaded resumes, cover letters, offer letters, and compliance documents stored against candidate and employee records in Rival Recruit are extracted as binary files separately from metadata. Files are remapped to Zoho Recruit Attachments linked to the corresponding Candidate or Job Opening record. We handle file naming collisions by prefixing with the source record ID.

Rival Recruit interview events (date, time, interviewer, candidate, position) stored in the scheduling module are mapped to Zoho Recruit Events. The calendar relationships are preserved, but interview scorecards and evaluation forms require manual rebuild in Zoho Recruit as they are not exported as data records.

Branded career site content, job board distributions, and employee testimonial pages are configurable assets in Rival Recruit rather than transactional records. We export the site configuration and content block structure as a written documentation package. The customer's admin rebuilds the Careers Page in Zoho Recruit using the provided configuration summary. We do not migrate career site code or hosted assets.

Configured HR workflows in Rival Recruit (onboarding, offboarding, internal mobility) defining journeys with steps, assignees, and conditions are exported as JSON blueprints and written documentation. We do not migrate workflows as executable code because Rival and Zoho use fundamentally different workflow engines. The Workflow inventory document maps each Rival workflow step to a recommended Zoho Recruit Workflow Rule configuration for the customer's admin to rebuild.

Stage transition history (candidate moved from Applied to Phone Screen to Onsite) stored against candidate records in Rival is mapped to Zoho Recruit Candidate Activity Log entries. Each stage change is logged as a timestamped Activity with the stage name preserved. The full stage history provides audit continuity for compliance and reporting in the destination system.