Migrate from iCIMS Talent Cloud to Recruit CRM & ATS

iCIMS Person Profiles map directly to Recruit CRM Candidates. Standard fields (first name, last name, email, phone, address, resume) migrate 1:1. Custom fields on Person Profiles carry numeric internal identifiers from the iCIMS Schema API; we preserve these as a reference note in the migration record so that if the customer has downstream integrations referencing these IDs, the admin can remap them to Recruit CRM field names. Duplicate resolution uses email as the primary dedupe key.

iCIMS Job Profiles map to Recruit CRM Job records. Fields including title, department, location, employment type, and job description migrate directly. Job pipeline stages from iCIMS Hiring Workflows map to Recruit CRM pipeline stages, though custom stage names and approval routing chains require manual configuration in Recruit CRM's pipeline settings. Job status (open, on hold, closed) maps to Recruit CRM status values.

iCIMS Submittals represent the association between a Person Profile and a Job Profile at a specific stage. We resolve both parent references at migration time: the Candidate record must exist before the Application record is inserted, and the Job record must exist before the Application references it. Submittal status, submission date, and routing history migrate to Application status, submission timestamp, and a notes field respectively. This is the most dependency-heavy object in the iCIMS schema.

iCIMS Companies store employer organization data used within the ATS context. These map to Recruit CRM Client records if the customer uses Recruit CRM's client management module; otherwise they map as Company fields on the Job or Candidate record. Standard fields (company name, industry, size, address) migrate directly. iCIMS company records are distinct from candidate employer history, which is stored as work experience on the Person Profile.

iCIMS Offers record compensation packages extended to candidates including salary, start date, and offer status. Recruit CRM does not have a dedicated Offer object; offer details typically attach to the Candidate record or the Application as custom fields. We migrate the offer data as structured custom fields on the Candidate record and document the mapping so the admin can configure Recruit CRM fields to match their offer tracking needs.

iCIMS Talent Pools are AI-tiered groupings of candidates organized by skill match and Role Fit scoring. Recruit CRM does not have an equivalent Talent Pool object with native AI tiering. Pool membership migrates as Candidate List membership or tag assignments in Recruit CRM. Role Fit tier levels (Tier 1, Tier 2, Tier 3) and AI-calculated scores do not have native equivalents and are documented as custom field values for the admin to interpret in context.

Custom fields on iCIMS Person Profiles, Job Profiles, and Submittals carry a numeric internal identifier alongside the attribute name. During migration, we read the full custom field schema via the iCIMS Schema API and map each to a Recruit CRM custom field of equivalent type (text, number, date, dropdown). The numeric internal identifier is preserved as a migration reference note. We flag any custom fields with type mismatches for the customer admin to resolve.

iCIMS Hiring Workflows define the pipeline stages and routing rules for a Job Profile. Workflow configurations are specific to each iCIMS instance and may use custom stage names and approval chains. We do not migrate workflows as code. We extract a written inventory of every active Hiring Workflow with its trigger, stage names, stage order, routing rules, and approval conditions for the customer admin to rebuild in Recruit CRM's pipeline settings. This document is delivered as part of the migration handoff.

iForms are electronic documents completed by candidates or employees — I-9s, background check authorizations, new-hire paperwork. iForm data must be retrieved by the completed form's ID. Recruit CRM does not have a structured form submission tracking equivalent. We extract iForm records and migrate them as document attachments on the Candidate record. The customer should be aware that iCIMS data migration exports may deliver iForm files as folder structures rather than bundled archives; we flag any missing files in the reconciliation report.

iCIMS Connect Events log candidate engagement activities — email opens, career site visits, chatbot interactions. Recruit CRM tracks candidate activities as notes and activity log entries. We migrate email engagement data as notes on the Candidate record with a timestamp. Career site visit history and chatbot interaction data may not have direct equivalents and are flagged for the admin to assess whether they are required in Recruit CRM.

Referral tracking logs the source of contacts who were referred by existing employees. Referral source metadata attached to Person Profiles migrates to a Referral Source field on the Recruit CRM Candidate record. We map the referral source value and preserve any referral bonus tracking data as a custom field.

iCIMS Onboard records track post-hire onboarding activity, document completion, and employee setup. Recruit CRM is primarily an ATS and recruiting CRM and does not have a dedicated onboarding management module. We migrate onboarding status and completion flags as custom fields on the Candidate record. Full onboarding workflow management is outside Recruit CRM's standard scope and would require a separate onboarding tool post-migration.