Migrate from SignalHire to Recruit CRM & ATS

SignalHire People Profile maps to Recruit CRM Candidate. The SignalHire profile URL becomes a custom text field original_signalhire_url__c on the candidate record. The SignalHire-generated UID is preserved in signalhire_uid__c for deduplication. Name fields (first_name, last_name) map directly. The candidate is created before any dependent records to satisfy Recruit CRM's required fields on creation.

SignalHire Company Profile maps to Recruit CRM Organization. Company name, domain, industry, size range, and location migrate. Headcount and LinkedIn company page URL are stored as custom fields since Recruit CRM Organization's standard fields do not cover all SignalHire company attributes. The organization is created before the candidate so that the candidate-organization relationship is resolved at insert time.

Each email address from SignalHire migrates to the Candidate's email field, with the SignalHire verification status (Valid, Risky, Unknown) stored in a custom picklist field signalhire_email_status__c and the SignalHire confidence score stored in signalhire_email_score__c. Candidates with multiple email addresses retain the additional addresses as custom multi-line text fields so recruiters can see the full contact portfolio. Recruit CRM's native email verification runs independently on the imported addresses post-migration.

SignalHire phone records migrate to the Candidate's primary phone field with country code and line type (mobile, landline) preserved in custom fields signalhire_phone_type__c and signalhire_phone_country__c. Each additional phone variant from SignalHire is stored as a secondary phone custom field. Verification confidence scores migrate to signalhire_phone_score__c. Phone data provenance is noted as SignalHire-sourced so the customer understands the confidence level during initial outreach.

LinkedIn profile URL, Twitter/X handle, GitHub URL, and any other social links from SignalHire migrate to the Candidate record's social link fields. The LinkedIn URL is stored as a dedicated linkedin_url__c field for use in Recruit CRM's native LinkedIn browser extension integration. Each social platform is identified by type in a custom text array so the full portfolio of social presence is visible on the candidate profile.

SignalHire work history entries (job title, company name, start date, end date, is_current) migrate to the Candidate's employment history sub-section in Recruit CRM. Company name is linked to the mapped Organization record where a match exists; otherwise it is stored as free text. Job title accuracy is flagged as an advisory because SignalHire company profiles are scraped derivatives and some work history may reflect outdated titles at time of scrape.

SignalHire city, state, country, and postal_code fields migrate to the Candidate's address section. SignalHire location is sourced from profile data and may not reflect current residence or intended work location; this is flagged as a data provenance note during migration. If SignalHire returns timezone data it is stored in a custom field for scheduling and outreach optimization in Recruit CRM.

SignalHire's per-email deliverability status (Valid, Risky, Unknown) has no native equivalent in Recruit CRM's Candidate object. We create custom picklist and number fields on the Candidate record during schema configuration and preserve the full SignalHire verification confidence score for each contact method. This allows recruiters in Recruit CRM to filter candidates by outreach priority based on historical SignalHire verification data without re-running enrichment.

SignalHire named lead lists and talent pools are reconstructed in Recruit CRM as candidate lists. List membership is a many-to-many relationship: we extract each SignalHire list ID and its constituent profile UIDs, then create corresponding lists in Recruit CRM and add each profile's mapped candidate ID as a member. If a candidate belongs to multiple SignalHire lists, the candidate is added to all corresponding Recruit CRM lists. Lists with fewer than 10 members are noted as small lists during migration scoping so the customer can decide whether to create them in Recruit CRM.

SignalHire profile tags, source channel, and lookup attribution (how the candidate was originally found in SignalHire) are preserved as custom text fields on the Candidate record. This includes the original SignalHire lookup timestamp so the customer can understand the data age of each record. Any SignalHire notes attached to the profile migrate as Candidate notes in Recruit CRM.