Migrate from Unatrix to Bullhorn ATS & CRM

Unatrix Candidates map 1:1 to Bullhorn Candidate records. We preserve standard fields (name, email, phone, address, employment history) and extract custom properties defined on the Candidate object during discovery. CV documents and attachments associated with Candidates migrate as ContentDocument records linked via ContentDocumentLink to the parent Candidate. The migration resolves the Bullhorn Candidate deduplication rule (email as primary key) before insert to avoid duplicate Candidates in high-volume pipelines.

Unatrix Client records map to Bullhorn ClientCorporation (the Bullhorn term for company-level CRM records). We preserve client name, industry, address, revenue range, and any custom fields. Client status (active, inactive, prospect) maps to the corresponding Bullhorn status field. The Client-to-Job relationship (which Unatrix links directly) resolves in Bullhorn through JobOrder.clientCorporationId linking to the ClientCorporation record.

Unatrix Job records map to Bullhorn JobOrder. Job title, description, requirements, status (open, filled, closed), and salary/rate fields migrate directly. Required qualifications from the Unatrix Job are extracted as a list and mapped to Bullhorn Skills associated with the JobOrder via the JobOrderSkill entity. Job publish date and expiration date migrate as is.

Unatrix Qualifications are extracted from CVs using a tenant-specific taxonomy that varies between organizations. We discover the full taxonomy during the scoping phase, normalize skill names (removing duplicates, standardizing casing, resolving synonyms), and map the normalized set to Bullhorn Skills. Each Skill record is created once in Bullhorn and then associated with Candidates (via CandidateSkill) and JobOrders (via JobOrderSkill) with a proficiency level where available in Unatrix. This is the highest-scope transformation in the migration.

Unatrix Projects represent staffing engagements linking Candidates to Jobs under a Client, with placement performance metadata. Bullhorn has no native Project object. We map Projects to either a Bullhorn custom object (Front Office Growth/Enterprise) or an Opportunity with structured custom fields (JobOrder title, ClientCorporation link, placement status, and key metrics). The customer selects the approach during scoping based on their Bullhorn edition. Engagement metadata (project status, revenue, milestones) is preserved as custom fields on the destination object.

Unatrix interview schedules and team events (with date ranges and assigned team members) map to Bullhorn Event records. We extract the event title, start and end datetime, assigned recruiter (mapped to Bullhorn User by email), and candidate association (mapped via a Candidate lookup). Bullhorn EventRelation records are created to link attendees (candidate and internal users) to the event.

Unatrix user accounts (recruiters, sales managers, administrators with role-based permissions) map to Bullhorn User records. We resolve by email match and preserve role assignment. Active versus inactive status migrates as-is. Bullhorn User provisioning (deprovisioning is often ticket-requiring according to user reviews) should be coordinated with the Bullhorn admin before migration to avoid permission gaps on day one.

Unatrix custom fields on Candidate and Job objects map to Bullhorn custom fields on the corresponding entities. Bullhorn enforces field type limits per edit type (e.g., up to 20 checkboxes, dropdowns, or text fields). If the migration discovers custom field counts that exceed Bullhorn's per-entity limits, we escalate to a custom object design. Custom field definitions are documented during discovery and deployed to the Bullhorn Sandbox before production migration.

Unatrix KPI dashboards and report configurations are generated from raw data and do not export as self-contained objects. We do not migrate these. We extract the underlying raw data records (placement counts, cost-per-hire, time-per-hire) so that Bullhorn's reporting and analytics capabilities can reproduce the metrics from migrated data. Bullhorn's built-in reporting and Pulse Relationship Intelligence (Pro/Enterprise tiers) serve as the replacement reporting layer.

CVs and attachments stored against Candidate records in Unatrix are extracted as file references via the Unatrix REST API where accessible. File names, content types, and association metadata are preserved. Binary file content is migrated separately from record data and linked via Bullhorn ContentDocument and ContentDocumentLink. Bullhorn's document storage limits vary by edition; we flag any attachment volume that approaches the storage ceiling.

Unatrix does not have a separate Placement object but tracks placements through the Project-Candidate-Job relationship. We reconstruct Placement records as Bullhorn Placement entities (a standard Bullhorn object linking Candidate to JobOrder with employment terms, start date, and billing/pay rate fields). Placement history is derived from Project records with status=completed and candidate-job association metadata.

Unatrix engagement records (if accessible via REST API) migrate to Bullhorn Task (calls, notes, generic tasks), Event (meetings), and EmailMessage (emails) objects. We resolve the WhoId (Candidate) and WhatId (JobOrder, Opportunity, or ClientCorporation) at migration time. Bullhorn's engagement timeline organizes these as Activity records. Bullhorn's Activity Goals and Sales Quotas (Enterprise tier) serve as the replacement engagement tracking layer.