Migrate from Rippling to Zoho Recruit

Rippling Worker records map to Zoho Recruit Candidates. Not every Rippling Worker is a Candidate — the migration scope includes only workers who applied through Rippling's ATS module or were imported as candidates. We filter the Rippling Worker export to records with a sourcing date and an ATS-related status (Applied, Screened, Interviewed, Hired). Name, email, phone, address, and employment eligibility fields map to Zoho Recruit's standard Candidate fields. Rippling's worker photo and avatar data do not transfer; we flag this as a gap for manual re-upload if needed.

Rippling Job records (titles, descriptions, department assignments, pay ranges) map to Zoho Recruit Job Openings. The Rippling Job status (Open, On Hold, Closed, Draft) maps to Zoho Recruit Opening Status. Department assignment from Rippling becomes a custom picklist field or Lookup to a Zoho Recruit Department if configured. Job board distribution settings from Rippling (where jobs were posted) map as source attribution tags in Zoho Recruit.

Rippling's ATS pipeline stages (Screening, Interview, Offer, etc.) map to Zoho Recruit's candidate pipeline stages. Zoho Recruit Standard edition uses a fixed pipeline; Professional and Enterprise editions allow custom stage names. We create Zoho Recruit custom stages matching Rippling's pipeline configuration before candidate migration begins. Stage probabilities from Rippling do not transfer as Zoho Recruit does not expose stage probability on the candidate pipeline object.

Rippling candidate applications (the record of a Worker applying to a Job) map to Zoho Recruit Candidates linked to the corresponding Job Opening via Zoho Recruit's Candidate-to-Job Opening association. The application date, source channel, and referral information migrate as custom fields on the Candidate record. Multiple applications from the same candidate in Rippling (re-hires or internal mobility) become separate Candidate-Job Opening associations in Zoho Recruit.

Rippling interview records (scheduled interviews, interviewer assignments, feedback) map to Zoho Recruit Interview records linked to the Candidate. Interview feedback scores and notes from Rippling map to Zoho Recruit Interview Feedback Form responses. If Rippling stores interview notes as free-text fields, we migrate them to Zoho Recruit's Notes module linked to the Candidate. Audio or video interview recordings stored in Rippling are exported as file references (not transcoded); the customer downloads and re-uploads to Zoho Recruit's document library.

Rippling Departments map to Zoho Recruit's Department module (available in all paid editions). We migrate the department hierarchy (parent-child relationships) as Zoho Recruit Department records with parent-department lookups. This supports reporting by department on hiring activity without requiring custom rollup fields.

Rippling Work Locations (office sites, remote designations, jurisdictions) map as custom fields on Zoho Recruit Job Openings if the customer uses location as a hiring criterion. For staffing agencies using Zoho Recruit's Client module, Work Locations may map to Client address records if the agency's placement model ties candidates to client sites. We determine the correct mapping during scoping based on the customer's Zoho Recruit configuration.

Rippling tracks employment history — prior titles, compensation changes, transfers — with effective dates. For ATS migration, we extract the most recent prior employment record (previous employer, title, dates) and store it as a custom text block on the Zoho Recruit Candidate record. Full employment timeline is not migrated as Zoho Recruit's Candidate object does not support a linked Employment History sub-object. The customer's HR team retains the full history in Rippling export if needed for compliance.

Rippling compensation records (salary, bonus, equity) map to Zoho Recruit custom fields on the Candidate record if the customer requires this data in the ATS. We create custom currency or number fields (Expected Salary, Current Salary, Notice Period) in Zoho Recruit Professional or Enterprise to carry compensation expectations. Active payroll compensation data does not migrate — this belongs in a payroll system, not an ATS.

PTO accruals and balances are HR-timekeeping data, not recruiting data. Rippling PTO records do not map to Zoho Recruit objects. We do not migrate PTO data as part of an ATS extraction migration. If the customer also moves to Zoho People for HR, PTO migrates separately in a distinct HRMS migration engagement.

Benefit plan assignments, carrier details, and enrollment records are HR-benefits data outside Zoho Recruit's ATS scope. We do not migrate benefits enrollment as part of a Rippling-to-Zoho-Recruit migration. Active enrollment is documented in a supplemental HR data export for the customer's records.

Rippling Custom Objects used to store ATS-relevant structured data — such as certifications, background check results, drug screening outcomes, or security clearance levels — map to Zoho Recruit custom modules. We export the Rippling Custom Object schema (field names, types, required flags) during discovery, create equivalent custom modules and fields in Zoho Recruit before migration, and map record data accordingly. Zoho Recruit Standard edition limits custom fields to 50 per module; Professional allows 300 per module. Large custom object schemas may require Enterprise tier or field consolidation.

Rippling employee documents — offer letters, signed contracts, tax forms — that are associated with candidate records migrate as Zoho Recruit attachments on the corresponding Candidate. We export document metadata and links from Rippling and attach the files to the Zoho Recruit Candidate record via the Documents module. File content depends on whether Rippling's file storage is API-accessible; we request read access during discovery. If documents are stored in a Rippling-specific format not exportable, we document the file inventory for manual re-upload.