Migrate from RippleHire to Crelate

RippleHire Jobs are the primary requisition object organizing the hiring pipeline. We map Jobs to Crelate Job records, preserving job title, description, job board posting status, and sourcing channel attribution. RippleHire's pipeline stages (screening, interview, offer, hire) map to Crelate's job pipeline stages if configured. Any custom fields on the Job record (department, cost-center, hiring-manager assignment) migrate as Crelate custom properties. Job status (open, paused, closed) transfers directly.

RippleHire Candidates (sourced, referred, and applied profiles) map to Crelate Contact records. We preserve contact details, email, phone, current stage in the RippleHire pipeline, stage-progression timestamps, and sourcing channel attribution. Any resume attached to the Candidate record migrates as a Crelate file linked to the Contact. RippleHire's Candidate ID is preserved in a custom field rh_candidate_id__c for reconciliation purposes.

RippleHire Referral records carry the referrer identity, referral status (pending, shortlisted, hired), reward eligibility, and any incentive payout milestone. Crelate has no native gamification object, so we create a structured Note on the Crelate Contact record containing the referrer name, referral status, reward eligibility flag, and payout stage. This preserves the referral context without requiring a custom object. If the referrer is not already a Contact in RippleHire, we create a minimal Contact record for them in Crelate to anchor the referral note.

RippleHire Offers map to Crelate Opportunity records. We map offer amount, currency, offer status (accepted, declined, pending), and candidate name to the Opportunity. RippleHire's maker-checker approval chain (who approved, at which stage, under which policy rule) migrates as date-stamped notes on the Crelate Opportunity, preserving the full approval audit trail. Offer letter attachments migrate as files linked to the Opportunity.

RippleHire Onboarding data (post-offer engagement, BGV status, appointment scheduling, day-one join details) maps to Crelate Task records attached to the relevant Contact or Opportunity. BGV completion status migrates as a custom field on the Contact. We do not migrate the full onboarding-day details if they live in a separate document; in that case, we attach the document as a file and create a summary Task record with the onboarding checklist status.

RippleHire Users (recruiters, hiring managers, admins) map to Crelate User records by email match. Role-based permissions migrate as Crelate role assignments; any RippleHire role without a direct Crelate equivalent is documented for the customer's admin to reconfigure post-migration. Inactive RippleHire users map to inactive Crelate Users.

RippleHire custom fields on Jobs and Candidates migrate to Crelate custom properties on Job and Contact. We map the field name, data type, and picklist values. Conditional-logic dependencies and cross-field validation rules from RippleHire are documented in the migration scope as configuration requirements for the customer's admin to rebuild in Crelate's custom forms editor. If a RippleHire picklist maps to a Crelate multi-select, we create the matching picklist values during schema setup.

RippleHire BGV records track verification status against Aadhaar and other India-specific checks. We carry the verification status (pending, in-progress, completed, failed) as a custom field on the Crelate Contact. Detailed BGV report documents export as file attachments on the Contact. Any BGV data tied to India-specific identifiers (Aadhaar numbers) is flagged during migration for the customer's compliance team to handle per data-governance policy; we do not transfer personally identifiable Aadhaar data unless explicitly scoped and approved.

RippleHire unifies referrals, vendor/agencies, and job board sources under a single sourcing view with per-candidate attribution. We preserve source attribution as a Crelate Tag on the Contact record. Vendor-specific pipeline stages that may exist in RippleHire but not in Crelate are documented for admin review; we do not create custom pipeline stages without explicit scope confirmation.

RippleHire maker-checker workflow configurations govern offer approvals and other approval gates. These are system-level workflow definitions that do not migrate. We map the outcome records (who approved, at which stage, under which policy rule, with what timestamp) as date-stamped notes on the relevant Crelate record (Offer becomes Opportunity, Onboarding becomes Task). The customer receives a written workflow inventory documenting every RippleHire approval gate and a recommended rebuild approach in Crelate's workflow tools.

Decline analysis in RippleHire is an aggregated reporting artifact summarizing offer-decline trends, not a transactional data object. We do not migrate reporting-layer artifacts. The customer receives a written note identifying the Decline Analysis report as a reporting-layer feature that should be rebuilt as a Crelate report or exported to a BI tool post-migration.

RippleHire shared dashboards for offer status, pipeline analytics, and decline insights are BI-layer artifacts tied to the platform's data warehouse. These do not migrate as data records. We deliver a written inventory of every RippleHire report and dashboard with its underlying data sources and recommended Crelate equivalent (built-in report or exported to a BI platform).