Migrate from isolved to Recruit CRM & ATS

isolved ApplicantPro candidate records map directly to Recruit CRM Candidate records. Core fields (name, email, phone, resume) migrate via CSV import with field mapping from ApplicantPro export columns to Recruit CRM's documented import fields. We extract resume files as attachments and associate them with the Candidate record. Any custom candidate properties in ApplicantPro (source channel, referral tag, rating) map to Recruit CRM custom fields or tags. Employment history and education nested within ApplicantPro migrate as structured line items on the Candidate profile.

isolved job postings and requisitions map to Recruit CRM Job Openings. The Job Title, Job Description, and Employment Type fields migrate directly. We map the isolved job status (Open, Closed, On Hold, Draft) to Recruit CRM's Job Opening status field. Department and Work Location from isolved map to Recruit CRM's Department and Location fields. Salary range fields from isolved (if populated) map to the salary custom fields in Recruit CRM.

isolved allows candidates to be associated with multiple job requisitions. Recruit CRM associates candidates with Job Openings through an application record. We preserve the many-to-many relationship by creating an Application record in Recruit CRM for each isolved candidate-to-job association. Candidate pools or talent communities in isolved migrate to Recruit CRM Lists or Tags, which the customer chooses during scoping.

If isolved stores client or company data related to recruiting placements (particularly for staffing agencies that use isolved for both HR and client tracking), those records map to Recruit CRM Company. The Company Name, Address, and Industry fields migrate directly. We map any contact person records in isolved to Recruit CRM Contacts linked to the Company.

Organizations that used isolved ApplicantPro to track both external candidates and internal employees who applied for roles need to decide whether historical employee-applicants migrate as Candidates. We flag this record type during scoping. If the customer chooses to migrate, we map the Employee record's contact information and application history to a Candidate profile in Recruit CRM, excluding payroll and HR fields that do not belong in the ATS.

Candidate communication logs, interview notes, and engagement history in isolved ApplicantPro migrate to Recruit CRM's Activity and Note records linked to the Candidate. Email threads, interview scheduling records, and interview feedback migrate as structured activity entries with timestamps preserved. We map the engagement type (email, call, interview, note) to the corresponding Recruit CRM activity type. Activity ordering is preserved by setting the activity date to the original isolved timestamp.

Resume files, cover letters, offer letters, and supporting attachments stored in isolved ApplicantPro migrate as document attachments on the corresponding Candidate record in Recruit CRM. We export document blobs with metadata (file name, upload date, file type) and import via Recruit CRM's document attachment interface. Large document volumes may require chunking to stay within import limits.

isolved stores employer-defined classification codes (Job Codes, Work Locations, Pay Types) as picklists that apply across the HCM suite. Recruit CRM uses agency-level custom fields instead. We extract the full picklist table from isolved and produce a mapping matrix that links each isolved picklist value to either a Recruit CRM custom field value or a tag. The customer's admin selects the target strategy during scoping.

isolved ApplicantPro workflows (candidate routing, status change triggers, notification rules) do not migrate as executable code to Recruit CRM because the automation models differ. We deliver a written inventory of every active ApplicantPro workflow with its trigger, conditions, actions, and recommended Recruit CRM equivalent. The customer's admin rebuilds these in Recruit CRM's automation builder post-migration.

These isolved HCM core objects have no equivalent in Recruit CRM's ATS/CRM data model. Payroll registers, tax withholdings, benefit elections, and time-off accruals are outside Recruit CRM's object schema and are excluded from migration scope. If the customer also migrates to a separate HRMS or payroll platform (Workday, Rippling, Paylocity), those objects migrate in a parallel engagement under the appropriate HRMS category. We flag the exclusion explicitly during scoping so there is no ambiguity about what does and does not move.