Migrate from iCIMS Talent Cloud to Crelate

iCIMS Person Profiles map to Crelate People records. The platform parses uploaded resumes into structured profile fields including name, email, phone, address, current position, and employer. We preserve custom field numeric identifiers from iCIMS via the Schema API and map them to equivalent Crelate custom fields configured in Settings | Custom Forms before import. Resume files migrate as attachments linked to the People record.

iCIMS Job Profiles map to Crelate Jobs. Standard fields for title, department, location, and job description transfer directly. Pipeline stage configurations from iCIMS map to Crelate's activity-based pipeline structure, but custom stage names and approval chains are documented for manual configuration in Crelate because the stage model differs fundamentally between platforms.

iCIMS Submittals represent the association between a Person Profile and a Job Profile at a specific pipeline stage. We map Submittals to Crelate's candidate-job association records, preserving submission date, stage status, and routing history. Submittal records require both the Person reference and the Job reference to be resolved before import, which we handle by maintaining a lookup table of iCIMS internal IDs to Crelate record IDs.

iCIMS Company profiles store employer organization data within the ATS context, distinct from candidate employer history on Person Profiles. Standard fields (company name, industry, size, address) map directly to Crelate Organizations. We use company name as the dedupe key during import to prevent duplicate Organizations.

iCIMS Offers record the compensation package extended to a candidate including salary, start date, and offer status. This object migrates cleanly to Crelate's Offer structure as long as the target system supports the offer record type. We verify Crelate's active plan tier supports offers before migration; Enterprise and Business Plus tiers include full offer management.

iCIMS Onboard records track post-hire onboarding activity, document completion, and employee setup via the onboard and onboardworkflow profile types in the Schema API. Crelate Hire handles hiring and onboarding workflows, credential management, compliance, and candidate onboarding. We migrate Onboard record status and document references, but complex workflow chains require rebuilding in Crelate Hire post-migration. Onboard records are migrated after all Person Profiles and Submittals are confirmed in Crelate.

iCIMS Talent Pools are AI-tiered groupings of candidates organized by skill match and engagement scoring. Pool membership, tier level, and AI-calculated Role Fit scores do not have a direct Crelate equivalent because Crelate uses a tag-based organization model. We extract pool membership and tier metadata from iCIMS and write it as custom tag fields on the Crelate People record, preserving the signal without attempting to replicate the AI tiering structure.

Custom fields on iCIMS Person Profiles, Job Profiles, and Submittals carry a numeric internal identifier alongside the attribute name. We read the full custom field schema via the iCIMS Schema API and pre-create equivalent Crelate custom fields in Settings | Custom Forms before migration. Field types are mapped (text to text, picklist to picklist, date to date) and any type mismatches are documented for manual resolution.

iCIMS Connect Events log candidate engagement activities including career site visits, email opens, and chatbot interactions via the connectevent profile type. Crelate tracks all recruiting activities made for a candidate, job, opportunity, client, and organization in its native activity stream. We map Connect Events to Crelate activity records with the original timestamp preserved for timeline ordering. Note that Crelate's activity model does not include a direct equivalent for career site tracking or chatbot interactions; these are documented as scope items for customer awareness.

iCIMS referral tracking logs the source of contacts referred by existing employees. Referral source metadata is attached to Person Profiles. We extract referral attribution data and map it to a Crelate tag (referral-source) on the People record, enabling reporting on referral pipeline without a dedicated referral object.

iCIMS iForms are electronic documents completed by candidates or employees, such as I-9s, background check authorizations, or new-hire paperwork. iForm data must be retrieved by the completed form's ID. We flag iForm records as requiring separate manual retrieval from iCIMS because the standard data migration export does not bundle completed forms as accessible files in a recoverable format, as documented in recruiter community threads. We extract iForm IDs and metadata during migration for manual handoff.

iCIMS Hiring Workflows define pipeline stages and routing rules for a Job Profile with custom stage names and approval chains. Crelate uses activity templates and custom forms accessed via Settings | Custom Forms as the equivalent configuration surface. We do not migrate workflow configurations as code. We deliver a written inventory of every active iCIMS Hiring Workflow with its stage names, routing rules, and recommended Crelate Activity Template equivalent for the customer's admin to rebuild.