Migrate from Revolut People to Bullhorn ATS & CRM

Revolut People employee records map to Bullhorn Candidate. We extract name, email, phone, job title, department, employment status, start date, and manager reporting line. The Candidate record becomes the primary destination object. If the Bullhorn instance uses the Candidate-to-Contact split, we map Revolut People employees to Candidate (active or placed worker) and flag any contingent worker records for separate handling. Custom fields for employment type (full-time, part-time, contractor) and cost centre migrate to Bullhorn Candidate custom fields.

Revolut People's hierarchical org chart with departments, roles, and reporting lines has no direct Bullhorn equivalent. Bullhorn's Corporate Structure provides divisions and user roles for internal staffing operations, but it does not store a full org chart or role-to-skills mapping. We extract the hierarchy as a flat parent-child map, restore divisions in Bullhorn's corporate structure, and document the reporting-line tree for the customer's admin to reference during Bullhorn user provisioning.

Revolut People job postings map to Bullhorn JobOrder. Job title, description, location, employment type, salary range, and status migrate directly. The job pipeline stage names from Revolut People map to Bullhorn JobOrder status values (Open, On Hold, Closed, Cancelled). We preserve the original job ID for audit and cross-reference during reconciliation.

Revolut People applicant records map to Bullhorn Candidate (person record) and JobSubmission (application record linking Candidate to JobOrder). Application status values from Revolut People map to Bullhorn SubmissionStatus (New, Active, Reviewed, Interviewing, Offered, Placed, Rejected). Interview scheduling notes and application notes migrate as Candidate notes. Where Revolut People stores candidate skills or competency scores against the application, we map these to Bullhorn Candidate custom fields.

Revolut People performance cycles (date-bounded review periods with review records) have no native Bullhorn object. Bullhorn ATS does not include performance management. We migrate cycle metadata as a Bullhorn Note on the Candidate record with cycle name, start date, and end date, and we flag the performance cycle object in the written inventory for the customer to rebuild in Bullhorn or a complementary performance tool post-migration.

Revolut People review records with structured feedback, ratings, and reviewer comments migrate to Bullhorn Candidate custom fields (rating scores) and a Candidate Note (full review text and reviewer identity). PIP and probation records migrate as flagged notes with a custom status field to distinguish them from standard reviews. We cannot preserve review cycle relationships natively in Bullhorn; this context is documented in the written handoff.

Revolut People skills, proficiency levels, and custom competency frameworks vary per tenant and have no standard Bullhorn equivalent. We audit the full skill library during discovery, normalise skill names and proficiency scales, and map each skill to a Bullhorn Candidate custom field. Custom scorecards with non-standard rubrics are flattened to key-value pairs and stored in a structured note. Bullhorn's custom field limits per object are confirmed during scoping.

Revolut People goal records with milestones, ownership, and progress percentages map to Bullhorn Task. Goal name, description, due date, and status transfer. Custom roadmap layouts do not have a Bullhorn equivalent; we store roadmap structure as a structured note on the Task. Goal hierarchies with parent-child relationships are flattened into separate Task records with a custom parent-goal reference field.

Revolut People engagement survey questions and employee response data have no native Bullhorn object. Survey response scores for aggregate engagement metrics migrate to a Bullhorn custom object (if the Bullhorn edition supports custom objects) or as structured notes on the Candidate record. Individual question-and-answer pairs are stored as a serialised note. Survey metadata (survey name, date, participation rate) is documented separately.

Revolut People time, attendance, PTO, and sick leave data has no Bullhorn equivalent. Bullhorn ATS does not include a leave management or time-tracking module. We export current leave balances and leave type assignments from Revolut People as a structured CSV and hand it off to the customer for import into a dedicated HR system or for manual entry. Leave balance data is not written to Bullhorn as part of the standard migration scope.

Revolut People pay grades, position descriptions, and base salary data migrate as Bullhorn Placement custom fields (if Bullhorn CRM or Enterprise tier is in scope) or as Candidate custom fields. Equity vesting data from Revolut People's compensation insights dashboard is exported as a separate dataset and stored as structured notes on the Candidate record; vesting schedules and projection data do not export cleanly and are flagged in the handoff. Pay structure definitions (grade, level, band) map to Bullhorn Placement compensation fields.

Revolut People role-based access controls assign permissions per user and differ from Bullhorn's permission model. We extract role assignments from Revolut People and map them to Bullhorn user roles (recruiter, sales, hiring manager, admin) and permission sets. Bullhorn's division-level access controls are configured during migration. Role mapping is validated with the customer's Bullhorn admin before user provisioning begins.

Revolut People employee documents (contracts, ID copies, offer letters) are not accessible via a documented public API and do not migrate. We generate a file manifest listing each document's original location, associated employee, and document type, and hand this to the customer's admin for manual re-upload to Bullhorn Candidate records post-migration.