Migrate from Recruitly to Bullhorn ATS & CRM

Recruitly Candidate records map directly to Bullhorn Candidate. Standard fields (firstName, lastName, email, phone, skills, source, status) transfer via REST API. Custom fields on Candidate require a Bullhorn Support ticket to create customObject1-10 schema before import; we pre-create the custom object definitions during discovery and submit the Custom Object Setup Sheet to Bullhorn Support before the migration phase begins. CV and resume attachments export from Recruitly's Export Data module and attach as ContentDocument records on the Bullhorn Candidate.

Recruitly Contacts (managed under the Sales module) map to Bullhorn ClientContact. The contact's associated Recruitly Company record maps to a Bullhorn ClientCorporation, and the ClientContact.clientCorporation lookup is resolved at import time. Email, phone, title, and owner fields map directly. Recruitly's contact record limits (200 Free, 5,000 Solo, 25,000+ Professional) do not apply at Bullhorn, removing a constraint that often surfaces after migration scoping.

Recruitly Companies map to Bullhorn ClientCorporation. This mapping requires explicit field extraction from the customer's live Recruitly Companies module because the column configuration can include fields from Sales Analytics, Recruiting Analytics, Billing, General, Recent Activities, and Custom field groups. We extract the full visible column list before export and map each to a corresponding Bullhorn ClientCorporation field. Fields without a Bullhorn equivalent become custom fields on ClientCorporation, subject to the 55-field custom object limit if they exceed standard field capacity.

Recruitly Jobs map to Bullhorn JobOrder. The Recruitly job status (open, filled, on hold, cancelled) maps to Bullhorn's jobStatus field. Job requirements, description, and board distribution settings transfer as custom fields or standard JobOrder text fields. Recruitly's tier-based job limits (5 Free, 25 Solo, unlimited Professional) do not apply at Bullhorn, so open job counts above Recruitly Professional limits can be migrated without tier upgrades.

Recruitly Placements map to Bullhorn Placement. The full lifecycle from offer acceptance through onboarding, guarantee period, and commission tracks as Bullhorn Placement records with corresponding Candidate, JobOrder, and ClientContact lookups. Placement-to-invoice linkage is preserved by mapping Recruitly invoice references to Bullhorn Billing or third-party billing system fields; if Bullhorn Billing is not in scope, we flag the invoice mapping for manual review during cutover. Commission rates and guarantee period details transfer as custom fields on Placement.

Recruitly candidate pipelines are structured with stages tied to Jobs. Bullhorn does not have a native pipeline Kanban for candidates in the same way Recruitly does; candidate progression through stages maps to JobOrder status values or to a custom pipeline field that we create during Bullhorn schema setup. We preserve stage names, candidate order within stages, and stage-to-stage movement history where available via the Recruitly API. The mapping is configured during discovery and validated in a Bullhorn Sandbox before production migration.

Recruitly logs engagement activities on Candidates and Contacts as Recent Activities. We export Recent Activities fields from Recruitly and map them to Bullhorn Note, Task (with TaskSubtype), and Appointment (Event) records. The parent record lookup (candidateID or clientContactID) is resolved at migration time so that activities attach to the correct Bullhorn record. Bullhorn's REST API supports notes, tasks, and appointments via the engagement and activity endpoints; we use batch inserts to manage volume. Bullhorn Plugin documentation confirms activities, notes, and appointments are importable objects.

Recruitly Folders and Saved Searches are soft-organisation constructs that do not have a direct Bullhorn equivalent. We export the underlying record sets rather than the folder structure itself, and tag migrated records with the folder name as a custom Candidate or Contact field. We deliver a written reference document mapping each Recruitly folder to the set of Candidate IDs it contained, so the Bullhorn admin can recreate groupings or note which candidates require re-tagging.

Recruitly Outreach Campaigns (email sequences with templates, recipient lists, send history, and open/click metrics) do not migrate as functional campaigns to Bullhorn because Bullhorn's cadence and sequencing features live in Bullhorn Automation (Herefish), a separate add-on. We export campaign templates as reference documents and map recipient lists to Bullhorn Candidate records with a custom campaign-source field. A Bullhorn admin rebuilds the cadence logic in Herefish post-migration. Recruitly's per-tier recipient limits (100 Free, 500 Solo, unlimited Professional) do not apply at Bullhorn.

Recruitly User records and Owner assignments on Candidates, Jobs, and Placements map to Bullhorn BullhornUser. We resolve owners by email match. Any Recruitly Owner without a matching BullhornUser goes to a reconciliation queue for the customer's Bullhorn admin to provision before record import resumes. Inactive Recruitly users are mapped to inactive BullhornUser records to preserve assignment history without granting active login access.

CVs, cover letters, and supporting documents attached to Recruitly Candidates and Jobs export from the Recruitly Export Data module (Export Data privilege required) and migrate as Bullhorn ContentDocument records linked via ContentDocumentLink to the parent Candidate or JobOrder. Document format conversion is applied where Recruitly's branded CV format (PDF with watermarking) is not natively supported in Bullhorn; we convert to standard PDF and preserve the original as a secondary attachment if the customer requests.

Recruitly placement-linked invoices with line items, payment status, and trust account references require manual mapping review because billing workflows differ significantly between platforms. If Bullhorn Billing or Bullhorn One is in scope, we map invoice records to the Bullhorn Billing entity model. If not, we deliver a written invoice mapping reference and flag the records that require manual entry or third-party accounting system reconciliation post-migration. This is consistently the highest-touch object in the migration scope.

Recruitly custom fields across all major objects map to Bullhorn customObject1 through customObject10. Bullhorn requires a Support ticket with a completed Custom Object Setup Sheet specifying field display name, description, hint, required status, edit type (text, drop-down, checkbox, picker, etc.), and field values for each custom field. Bullhorn editions restrict the number of searchable custom objects: Growth/Enterprise allows 10 custom objects with 55 fields each; ATS Growth has none. We pre-scope custom field count against the target Bullhorn edition during discovery.