Migrate from SignalHire to Zoho Recruit

SignalHire People Profile records map to Zoho Recruit Candidate. We map firstName, lastName, currentJobTitle, location, signalhireUid, and linkedinUrl to their Zoho Recruit Candidate field equivalents. SignalHire's currentCompany and currentCompanyId resolve to either an existing Zoho Client record (if the company is a known client) or a Contact record created during the migration. Note that SignalHire profiles may lack a structured lastName field; we flag records missing lastName for the customer to review and assign a placeholder value ('not provided' per Zoho Recruit's import requirements) before import to avoid record rejection.

SignalHire profiles may contain multiple email addresses with individual verification status (Valid, Risky, Unknown). Zoho Recruit's Candidate module stores a single primary email address. We preserve additional emails as custom text fields (email_2__c, email_3__c) and the verification status for each email in corresponding custom picklist fields. The primary email is selected as the highest-confidence Valid result; if no Valid result exists, the Risky result is used and flagged for review.

SignalHire stores multiple phone variants per profile with country code and line type (mobile, landline, unknown). Zoho Recruit Candidate holds one primary phone field. We map the primary mobile phone to the standard Phone field and additional phone numbers to custom fields (mobile_phone__c, work_phone__c, alternate_phone__c). SignalHire's verification confidence score migrates to custom picklist fields on each phone variant.

SignalHire's linkedinUrl field maps to the LinkedIn social profile on the Zoho Recruit Candidate. This is the primary social reference used for duplicate detection: if a Zoho Candidate with the same LinkedIn URL already exists, we flag it for merge rather than creating a duplicate. SignalHire's signalhireUid is stored as a read-only custom field for audit traceability back to the source system.

SignalHire profiles may include social profile URLs beyond LinkedIn — Twitter, GitHub, Facebook, and others stored as URL arrays. Zoho Recruit's Candidate module does not have native multi-social fields. We map each social platform to a dedicated custom URL field (twitter_url__c, github_url__c, facebook_url__c). Custom fields must be pre-created in Zoho Recruit via the UI before migration; we provide a field creation guide as part of the pre-migration checklist.

SignalHire's email deliverability status (Valid, Risky, Unknown) and confidence score have no native Zoho Recruit equivalent. We preserve this metadata in two custom fields on Candidate: email_verification_status__c (picklist) and email_verification_score__c (number). This allows recruiters to filter candidates by data quality and prioritize outreach on Valid-status contacts even after the SignalHire account is decommissioned.

SignalHire named talent pools and lead lists are many-to-many membership relationships with no direct Zoho Recruit equivalent. We reconstruct list membership using Zoho Recruit's Tags feature: each SignalHire list name becomes a Tag, and each profile's UID membership is mapped to the corresponding tag. During import, we attach all relevant tags to each Candidate record. If a customer has more than 50 lists, we coordinate with them to prioritize the most actively sourced pools.

SignalHire Company Profiles (company name, domain, industry, size range, location, LinkedIn company page URL) map to Zoho Recruit Client records. We use the company domain as a dedupe key during import. If the customer has existing Client records in Zoho Recruit, we match by domain and link Candidates to the existing Client rather than creating duplicates. Company data provenance (scraped from public professional pages rather than authoritative records) is noted in a custom field company_data_source__c for data quality awareness.

SignalHire team members on paid plans (name, email, role) map to Zoho Recruit User records by email match. We extract the distinct owner IDs from SignalHire profile records and match them to Zoho Recruit users by email. Users without an existing Zoho account are placed in a reconciliation queue for the customer admin to provision before the migration phase resumes. Non-recruiter team members (billing-only or viewer roles) do not have a Zoho Recruit User equivalent and are not migrated.

SignalHire profiles contain work history (job title, company, start date, end date, location). Zoho Recruit Candidate supports a Work Experience section with these fields. We map job title and company to the primary work history entry and store additional positions as secondary entries. SignalHire profiles that lack structured work history (only current title and company) migrate as a single work experience entry.

SignalHire API keys are scoped to the account and cannot be transferred to Zoho Recruit. API credentials for the destination platform must be generated separately in Zoho Recruit via Setup > Developer Space > API. We do not migrate authentication material. Customers should revoke SignalHire API keys after migration completes to prevent unauthorized access to the decommissioned account.

Credits are a SignalHire-specific billing mechanism with no equivalent in Zoho Recruit's subscription model. We do not migrate credit balances. Any unused SignalHire credits are forfeited at subscription cancellation. We advise customers to consume or document their remaining credit balance before migration begins if they want visibility into total usage against their billing cycle.