Migrate from Talent Ninja to Bullhorn ATS & CRM

Talent Ninja Candidate records map to Bullhorn Candidate. We map standard fields (name, email, phone, address) directly. Talent Ninja custom properties on the Candidate record map to Bullhorn custom fields on the Candidate entity. Where Talent Ninja uses multi-checkbox properties, we map to Bullhorn multi-select picklist or a Custom Object if the data structure warrants a related entity. Skills and tags from Talent Ninja migrate to Bullhorn Skill and Specialty fields or to a Candidate Custom Object depending on the customer's usage pattern.

Talent Ninja Job Postings map to Bullhorn Job Order. The job title, description, requirements, and location fields migrate directly. Talent Ninja's job status (open, closed, draft) maps to Bullhorn's JobOrderStatus field. We preserve the published date and any custom job classification fields as custom fields on the Job Order. Job Orders in Bullhorn are the parent entity for all related Submissions and Placements.

Talent Ninja Application records map to Bullhorn Submission. The submission date, current stage, and stage history migrate as custom fields or as a Submission History Custom Object if the customer relies on multi-stage progression for reporting. We resolve the Candidate reference and Job Order reference before inserting Submissions to satisfy Bullhorn's foreign-key requirements.

Talent Ninja hiring stages (applied, screening, interview, offer, hired, rejected) map to Bullhorn Submission status values. We configure the Bullhorn Job Order's status order to match the customer's Talent Ninja stage sequence during migration setup. Any custom stages beyond the standard five become custom Submission Status values configurable in Bullhorn Field Mappings.

Talent Ninja does not have a dedicated client entity; client information lives as attributes on Job Postings. Bullhorn separates Client Corporation (the employing company) from Contact (the hiring manager or recruiter at that company). We extract unique employer entities from Talent Ninja Job Postings and create Client Corporation records, then extract staffing contact information to create related Contact records with a ClientCorporation lookup.

Talent Ninja interview scores and evaluation notes migrate to a Bullhorn Custom Object (Interview Evaluation) linked to the Submission via a lookup relationship. We pre-create the Custom Object schema with fields for evaluator name, score, date, and notes before migration. Bullhorn Custom Objects allow this entity to extend Candidate, JobOrder, Submission, and Placement as needed.

Talent Ninja offer details (salary, start date, benefits, offer status) map to Bullhorn Placement. Bullhorn Placement is the canonical record for a hired candidate and includes billing rate, commission, and onboarding status fields that Talent Ninja does not model. We populate Placement fields from Talent Ninja offer data and set the Placement date to the offered start date.

Talent Ninja work history entries (employer, title, dates, description) map to Bullhorn Candidate Work History sub-records. We maintain the chronological ordering by setting start and end dates during import. Bullhorn's Work History entity is a separate related entity from the Candidate itself, requiring parent-record resolution during migration.

Talent Ninja education records (institution, degree, field, graduation date) migrate to Bullhorn Candidate Education. We resolve the parent Candidate by email dedupe during migration. Education records attach to the Candidate as a related entity with degree level mapped to the standard degree picklist.

Talent Ninja users (recruiters, sourcers, admins) map to Bullhorn User records. We match by email address. Any Talent Ninja user without a corresponding Bullhorn User goes to a reconciliation queue for the customer's Bullhorn admin to provision before record import completes, because OwnerId references on Candidate, Job Order, and Submission must resolve to an active User.

Talent Ninja custom properties that are simple key-value pairs map to Bullhorn custom fields on the appropriate entity. Custom properties with multi-value, nested, or entity-reference semantics map to Bullhorn Custom Objects. We design the Custom Object schema during scoping, pre-create it via Bullhorn metadata API, and then load the data. Bullhorn restricts Custom Component Fields to integration use; we avoid them for general client data and use supported Custom Objects instead.

Talent Ninja tags on Candidate records migrate to Bullhorn Specialty fields or a multi-select picklist depending on tag cardinality. We inventory the distinct tag values during scoping and recommend a field type that balances usability in Bullhorn's UI with migration fidelity. Tags used for sourcing attribution migrate to a custom field rather than Bullhorn's standard Specialty to preserve the sourcing signal.