Migrate from isolved to Zoho Recruit

isolved ApplicantPro candidate applications map to Zoho Recruit Candidate records. The Candidate First Name, Last Name, Email, Phone, and Source fields migrate directly. Any isolved custom candidate properties (skills, certifications, availability flags) migrate as Zoho Recruit custom fields created via Setup > Customization > Modules before import. Last Name is a mandatory field in Zoho Recruit; records without a last name in isolved are flagged with a 'not provided' value per Zoho's migration documentation.

isolved ApplicantPro job postings map to Zoho Recruit Job Opening records. The posting title, description (HTML), job board distribution settings, and employment type (full-time, part-time, contract) migrate directly. Status mapping: isolved Active/Closed maps to Zoho Recruit Open/Closed. Job Openings must exist in Zoho Recruit before Candidates can be associated via the Candidates tab import.

isolved employer-defined Job Codes are a defined picklist in the source system with no direct Zoho Recruit equivalent. We export the full isolved Job Code table during discovery and create a corresponding picklist field (e.g., Job Classification) on the Job Opening module in Zoho Recruit. Each isolved Job Code value is entered as a picklist option before any Job Opening import runs, preventing null or mismatched classification codes on migrated records.

isolved Work Locations drive tax withholding and benefit eligibility rules and are stored as a defined list tied to legal work sites. Zoho Recruit has a Location field on Job Opening and a City/State/Zip structure on Candidates. We create a picklist field on Job Opening capturing the isolved Work Location name and map the physical address components to Zoho Recruit's standard address fields on Candidate records.

isolved Pay Type (Hourly, Salaried, Exempt, Non-Exempt) is an employer-defined list used for payroll classification. Zoho Recruit does not have a native payroll classification field. We create a custom picklist field (Employment Classification) on Candidate and populate it from the isolved Pay Type value during candidate import. This field is informational for the recruiting team; Zoho Recruit does not process payroll.

isolved ApplicantPro application submissions (candidate applied to a job posting) map to Zoho Recruit Candidate records linked to the corresponding Job Opening via the Candidates tab. Application status in isolved (Applied, Screening, Interview, Offer, Hired, Rejected) maps to Zoho Recruit Candidate status values configurable per hiring pipeline.

isolved ApplicantPro pending workflow transactions (in-flight candidate status changes, offer letters in progress) are stateful records that do not auto-close on export. We export pending transactions as a separate CSV and load them into a Zoho Recruit custom module (e.g., Pending Actions) or attach them as Notes to the relevant Candidate record, flagging them for recruiter follow-up post-migration.

isolved ApplicantPro stored attachments (resumes, cover letters, assessment results) migrate to Zoho Recruit Candidate Attachments via the attachment import option in Zoho's Data Migration tool. We note that Zoho Recruit's attachment limit and file size constraints apply; resume parsing in Zoho Recruit extracts fields from uploaded documents automatically after migration.

isolved ApplicantPro recruiter users map to Zoho Recruit Users by email match. Zoho Recruit's Data Migration documentation specifies that users with an existing separate Zoho Recruit account cannot be imported until that account is closed; we flag any duplicate email matches during discovery for admin resolution before migration runs.

isolved ApplicantPro custom candidate properties (skills, certifications, preferred locations, salary expectations, referral sources) that have no Zoho Recruit native equivalent are migrated as custom fields created via the Layout Editor before import. Field types are mapped: text properties to Text fields, date properties to Date fields, multi-value properties to Multi-Select Picklist. Custom fields are not available in Zoho Recruit Free Edition; we confirm the destination Zoho Recruit edition is Standard or above during scoping.

For staffing agency customers of isolved ApplicantPro who maintain client relationships, the Client records map to Zoho Recruit Client objects. Client name, contact information, and any associated job requirements migrate directly. This mapping applies only if the isolved instance includes client-facing functionality; pure corporate HR implementations do not have Client records.

These isolved HCM objects do not migrate to Zoho Recruit. Zoho Recruit is an ATS with no payroll, benefits administration, or time-off processing capabilities. We flag these objects during discovery, document their isolved data location for any future HRMS migration, and exclude them from the Zoho Recruit migration scope entirely. Customers who need both ATS and HRMS functionality should evaluate Zoho People alongside Zoho Recruit as a combined destination.