Migrate from Rippling to Recruit CRM & ATS

Rippling Workers in an ATS context (candidates created via Rippling's recruiting module) map to Recruit CRM Candidate records. The candidate's name, email, phone, resume content, and status from Rippling's applicant pipeline map to Recruit CRM's candidate_name, email, phone, resume_file, and status fields. We extract the candidate's source (referral, job board, direct) and preserve it in a custom field for reporting. Active Rippling job applications link to Candidate records via the Candidate-Job association table.

Rippling Job Openings map to Recruit CRM Job records. The job title, description, work location, and employment type (full-time, part-time, contract) transfer directly. Rippling's job status (open, filled, closed) maps to Recruit CRM's job status. We handle the pipeline order and stage names as Recruit CRM stage values configured during schema setup. Jobs must import before Candidate-Job associations.

Rippling Departments map to Recruit CRM Client records when the customer uses Rippling to track external client relationships (more common in staffing deployments). The department name becomes the client organization name, and the work location address populates the client address fields. If Rippling is used for internal hiring only (no external clients), we scope this mapping to internal organizational units and flag whether the customer needs a separate client structure built in Recruit CRM.

Rippling Work Locations with distinct addresses map to separate Client Location records in Recruit CRM. Multi-location staffing operations commonly have candidates assigned to different job site locations; we preserve each location's address, city, state, and country as distinct nested records under the parent Client. Location type (onsite, remote, hybrid) migrates as a picklist field on the location record.

Rippling Contacts created in the ATS context (hiring manager contacts, client contacts) map to Recruit CRM Contact records. The contact's name, email, phone, and title transfer directly. We resolve the Contact-Client relationship by matching the Rippling department or location to the corresponding Recruit CRM Client record. Contacts without a resolved Client parent are held in a reconciliation queue for the customer's admin to assign during cutover validation.

For staffing agencies using Recruit CRM's Deals to track placement agreements, Rippling Compensation Records (pay rates, salary bands) serve as the rate-reference data that populates Deal financial fields. The placement fee percentage, margin, and candidate pay rate transfer to Recruit CRM Deal records linked to the Job and Client. This mapping applies only if the customer is actively using Recruit CRM Deals for placement tracking; otherwise, compensation data is preserved as custom fields on the Candidate record.

Rippling Custom Objects with per-customer field schemas (certifications, skills matrices, equipment assignments) require schema export before any data move. We extract the Custom Object field definitions (API name, data type, required flag) via the Rippling Custom Objects API, then map each to either a Recruit CRM native custom field or a nested custom field structure on the equivalent Recruit CRM object. Recruit CRM's Custom Fields API supports text, number, date, picklist, and boolean types; formula fields and derived fields from Rippling require a documented manual rebuild in Recruit CRM's formula builder.

Rippling's effective-dated employment history (title changes, compensation changes, transfers) represents prior placement experience for candidates. We extract the employment timeline as a chronological set of notes with a timestamp header, each entry containing job title, company, dates, and key responsibilities, and attach them as time-stamped Notes on the Recruit CRM Candidate record. This preserves the work history narrative without requiring a native employment-history object in Recruit CRM.

PTO accruals and balance snapshots are HR-specific time-sensitive data that have no equivalent in Recruit CRM's ATS data model. We do not migrate PTO data to Recruit CRM. For customers who need PTO records for compliance or audit purposes, we recommend exporting the balance snapshot as a dated CSV for the customer's HR records and flagging that Recruit CRM is not an HRIS.

Employee documents stored in Rippling (offer letters, resumes, tax forms, certifications) migrate as Files attached to the corresponding Recruit CRM Candidate record. We export document metadata (file name, type, upload date) and, where Rippling's file storage is API-accessible, the binary file content. File attachments are associated to the Candidate via Recruit CRM's file upload API after the Candidate record exists in the destination.

Rippling's device inventory and MDM enrollment records are IT module data with no equivalent in Recruit CRM. We do not migrate device records. The customer's IT team manages device offboarding separately from the ATS migration.