Migrate from TalentNest to BambooHR

TalentNest Jobs (top-level recruitment containers with title, description, and stage configuration) map directly to BambooHR Jobs in the Hiring module. Job status (Open, Closed, Draft) maps to BambooHR job status. We preserve the job description as a rich-text field and flag the stage names for your admin to map to BambooHR's hiring pipeline stages. Note that BambooHR does not have a native equivalent to TalentNest's stage-based workflow automation with email and SMS triggers; those automations are documented separately for rebuild.

TalentNest Candidate profiles (contact details, resume, demographics, notes) map to BambooHR Candidates. The BambooHR Candidate record holds name, contact information, resume file, and hiring-specific metadata. We map email addresses as the dedupe key. Any TalentNest candidate notes migrate as BambooHR Candidate Notes attached to the candidate record.

TalentNest Applications (junction records linking Candidates to Jobs with status, rating, and stage history) map to BambooHR Applications. We use the TalentNest application audit trail to preserve the original submission date as a custom field (tn_original_submission_date__c) because BambooHR records its own application date at submission and TalentNest resets the application date on any record edit. Stage-transition timestamps migrate as structured activity records so the full hiring timeline is visible in BambooHR.

TalentNest screening results are stored as job-specific custom fields on Applications with no standardized assessment score schema. BambooHR does not have a native assessment engine or screening instrument layer. We export all numeric and text fields from the TalentNest screening section as key-value pairs and flag them explicitly as assessment data. Your admin maps these to BambooHR custom fields on the Application object manually or using our field-mapping tool. This is the highest-effort mapping in the migration and may require a BambooHR partner or professional services engagement for complex screening instruments.

TalentNest stage definitions (Review Candidate, Interview, Offer, etc.) with trigger actions and automation rules map conceptually to BambooHR's hiring pipeline stages. However, the automation logic (email triggers, SMS triggers, conditional routing) is not transferable because BambooHR Hiring does not expose stage-triggered automation as a first-class configuration object. We deliver a written stage-map documenting each TalentNest stage, its automation triggers, and the recommended BambooHR equivalent (manual task assignment, BambooHR email notifications, or a third-party automation layer like Zapier or Workato).

TalentNest User accounts (names, emails, roles, and assignment history) map to BambooHR Users. We resolve by email match. Any TalentNest user without a matching BambooHR user account enters a reconciliation queue for your admin to provision. Note that BambooHR does not support importing users who are not employees through standard API endpoints; contractors and external recruiters may need to be set up separately.

Recruiter notes attached to TalentNest candidate profiles migrate as BambooHR Notes on the corresponding Candidate record. We preserve the author name, timestamp, and full note body. If notes contain rich text formatting, we convert to plain text with inline formatting preserved where the destination supports it.

TalentNest referral tracking (available on Business and Enterprise tiers) stores referral source data as a property on the Application record. If your TalentNest plan includes referral tracking, we map this to the BambooHR Application referralSource field. If you are on a Starter or Growth TalentNest plan without referral tracking, this property will be absent or null in the export, and no mapping is possible.

TalentNest Talent CRM (Growth and above) stores candidate profiles outside of active job applications. We export all CRM candidate records and flag those not linked to a specific Job. Unlinked candidates migrate to BambooHR Candidate Talent Pools (Advantage tier feature). Candidates already linked to a Job migrate as standard BambooHR Candidates attached to the corresponding Application. This split is computed during the transform phase based on whether the candidate record has an associated application.

TalentNest email and SMS templates tied to workflow stages are exported as template records with body text and metadata. Since template IDs are proprietary and BambooHR does not expose a template import API, we deliver the template bodies and metadata in a structured document for your admin to re-create manually in BambooHR. BambooHR's hiring email notifications are account-level templates that your admin configures under Settings > Hiring > Email Templates.

TalentNest job board distribution configuration (30+ aggregators) is stored per Job. We export the distribution list as a property and flag which boards were active at the time of each job posting. BambooHR's ZipRecruiter integration is the only native job board connector; other boards require manual posting or a third-party distribution tool. We provide a job-board matrix document mapping each active TalentNest board to either a BambooHR-supported board or a manual posting recommendation.

TalentNest pre-screen and demographic questions stored as custom fields on Applications export with field type, label, and answer options. We map them to BambooHR custom fields on the Application object. BambooHR supports text, number, date, dropdown, checkbox, and other field types via the BambooHR API. We flag any field type that requires conversion (e.g., a TalentNest multi-select that may need to become a comma-separated text field in BambooHR) and document the conversion logic.