Migrate from RippleHire to Recruit CRM & ATS

RippleHire Jobs map directly to Recruit CRM Job records. We preserve job title, description, department, location, status, and any job-board posting attribution as sourcing channel metadata. Pipeline stages from RippleHire map to Recruit CRM's stage configuration. If RippleHire stores hiring manager or recruiter owner on the Job, we resolve by email to a Recruit CRM User and set the Owner field accordingly.

RippleHire Candidates are the primary record type and map directly to Recruit CRM Candidates. We preserve full contact details, current status, stage progression timestamps, source attribution (referral, job board, vendor, direct), and any custom fields configured per hiring workflow. Sourcing channel attribution is stored as a custom field or note in Recruit CRM since RippleHire's unified sourcing view does not map to a native Recruit CRM field.

RippleHire Referral records carry referrer identity, referral status, and reward eligibility as part of the gamified engine. Recruit CRM does not have a native gamified referral schema. We split the referral record: the referred Candidate moves to the Candidate object, the referrer identity moves as a custom field or related contact record, and reward eligibility and incentive payout status flag as custom fields on the Candidate. Any gamified reward-specific data that cannot map directly is flagged for manual reconciliation post-migration.

RippleHire Offer records track offer letter content, multi-level maker-checker approval outcomes, and acceptance or decline status. Recruit CRM stores offer data as part of the Candidate or Job record or as a custom object. We map offer status, salary, start date, and approval outcome as custom fields. The maker-checker approval chain (who approved, at which stage, under which policy rule) carries as a date-stamped notes field rather than a native approval record. Multi-level approval logic is flagged as a workflow rebuild item in Recruit CRM's automation engine.

RippleHire Users (recruiters, hiring managers, admins) map to Recruit CRM Users by email match. Role-based access from RippleHire maps to Recruit CRM role assignments. Any RippleHire User referenced on a record but not found in Recruit CRM goes to a reconciliation queue for the customer's admin to provision before record import resumes.

RippleHire custom fields on Jobs and Candidates map to Recruit CRM custom fields. We recreate picklist values, conditional logic dependencies, and field-level visibility as part of the destination schema configuration before migration begins. Any conditional-logic dependencies that cannot map to Recruit CRM's custom field engine are flagged for admin review.

RippleHire BGV records track Aadhaar verification status and other India-specific checks tied to Candidates. We map verification status flags to custom fields on the Recruit CRM Candidate record. Detailed BGV report documents export as attachments and are linked to the Candidate record. Full BGV workflow tracking (steps, dates, outcome) carries as notes or a BGV-specific custom object if the customer configures one in Recruit CRM.

RippleHire Onboarding records include post-offer engagement tracking (POFU), appointment scheduling, and task completion status. We map onboarding task completion and status flags to Recruit CRM Tasks or to custom fields on the Candidate record. Full day-one details that live in a downstream HRIS do not migrate since RippleHire Onboarding is a separate module from the hiring ATS. We flag any post-offer engagement data that requires manual follow-up in Recruit CRM.

RippleHire unifies referrals, vendor or agency sources, and job board sources under a single sourcing view. We preserve source attribution at the candidate level as a custom field in Recruit CRM. Vendor-specific pipeline stages that are RippleHire-specific do not map directly and are noted for the admin to standardize post-migration. The sourcing attribution is valuable for reporting and is preserved without being tied to a native object structure in Recruit CRM.

RippleHire maker-checker workflow configurations govern offer approvals and other approval gates. These are system-level workflow definitions that we do not migrate as code. We audit and document every active RippleHire workflow configuration including its trigger, conditions, stages, approver chain, and actions, and deliver a written inventory that maps each RippleHire workflow to a recommended Recruit CRM automation or manual process. The customer rebuilds in Recruit CRM's automation engine post-migration.