Migrate from Alpha Hire to Bullhorn ATS & CRM

Alpha Hire Job Orders map directly to Bullhorn JobOrder. We preserve source attribution (VMS vs manual entry), status, and associated hiring manager from the Alpha Hire export. JobOrder.title, JobOrder.address, JobOrder.salary, and JobOrder.description migrate as standard Bullhorn fields. VMS-sourced job orders may have incomplete metadata compared to manually entered orders; we validate every record against Bullhorn's required fields during import and flag records with missing required values for customer review before final load.

Alpha Hire Candidate profiles (including AI-generated screening scores and match ratings) map to Bullhorn Candidate records. We preserve candidate firstName, lastName, email, phone, occupation, and address fields, and carry any screening scores as custom fields on the Bullhorn Candidate record. Resume documents migrate as ContentDocument records attached via ContentDocumentLink to the parent Candidate.

Alpha Hire Talent Partners are distinct entities who assist throughout the hiring process. We map talent partner profiles to Bullhorn ClientContact records under a designated ClientCorporation (typically the customer's own company record used as a holding entity for internal partners). Assignment history and associated client records migrate as Note entries or Opportunity associations depending on the relationship structure. Active talent partner assignment logic requires documentation during scoping because Alpha Hire's rule engine logic does not export.

Alpha Hire's 3-step hiring process maps to Bullhorn's Placement (the final placed record) and Opportunity (the pipeline tracking record). Each Alpha Hire process stage maps to a Bullhorn Opportunity Stage value that we configure as a Sales Process in Bullhorn during schema setup. Process templates that vary by client configuration are mapped to Bullhorn Record Types if multiple distinct workflows exist.

Alpha Hire's rule-based auto-assignment engine stores routing logic internally with no exportable format. During scoping, we request the customer to document their active rule configurations. We reproduce the rule logic in a written inventory that maps each Alpha Hire rule to Bullhorn equivalent functionality: Bullhorn Workflows (record-triggered), Assignment Rules (lead-to-rep routing), or Bullhorn Automation (formerly Herefish) for complex cadence-based routing. The rebuild is manual and falls outside the data migration scope.

Alpha Hire subscription metadata (plan tier, billing model, start dates) is preserved as read-only reference data in a Note attached to the migration summary record. Bullhorn does not replicate billing relationships; these are re-established directly with Bullhorn post-migration. We flag the current Alpha Hire plan tier to help the customer select the equivalent Bullhorn edition during scoping.

Alpha Hire integrates with Microsoft Outlook, ADP, and QuickBooks. We document active integrations during scoping, identify Bullhorn equivalents (Microsoft Outlook sync via Bullhorn native integration, ADP via Bullhorn marketplace connector or third-party integration), and flag any Alpha Hire integrations that have no Bullhorn equivalent for the customer to address post-migration. VMS feed configurations do not migrate; we document the current VMS sources for reconfiguration in Bullhorn's VMS settings.

Candidate attachments, offer letters, and onboarding documents stored within Alpha Hire migrate to Bullhorn ContentDocument records attached to the parent Candidate via ContentDocumentLink. Export availability depends on the Alpha Hire data export capability. We attempt to include all accessible documents and flag any records where attachments were inaccessible during the export phase. Bullhorn's file storage limits depend on the edition tier.

Alpha Hire's AI-powered candidate screening scores and match ratings migrate to Bullhorn custom fields on the Candidate record. We create custom fields during Bullhorn schema setup (up to the edition limit: Front Office Growth/Enterprise: 10 custom objects with 55 fields each; ATS: 2; ATS Growth: none). If screening data exceeds these limits, we prioritize the highest-value scoring fields and document additional fields for manual entry post-migration.

Alpha Hire client relationships stored alongside job orders and talent partner assignments map to Bullhorn ClientCorporation (the company entity) and ClientContact (the hiring manager or buyer contact). We use company name as the dedupe key. ClientContact records are linked to their parent ClientCorporation via the corporateId lookup. Historical client notes and communication records migrate as Note or Task entries on the ClientCorporation.

Alpha Hire's pipeline stage assignments on job orders and hiring processes map to Bullhorn Opportunity Stage values. We configure a Bullhorn Sales Process with the relevant stage values, probabilities, and record type associations during Bullhorn schema setup. Stage names and probabilities are derived from the Alpha Hire export and validated against the customer's current Bullhorn edition configuration.

Alpha Hire job order assignments (which recruiter or talent partner is assigned to a requisition) map to Bullhorn Opportunity OwnerId and Placement records. Owner resolution uses email matching against the Bullhorn User table. Any Alpha Hire assignment without a matching Bullhorn User goes to a reconciliation queue for the customer's admin to provision before record import resumes.