Migrate your iCIMS Talent Cloud data

Person Profiles are the core candidate object in iCIMS. The platform parses uploaded resumes into structured, searchable profile fields. Standard fields are stable and well-documented via the Profiles API. We migrate Person Profiles 1:1; custom fields use numeric internal identifiers that we map explicitly during import to preserve the correct field bindings.

Job Profiles represent open positions with associated hiring stage pipelines. The Job Profile data model is documented in the Schema API and includes standard fields for title, department, location, and requisition metadata. We migrate Job Profiles with their active pipeline stage configuration intact.

Submittals represent the association between a Person Profile and a Job Profile at a specific stage. They carry status, submission date, and routing history. This object references both Persons and Jobs and requires careful sequencing in migration to maintain referential integrity across the record graph.

Company profiles store employer organization data used within the ATS context — distinct from candidate employer history. Standard fields include company name, industry, size, and address. Companies are referenced by Job Profiles and Submittals, so we migrate them before child objects to preserve foreign key relationships.

Offers record the compensation package extended to a candidate, including salary, start date, and offer status. The data model is straightforward and migrates cleanly as long as the target system supports offer-level records. We map offer status to equivalent values in the destination ATS.

Onboard records track post-hire onboarding activity, document completion, and employee setup. The onboard and onboardworkflow profile types are accessible via the Schema API. We migrate Onboard records linked to candidates who completed the hiring process; orphaned records are flagged for review before import.

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 must be mapped to equivalent structures in the destination CRM or ATS, as not all platforms support the same tiering model.

Custom fields on 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 Schema API and build an explicit field-mapping table so each custom property lands in the correct destination field without collision or data loss.

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 extract workflow definitions as part of the schema audit and map them to pipeline structures in the destination system.

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 and imported in the correct sequence relative to the associated Person Profile. We extract iForm schema and completed records separately and reassociate them on the destination side.

Connect Events log candidate engagement activities — email opens, career site visits, chatbot interactions. The connectevent profile type is documented in the Schema API. Not all destination ATS platforms store granular engagement events, so we map these to available equivalents such as activity logs or custom note fields.

Referral tracking logs the source of contacts who were referred by existing employees. Referral source metadata is attached to Person Profiles. We extract referral attribution data and map it to the destination ATS's standard referral source field or a custom property where no native equivalent exists.