Migrate from SignalHire to BambooHR

SignalHire People Profiles represent external contacts of unknown employment status. We apply a split rule during scoping: contacts flagged as hired (identified through talent pool status or explicit hiring stage) map to BambooHR Employee records; contacts in recruiting or prospecting stages map to BambooHR Applicant records if the ATS module is licensed, or to Employee records with a recruiting_source__c custom field if the ATS module is not included. The original SignalHire profile UID and status are preserved in custom fields for audit. The LinkedIn URL and SignalHire profile URL migrate as text fields against the Employee or Applicant record.

SignalHire email addresses migrate to the BambooHR standard email field (for Employees) or email field (for Applicants). The SignalHire deliverability status (Valid, Risky, Unknown) is stored in a custom field signalhire_email_status__c so that the HR team can re-verify risky addresses post-migration without losing the original verification signal.

SignalHire phone numbers with country code and line type (mobile/landline) migrate to the BambooHR mobilePhone field. If multiple phone variants exist per person, the primary verified mobile number is prioritized; landline and secondary numbers are stored in a custom field signalhire_secondary_phone__c.

SignalHire Company Profiles (scraped from public profiles, not authoritative records) do not map to a native BambooHR object because BambooHR does not store external company data. Instead, the company name from the SignalHire record becomes the Employee's department or a custom text field signalhire_source_company__c. If the customer has an internal org chart in BambooHR, we map the SignalHire company name to the closest BambooHR Department value. Company domain, industry, and headcount from SignalHire are stored as custom fields for reference only.

SignalHire LinkedIn profile URLs (personal LinkedIn, not company page) migrate to a custom text field signalhire_linkedin_url__c on the Employee or Applicant record. Twitter, GitHub, and other social links are stored in a custom text area field signalhire_social_profiles__c as a semicolon-delimited list. BambooHR does not have native social profile fields; these are reference fields only.

SignalHire talent pools (named lists with many-to-many profile membership) map to BambooHR Applicant Stages if the ATS module is active. We reconstruct pool membership by mapping each SignalHire list ID to a BambooHR stage value and assign it to the corresponding Applicant records. If ATS is not licensed, talent pool membership is stored as a multi-select custom field signalhire_talent_pools__c on the Employee record. The list names are preserved as stage labels in a migration reference document.

The SignalHire job_title field (derived from scraped profile data, not the destination company's HR system) migrates to the BambooHR jobTitle field on Employee or position field on Applicant. We flag during scoping that SignalHire job titles reflect the person's current role at time of scrape, not necessarily the role they would hold if hired. The HR admin updates job titles post-hire through BambooHR's standard onboarding flow.

SignalHire location (city, state, country from the scraped profile) migrates to the BambooHR location field on Employee or the city/state fields in the Applicant address. Country codes are normalized to full country names to match BambooHR's expected format.

SignalHire team members are internal users of the prospecting platform with roles (Admin, Recruiter, Sales). BambooHR team members are HR administrators and employees. There is no meaningful mapping between these concepts. We do not migrate SignalHire user accounts; the customer provisions BambooHR users separately through their BambooHR admin console.

SignalHire credits are a billing mechanism with no equivalent in BambooHR. Unused credits are forfeited at SignalHire cancellation and cannot be transferred. We do not migrate credit balances.