Migrate from In-recruiting to BambooHR

In-recruiting Candidate records map to BambooHR People as Candidate records (not Employee records, which are reserved for hired employees). The In-recruiting candidate first name, last name, email, phone, address, and source channel map to the equivalent BambooHR fields. We resolve duplicate candidates by email dedupe before import. Any In-recruiting GDPR consent flags map to BambooHR custom fields; the customer's BambooHR admin configures the corresponding consent records post-migration.

In-recruiting Job records map to BambooHR Job Openings. The In-recruiting job title, description, department, location, and employment type map to the equivalent BambooHR fields. Open/closed status maps directly. Active In-recruiting jobs are handled last in the migration sequence so that live job postings remain functional through cutover. In-recruiting job fields with HTML-formatted descriptions are stripped to plain text before insertion into BambooHR.

In-recruiting Application records (the join entity between Candidate and Job) map to BambooHR Candidate records linked to a Job Opening. The Application ID is preserved in a custom BambooHR field for reconciliation. If the In-recruiting source system uses a separate Application object rather than a direct candidate-to-job relationship, we flatten it by linking the Candidate to the corresponding BambooHR Job Opening and preserving the application timestamp and status.

In-recruiting pipeline stages (Configured Pipeline Stage 1, Stage 2, etc.) do not have a direct BambooHR equivalent because BambooHR uses a simpler candidate status model (Applied, Phone Screen, Interview, Offer, Hired). We map each In-recruiting stage to the nearest BambooHR status and preserve the original stage label in a custom multi-select picklist field original_pipeline_stage__c on the Candidate for reporting continuity. If In-recruiting uses more than five custom pipeline stages, we recommend consolidating during migration because BambooHR's status workflow is less flexible.

In-recruiting Interview records map to BambooHR Interview records on the Candidate. We transfer the interview date, interviewer name (resolved to a BambooHR User by email), interview type, duration, and interviewer score if present. Interviewer feedback notes migrate as a text custom field on the Interview record. If In-recruiting stores scorecard ratings in structured fields, we flatten them to a text field since BambooHR's ATS interview model does not support structured scorecard fields by default.

In-recruiting Notes linked to Candidates, Applications, or Jobs map to BambooHR Notes attached to the corresponding Candidate or Job Opening. We preserve the note creation date, author (resolved to a BambooHR User by email), and note body. Rich-text notes from In-recruiting are converted to plain text with bullet points preserved. Notes attached to Placement records are migrated to the hired Employee's BambooHR People record.

In-recruiting Company or Client records (used by staffing agencies to track client organizations) map to BambooHR Company records if the BambooHR account has the ATS Company feature enabled. If the destination BambooHR account does not use ATS Companies, we store the client organization name as a custom text field on the Candidate or Employee record. The customer chooses the strategy during scoping.

In-recruiting User records (internal recruiting team members) map to BambooHR Employee records in the People module if the customer wants to manage their recruiting team within BambooHR. For organizations that only use BambooHR for candidate and employee data and not for internal user management, In-recruiting Users are not migrated; instead we map Owner references on records to the corresponding BambooHR User by email resolution.

In-recruiting tags (used to label candidates by skill, source, or category) map to BambooHR custom multi-select picklist fields. We create the custom field in BambooHR before migration, populate it with the unique tag values, and link it to the Candidate object. Tags used for candidate classification migrate to the custom field; tags used for sourcing attribution migrate to the candidate_source custom field. The customer specifies the tag strategy during scoping.

In-recruiting custom fields on Candidate, Application, Job, and Interview migrate to BambooHR custom fields of the closest matching type. We translate In-recruiting field types (text, number, date, dropdown, checkbox, multi-select) to their BambooHR equivalents. Localized date formats from In-recruiting are converted to the format configured in the BambooHR destination account. Any In-recruiting custom fields with unsupported data types are flagged during discovery and resolved by the customer before migration.