Migrate from RippleHire to Zoho Recruit

RippleHire Jobs map directly to Zoho Recruit Job Openings. Job title, description, department, location, employment type, and job board posting status carry across. Pipeline stage assignments in RippleHire map to Zoho Recruit's Job Opening status (Open, On Hold, Closed, Draft). Sourcing channel attribution at the job level migrates as custom fields. RippleHire job board posting records map to Zoho's job distribution settings with the same board-specific status preserved as a custom picklist field.

RippleHire Candidates map to Zoho Recruit Candidates with contact fields (name, email, phone, current company, current title, LinkedIn URL) carried across. RippleHire's candidate status history and stage progression timestamps migrate as Zoho Recruit interview and activity records. Zoho Recruit requires a Last Name value on every Candidate record; RippleHire candidates without a populated last name receive a placeholder value of 'Not Provided' flagged for manual review post-migration. RippleHire's sourcing channel attribution (referral, vendor, job board, direct) maps to Zoho's Source picklist.

RippleHire Referral records map to Zoho Recruit Employee Referral records with referrer name, candidate name, job applied to, and referral status preserved. RippleHire's gamified reward schema (reward eligibility status, incentive payout tracking, referral stage in the reward cycle) cannot map directly to Zoho's standard Employee Referral module because Zoho lacks a native gamification layer. We carry reward eligibility and status flags as custom fields on the Zoho Referral record and flag all incentive-specific data for manual reconciliation against the customer's current reward payout records.

RippleHire Offers map to Zoho Recruit Job Offers with offer details (candidate, job, CTC, components, joining date, offer letter status) preserved. RippleHire's multi-level maker-checker approval chains capture who approved at each stage and under which policy rule; these outcomes carry as date-stamped notes on the Zoho Offer record (e.g., 'Approval by [Name] on [Date] per [Policy Rule]'). The multi-level approval logic itself requires rebuilding in Zoho Recruit's Blueprint or workflow automation tool post-migration.

RippleHire Onboarding tracks post-offer engagement, BGV status, appointment scheduling, and day-one task completion as a unified module. Zoho Recruit Onboarding Checklist records are structured as individual task items rather than a single onboarding record. We split RippleHire onboarding data into separate Onboarding Checklist items in Zoho Recruit with task name, assigned owner, due date, and completion status preserved. Any RippleHire POFU (post-offer follow-up) engagement records that do not fit the task-item model carry as Candidate notes in Zoho Recruit.

RippleHire BGV records track Aadhaar-based and other India-specific verification status tied to Candidates. Verification status flags (initiated, in-progress, verified, rejected) and verification date migrate as custom fields on the Zoho Recruit Candidate record. Detailed BGV report documents export as file attachments and attach to the corresponding Candidate record in Zoho Recruit. The customer should confirm that their chosen BGV vendor can receive verification data via Zoho Recruit's integration or manual re-entry post-migration.

RippleHire Users (recruiters, hiring managers, admins) with role-based access map to Zoho Recruit Users. We resolve by email address as the dedupe key. RippleHire role assignments (recruiter, hiring manager, admin) map to Zoho Recruit profile permissions. Any RippleHire User without a matching Zoho Recruit account goes to a reconciliation queue; Zoho Recruit requires each User to have an active Zoho account before record assignment during migration. If the customer is migrating from a RippleHire agency deployment, hiring manager accounts may require separate provisioning.

RippleHire custom fields on Jobs and Candidates migrate as Zoho Recruit custom fields in the corresponding modules. We create each custom field in Zoho with the appropriate field type (text, picklist, multi-select picklist, date, numeric) matched to the RippleHire field definition. RippleHire picklist values and conditional-logic dependencies are noted in the migration inventory; Zoho Recruit supports conditional field visibility and required-field rules per layout in the Professional and Enterprise tiers. Any cross-field formula or auto-calculation logic from RippleHire cannot migrate as active formulas and requires rebuilding in Zoho's formula fields (Professional and above) or as manual workflow logic.

RippleHire unifies referrals, agency/vendor sourcing, and job board channels under a single sourcing attribution view at the candidate level. Source attribution migrates to Zoho Recruit's Source picklist on the Candidate record, with RippleHire's sub-channel values (e.g., LinkedIn Recruiter vs. LinkedIn Free Job Posting) carried as a custom candidate field if Zoho's standard Source picklist cannot accommodate the full taxonomy. Vendor-specific pipeline stages in RippleHire may require scoping adjustment in Zoho Recruit, as Zoho uses a single pipeline view per job rather than vendor-specific stage branches.

RippleHire maker-checker workflow definitions governing offer approvals are system-level workflow logic that do not migrate as executable automation. The approval-chain outcome records (who approved what stage, when, under which policy rule) migrate as date-stamped notes on the corresponding Zoho Recruit Offer record. We deliver a written inventory of every RippleHire maker-checker workflow definition with its stages, approval conditions (role, location, CTC thresholds), and recommended Zoho Recruit Blueprint equivalent. The customer's Zoho admin rebuilds the automation logic in Blueprint post-migration.

RippleHire interview records (scheduled date, time, interviewer, interview type, feedback status) map to Zoho Recruit Interview records linked to the Candidate and Job Opening. RippleHire notes attached to candidates, jobs, or offers migrate as Zoho Recruit Notes linked to the corresponding record. RippleHire tasks (to-do items on candidates or jobs) migrate as Zoho Recruit Tasks with owner, due date, priority, and completion status preserved. Interview feedback forms from RippleHire map to Zoho's Interview Feedback form if the customer's Zoho tier supports it (Professional and above); otherwise they carry as Notes.

For RippleHire deployments used by staffing or recruitment agencies (a common configuration in RippleHire's India and SEA market), the Clients and Contacts module maps directly to Zoho Recruit's Clients and Contacts modules. Client name, contact name, email, phone, and associated job assignments carry across. Any active placements or assignment records tied to Clients carry as Job Openings with a client association in Zoho. This mapping is conditional on whether the source RippleHire account includes the agency module; standard enterprise ATS-only deployments may not have this object.

RippleHire file attachments (resumes, offer letters, BGV documents, certificates, signed agreements) migrate as Zoho Recruit attachments linked to their parent records. Resume files attach to the Candidate record; offer letter documents attach to the Job Offer; BGV reports attach to the Candidate. We use Zoho Recruit's attachment upload mechanism during the import phase. Large file attachments (BGV reports exceeding standard file size limits) may require chunked upload or separate file delivery. The customer should confirm any file naming conventions or PII handling requirements for attachments containing candidate personal data.