Migrate from Unatrix to BambooHR

Unatrix Candidates map to BambooHR Employee records with a custom hireStatus field distinguishing active employees from pre-hire applicants. Standard fields (firstName, lastName, email, phone, address) migrate directly. The original Unatrix candidate status (Application Received, Interview Scheduled, Offered, Hired, Rejected) is preserved in a custom field candidate_source_status__c for admin reference. Custom Candidate properties discovered during discovery are created in BambooHR via the custom field builder before import begins.

Unatrix Clients (hiring companies) do not have a native equivalent in BambooHR's standard data model, which treats the hiring organization as implicit rather than a tracked entity. For staffing teams migrating to BambooHR as their primary HRIS (managing their own employees rather than placed candidates), we note Client records as out of scope. If the customer uses BambooHR's ATS module for recruiting, Client records are flagged for manual entry or a one-time spreadsheet import to BambooHR's company directory if that feature is enabled on the plan.

Unatrix Jobs map to BambooHR Job Openings if the destination account includes the BambooHR ATS add-on ($99-$199 per month). BambooHR Job Openings include title, department, location, employment type, and description fields that map from Unatrix Job title, client assignment, and job description. Unatrix Job status (Open, On Hold, Filled, Cancelled) maps to BambooHR Job Opening status. If the BambooHR ATS module is not included in the destination plan, Job records are migrated as BambooHR custom fields on the Employee object or noted as out of scope pending ATS purchase.

Skills and qualifications extracted from CVs in Unatrix are tagged using a tenant-specific taxonomy that varies by organization. We discover the full taxonomy during the discovery phase by querying Unatrix for all unique qualification tags across Candidate records. During migration, we create a corresponding custom multi-select picklist field in BambooHR (or a text field if the tag count exceeds picklist limits) and normalize the taxonomy by deduplicating synonyms and mapping category hierarchies into dot-separated values (e.g., 'Programming.Python' or 'Cloud.AWS'). The normalization map is delivered as a written reference document alongside the migration.

Unatrix Projects represent staffing engagements tying a Candidate to a Job under a Client, often including placement metrics and performance data. BambooHR has no native Project or engagement object. We map Projects to a combination of custom fields on the Employee record (projectName__c, clientName__c, jobReference__c, placementDate__c) and Note attachments that carry the full project metadata as structured text. The customer's admin reviews the custom field set during Sandbox validation and can request consolidation or renaming before production migration.

Unatrix interview schedules and team events with date ranges and assigned team members migrate to BambooHR as structured Notes attached to the relevant Employee record, preserving the date range, interviewer names, and event description. Native BambooHR calendar or scheduling functionality does not support importing external interview data, so event records are migrated as reference documentation rather than live calendar entries. The customer should plan to rebuild interview scheduling workflows in BambooHR's workflow builder post-migration.

CVs and attachments stored against Unatrix Candidate records are extracted as binary files where accessible via the REST API. We preserve file names, content type, and association to the correct Candidate. During BambooHR import, files are re-attached to the corresponding Employee record using BambooHR's file attachment API. Binary files that cannot be extracted programmatically are flagged with a file reference note and the original file name so the customer's admin can manually re-upload if needed.

Unatrix user accounts representing recruiters, sales managers, and administrators map directly to BambooHR user accounts. Role assignments (Admin, Recruiter, Hiring Manager, Read-Only) are mapped to BambooHR permission roles during discovery. Active versus inactive status is preserved in BambooHR user status. The BambooHR API key for the migration user is scoped to the permissions of the account that generated it; we use a dedicated service account with employee data access rather than an admin's personal key.

Unatrix KPI dashboards and report configurations are generated from underlying raw data and do not export as self-contained objects. We do not migrate these. We extract the raw data records (Candidates, Jobs, Projects, engagement dates) so that KPI recalculation is possible in BambooHR's reporting module. The customer receives a written inventory of every Unatrix report and dashboard with its configuration summary so the admin can rebuild equivalent reports in BambooHR's Standard and Custom Report builder.

Unatrix custom fields defined on Candidate and Job objects are discovered during the scoping phase by querying the Unatrix schema via the REST API. Each custom field is typed (text, number, date, picklist, checkbox) and mapped to the equivalent BambooHR custom field type. BambooHR's self-serve custom field builder is available without contacting support, which accelerates schema setup. Multi-value tags in Unatrix map to BambooHR multi-select picklists where the value set is bounded; free-form tags map to text fields.