Migrate from isolved to Crelate

isolved ApplicantPro candidate records map to Crelate Contact. Core fields (name, email, phone, address, resume) migrate directly. isolved compensation expectations and preferred salary fields map to Crelate custom monetary fields on Contact. The original source of application (referral, job board, direct) migrates to Crelate's Source field. We convert any isolved defined-list values (clearance level, authorization type) to Crelate Tags during transform. Email addresses serve as the dedupe key during import to prevent duplicate Contact creation.

For candidates who are also current or former employees in isolved's HR module, we preserve the Employee record separately from the Applicant record. isolved stores these as distinct records; Crelate uses a single Contact object for both scenarios, with an Employee Status custom field distinguishing current, former, and candidate states. SSN and sensitive tax identifiers are extracted under encryption but are not imported into Crelate's standard fields; we create a masked reference field for compliance audits only.

isolved Job Requisitions map to Crelate Job records. Fields include job title, department, location (city/state), employment type (full-time, part-time, contract), salary range (min/max), and job description. The requisition status (open, filled, on-hold, cancelled) maps to Crelate's Job status field. Crelate's Job object requires a Name field; we populate it from the requisition title to satisfy this required attribute.

isolved applications submitted against a Job Requisition map to Crelate Job records linked to a Contact record via a submission relationship. The application date, stage in the hiring pipeline, and interviewer assignments migrate as Crelate Activity records attached to the Job-Contact pair. Pipeline stages from isolved (applied, screening, interview, offer, hired, rejected) map to Crelate's workflow stage values via the mapping matrix produced during discovery.

isolved Job Codes are employer-defined classification picklist values with no direct Crelate equivalent. We export the full Job Code picklist table from isolved, then create corresponding Crelate Tags under a 'Job Category' tag key. Each candidate's applicable Job Code becomes a Tag on the Contact record; each requisition's Job Code becomes a Tag on the Job record. This approach bypasses Crelate's 20-field soft limit for structured custom fields while preserving the taxonomy.

isolved Work Locations drive tax withholding, workers comp codes, and benefit eligibility in the HR module. In the recruiting context, we map Work Location to Crelate Tags under a 'Work Location' category. The actual address details (street, city, state, zip) also migrate to the Job record's location fields for candidate-facing display.

isolved Pay Types (hourly, salaried, commission-only, contractor) map to Crelate Tags under a 'Compensation Type' category on both Job and Contact records. Salary ranges stored as min/max in isolved migrate to Crelate custom monetary fields (Salary Min, Salary Max) on the Job record.

isolved interview events and scheduling records map to Crelate Event records linked to the relevant Job and Contact. The interview type (phone screen, on-site, panel, technical), scheduled time, interviewer participants, and interview notes migrate as Event records with attendee links via Crelate's EventRelation lookup convention.

Recruiter notes attached to candidates in isolved ApplicantPro map to Crelate Note records linked to the Contact. Notes preserve body text and author attribution. We attach notes via Crelate's ContentDocumentLink pattern if the note includes attachments, or directly to the Contact record for text-only notes.

Resume files, cover letters, portfolio attachments, and offer letters stored in isolved migrate as Crelate Attachments linked to the Contact record. We export document blobs with metadata (file name, MIME type, upload date) and import via Crelate's file attachment API. Binary document format compatibility is verified during staging validation.

isolved tracks application source (employee referral, job board, direct apply, agency) as a defined field on the application record. We map this to Crelate's native Source field and also create a Tag under 'Application Source' to allow multi-dimensional filtering. For agency-sourced candidates, the agency name migrates as a related Contact lookup if the agency exists in Crelate as a Company record.

isolved ApplicantPro workflow rules (auto-stage progression, email triggers, reminder automations) are not migratable as code. We audit every active workflow, document its trigger conditions, actions, and recipients, and deliver a written workflow inventory with recommended Crelate workflow equivalents. The customer's admin rebuilds these in Crelate's workflow builder post-migration.