Migrate from iCIMS Talent Cloud to BambooHR

iCIMS Person Profiles map to BambooHR Employee records. Standard fields (name, email, phone, address, work history) migrate directly. We read the full Person Profile schema via iCIMS Schema API to capture all standard attribute names. Custom fields migrate to BambooHR custom fields using the BambooHR Custom Field Builder API; short answer and single-select list custom fields transfer cleanly. Multi-select list custom fields, section headers, and information fields cannot pass via BambooHR API and are flagged in the custom field inventory as manual-entry items.

iCIMS Job Profiles (requisitions) map to BambooHR Job records. Title, department, location, employment type, and job description migrate directly. Hiring pipeline stages (iCIMS Workflow) do not have a BambooHR equivalent; we document each Job Profile's pipeline stages as a written stage configuration inventory for the customer's admin to recreate in BambooHR's job settings.

iCIMS Submittals represent the association between a Person Profile and a Job Profile at a specific stage. We create the Employee record with application source and application date captured in BambooHR's standard hiring metadata. The submittal stage (e.g., Phone Screen, Interview, Offer Extended) has no direct BambooHR field; we preserve stage history as a custom long-text field on the Employee record for audit purposes.

iCIMS Offer records (salary, start date, offer status) migrate to BambooHR Employee compensation fields (pay rate, pay type, start date) and a custom field for offer status. Compensation details migrate cleanly as long as BambooHR's pay structure (hourly/salary, pay frequency) is configured before migration. BambooHR does not have a separate Offer object; offer data folds into the employee record.

iCIMS Onboard records track post-hire onboarding activity and document completion. We migrate onboarding task status, document completion flags, and employee setup progress to BambooHR Employee custom fields. BambooHR's own onboarding feature may be active post-migration; we document the iCIMS onboarding state so that the customer can recreate the checklist in BambooHR's onboarding tool or complete remaining tasks manually.

iCIMS Company profiles store employer organization data used within the ATS context for candidate work history. BambooHR stores candidate work history as structured employment records on the Employee profile. We extract employer name, title, dates, and description from iCIMS Company associations and write them as employment entries on the BambooHR Employee record rather than creating separate Company records.

iCIMS Talent Pools are AI-tiered groupings of candidates organized by skill match and engagement scoring. BambooHR does not have a Talent Pool or CRM feature. We extract all Talent Pool memberships, tier levels, and AI-calculated Role Fit scores and deliver them as a written candidate segmentation inventory. The customer uses this to recreate talent pools in BambooHR by filtering employee records or exporting to a spreadsheet segmentation tool.

iCIMS custom fields carry a numeric internal identifier alongside the attribute name. We read the full custom field schema via the iCIMS Schema API before migration. BambooHR supports short answer, long answer, single-select list, and multi-select list custom fields. We create the matching BambooHR custom fields before migration begins. Any iCIMS custom fields of type Information, Section Header, or unsupported multi-select cannot pass via BambooHR API and are listed as manual-entry items in the migration report.

iCIMS Hiring Workflows define pipeline stages and routing rules specific to each Job Profile. Workflow configurations are not transferable to BambooHR because BambooHR does not support configurable stage pipelines for hiring. We extract every active Hiring Workflow (stage names, approval chains, routing rules) and deliver a written workflow inventory that maps each iCIMS workflow to a BambooHR approval chain configuration or a documented manual process the customer recreates post-migration.

iCIMS iForms (completed I-9s, background check authorizations, new-hire paperwork) must be retrieved by the completed form's ID. Reddit evidence from users who left iCIMS confirms that the standard data migration export delivers forms as a wall of folders and Excel sheets without the actual document files (zips containing completed forms). We flag this gap explicitly. We attempt to retrieve completed iForm documents via the iCIMS API using completed form IDs; if documents are not accessible through API, we document the iForm inventory and recommend manual retrieval from iCIMS admin export or requesting the files from iCIMS support before the source account closes.

iCIMS Connect Events log candidate engagement activities: email opens, career site visits, chatbot interactions. The connectevent profile type is documented in the iCIMS Schema API. BambooHR does not have a candidate engagement tracking feature. These records do not migrate. We deliver a written summary of engagement event counts per candidate so the customer has visibility into engagement history for manual follow-up.

iCIMS referral tracking logs the source of contacts who were referred by existing employees. Referral attribution attaches to Person Profiles. We extract referral source data and map it to BambooHR's standard Employee referral source field if configured, or to a custom Employee field. BambooHR has built-in employee referral tracking that the customer activates post-migration.