Migrate from OnePoint HCM to Bullhorn ATS & CRM

OnePoint Employee records carrying recruitment module data (candidate name, contact information, work history, skills, certifications, availability status, and assignment type) map to Bullhorn Candidate. We extract recruitment-specific fields from the unified Employee record and filter out payroll, benefits, and HR-only fields that have no Bullhorn equivalent. The migration preserves candidate status, source attribution, and any resume or profile data attached to the employee record. Employee records without recruitment activity become supplemental exports for the customer's replacement HRMS.

OnePoint Employment Assignments (position title, assignment type, HR assignment status code, system person type, location, and work schedule) map to Bullhorn JobOrder. Assignment status codes require mapping to Bullhorn JobOrder status values (Open, Completed, Cancelled, On Hold). Compensation rate and pay type from the OnePoint assignment map to Bullhorn JobOrder pay rate fields. We flag any multi-state or international job orders for Bullhorn corporate division assignment if the destination is configured for multi-entity staffing.

OnePoint organizational data for external clients (if maintained within OnePoint's recruitment module) maps to Bullhorn ClientCorporation. Bullhorn ClientCorporation holds company name, address, industry, phone, website, and primary contact. We resolve the primary contact as a separate ClientCorporation contact record. If OnePoint does not maintain client data (common in HCM-only configurations), we treat this as a supplemental import requiring the customer to provide a client roster for Bullhorn onboarding.

OnePoint historical assignments and employment records map to Bullhorn Placement history. Each placement links to a Candidate (the placed person), a JobOrder (the position filled), and a ClientCorporation (the client). Start date, end date, placement status, bill rate, and pay rate transfer as Placement fields. We flag any retroactive adjustments or back-dated placements that require special validation in Bullhorn to avoid billing discrepancies.

OnePoint user accounts (recruiters, hiring managers, and system administrators) map to Bullhorn User records. We resolve by email match and map OnePoint role assignments to Bullhorn Bullhornrank and permission sets. Bullhorn's role hierarchy (Corporate, Branch, and Standard roles) differs from OnePoint's security model, so we flag role mappings requiring customer admin confirmation before migration. Any OnePoint user without a Bullhorn login is held in the user reconciliation queue.

OnePoint employee documents attached to recruitment-relevant records (resumes, onboarding paperwork, signed agreements, certifications) migrate as Bullhorn Candidate file attachments. We export available document files from OnePoint and map them to the corresponding Candidate record in Bullhorn. Bullhorn stores attachments as ContentDocument records linked via ContentDocumentLink. Documents without a recruitment context (payroll forms, benefits documents) are excluded from Bullhorn migration and flagged for the HRMS replacement destination.

OnePoint payroll history has no direct Bullhorn equivalent because Bullhorn is not a payroll or HRMS system. We extract payroll records as supplemental export files for the customer's replacement HRMS. For staffing agencies that track bill-and-pay spreads on Placements, we map OnePoint compensation rate and billing rate from the assignment to Bullhorn Placement bill rate and pay rate fields as a configuration step. Historical payroll runs, tax withholdings, and earnings records are excluded from Bullhorn migration.

Benefits enrollments, coverage tiers, and carrier associations in OnePoint have no Bullhorn equivalent. Bullhorn does not administer employee benefits. We export benefits data as supplemental records for the customer's replacement HRMS destination. Any benefits data attached to a candidate record (such as benefit package preferences for contractor placements) is flagged and mapped to a custom field on Bullhorn Candidate or Placement if the customer requires it.

PTO, sick leave, and accrual balances calculated by OnePoint's rules engine do not migrate to Bullhorn. Bullhorn does not track time-off accruals. We export current accrual balances as supplemental records for the customer's replacement HRMS. Accrual data is not discarded; it is packaged alongside the employee migration export as a separate data dictionary for the customer's HR admin to configure in the new HRMS.

OnePoint time entries, punch data, and time-off requests are HRMS data with no Bullhorn equivalent for full-time employees. For staffing agencies using Bullhorn's optional timesheet feature on Placements (contractor billing), we map OnePoint time entries to Bullhorn Placement timesheet records if the customer licenses Bullhorn Back Office. Otherwise, time and labor data is excluded from Bullhorn migration and flagged for the replacement HRMS destination.

Performance reviews, goals, ratings, and performance improvement plans stored in OnePoint are HR data outside Bullhorn's scope. Bullhorn tracks candidate and placement activity but not internal employee performance management. We export performance data as supplemental records for the customer's replacement HRMS. If the customer uses Bullhorn for 1099 contractor placements with performance documentation, we map available notes to Bullhorn Placement custom fields.

OnePoint departments, cost centers, and locations map to Bullhorn Corporation (for multi-entity staffing firms) and Division structure. We extract the full org tree and map it to Bullhorn's corporate hierarchy, which supports multiple corporations for staffing firms operating under different legal entities. If the customer uses OnePoint's location-based assignment routing, we map locations to Bullhorn Branch or Division for recruiter assignment workflows.