Migrate from Loxo to Bullhorn ATS & CRM

Loxo Candidates unify job-seekers and client-side contacts under one object with a type property distinguishing them. Bullhorn splits these into Candidate (job-seekers with skills, resume, experience) and ClientContact (client-side people with company association). We compute the split at migration time using Loxo's candidate_type property or tagging logic, create both Bullhorn records, and link them with a custom field loxo_original_id__c on each for cross-reference audit.

Loxo client contacts map to Bullhorn ClientContact with company linked to ClientCorporation. We preserve phone, email, title, and custom properties. Address data migrates to Bullhorn's address compound field structure. Any Loxo contact tags map to Bullhorn ClientContact categories or a custom multi-select picklist.

Loxo Client Companies map to Bullhorn ClientCorporation with the company name as the dedupe key. Parent-child hierarchy migrates via the parentCompany relationship. Billing address, industry, and revenue range map to Bullhorn standard fields; custom properties migrate to Bullhorn custom fields if the edition supports them.

Loxo Jobs map to Bullhorn JobOrder with title, description, requirements, and status preserved. Custom job fields map to Bullhorn custom fields on JobOrder. The job's assigned owner migrates via email lookup to Bullhorn User. Published job links and career portal URLs are preserved as text fields for redirect configuration after cutover.

Loxo Deals map to Bullhorn Opportunity. The Loxo pipeline becomes a Bullhorn Record Type with a corresponding Sales Process that defines the stage values. Closed-Lost and Closed-Won reasons from Loxo custom properties become Bullhorn Opportunity LossReason fields. We validate that the mapped Bullhorn Sales Process has the required stage values before migration.

Loxo's customizable pipeline stages are org-specific and stored per Deal. We extract the full stage list from the Loxo API during scoping, present it to the customer for confirmation, and map each stage to a Bullhorn Opportunity StageName. Bullhorn's default Sales Process is extended with the customer-confirmed stage list. If multiple Loxo pipelines exist, each becomes a Bullhorn Record Type with its own Sales Process.

Loxo Placements record placed candidates against a Job and Deal, including start date, compensation, and status. Bullhorn has a native Placement object with fields for candidate (Candidate lookup), job (JobOrder lookup), client corporation (ClientCorporation lookup), start date, end date, pay rate, bill rate, and status. We map Loxo placement compensation details to Bullhorn's pay rate and bill rate fields, preserving the linked JobOrder and the placed Candidate record.

Loxo custom fields on Candidates, Contacts, Jobs, and Deals map to Bullhorn custom fields. Bullhorn ATS edition supports 2 custom objects; Growth and Enterprise support 10 custom objects with 55 fields each. We pre-coordinate the Bullhorn Support ticket for custom object creation during scoping so the schema is ready before migration. Custom field types (text, picklist, date, number) map to Bullhorn field types with edit types confirmed during scoping.

Loxo engagement history (email threads, call logs, SMS, and notes) migrates to Bullhorn Task and Event records. Call disposition and duration map to Bullhorn Task fields. Emails attach to the activity timeline via Task with the body preserved. We scope engagement history to the most recent 12-24 months per Loxo's documented recommendation to reduce fragmented thread import. Bullhorn's Activity DateTime ordering is preserved from the original Loxo timestamps.

Binary attachments stored per Loxo record (resumes, cover letters, client agreements) are extracted from the API as file URLs and re-uploaded to Bullhorn. Resumes attach to Bullhorn Candidate records via the document management system. Large file counts may require chunked download/upload with hash verification to confirm fidelity. We flag any attachment that exceeds Bullhorn's file size limit for manual handoff.

Loxo tags on Candidates, Contacts, and Jobs migrate to Bullhorn category associations. Bullhorn uses a category/tagging system on records that we populate during import. If the customer uses a tag strategy for segmentation, we recommend mapping to Bullhorn custom picklist fields for searchability rather than notes-only tags.

Every Loxo record has an assigned Owner linked by user ID and email. We resolve Loxo owner assignments to Bullhorn User records by email match. Any Loxo owner without a matching Bullhorn User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Active versus inactive status is preserved from the Loxo owner record.

Loxo Outreach sequences, email cadence rules, SMS steps, and auto follow-up triggers are not exposed through the Loxo public API and cannot be migrated as configuration. We preserve the most recent outreach status as Candidate custom properties (last campaign name, last step reached, last outreach date) so the destination Bullhorn team knows where each candidate sits without rebuilding from scratch. We deliver a written inventory of all active Loxo Outreach campaigns for the customer's admin to configure in Bullhorn or a third-party sales engagement tool.

Loxo's client portal configuration (branding, shared job visibility, report templates) is tied to the instance-level portal setup and is not accessible via API. Bullhorn's client portal is a separate configuration. We do not migrate these settings. We deliver a written summary of the current Loxo portal configuration for the customer's Bullhorn admin to replicate in Bullhorn's portal settings.