Migrate from Talent Connects to Bullhorn ATS & CRM

Talent Connects Jobs (title, description, status, pipeline stages) map to Bullhorn JobOrder records via the Bullhorn Jobs API endpoint. The job description HTML migrates as a text blob to Bullhorn's description field. We preserve the original job status (Open, Paused, Closed) as a JobOrder status value. Bullhorn's JobOrder object includes additional fields (skills, certifications, tax terms) that may require custom field pre-creation in Bullhorn if Talent Connects stores equivalent data as custom properties.

Talent Connects Candidate records map directly to Bullhorn Candidate. Standard fields (firstName, lastName, email, phone, resume file) migrate to Bullhorn Candidate with the resume uploaded as a ContentDocument and linked via ContentDocumentLink. Bullhorn's Candidate object is the parent for all application history — we resolve the Candidate-to-JobOrder relationship through the JobSubmission object.

Each Talent Connects application (Candidate applied to a Job) maps to a Bullhorn JobSubmission record that links the Candidate to the JobOrder. The application timestamp migrates as dateAdded; the application status (Applied, Screening, Interview, Offer, Hired, Rejected) maps to Bullhorn JobSubmission status values. We resolve CandidateID and JobOrderID references at migration time before inserting JobSubmission records.

Talent Connects Interview records (date, attendees, outcome notes) stored as activity records map to Bullhorn Note records linked to the corresponding JobSubmission or Candidate. Bullhorn does not have a native Interview scheduling object — interview activity is tracked as Note or Task with a custom interview-type flag. The calendar sync and video interview links from Talent Connects do not migrate; we document them as integration setup items for Bullhorn's Microsoft Office 365 calendar integration post-migration.

Talent Pool is an Enterprise-only feature in Talent Connects that stores passive candidate sourcing metadata separate from active applications. Bullhorn has no native Talent Pool object. We migrate Talent Pool records as Candidate records with a custom field tc_talent_pool__c set to true and tc_sourcing_date__c carrying the original sourcing timestamp. This preserves the passive-sourcing context without losing the metadata, though the Talent Pool workflow itself must be recreated in Bullhorn using Saved Lists or a custom object.

Talent Connects generates hosted career pages from Job data with template, branding, and URL settings stored as system-generated configuration. Bullhorn Career Portal is a separate product with its own setup. We do not migrate career page templates as data — they cannot be exported from Talent Connects. We deliver a written inventory of the current career page URLs, template sections, and branding settings from Talent Connects for the customer's admin to reconfigure in Bullhorn Career Portal post-migration.

Talent Connects user records (name, email, role) on both Growth and Enterprise tiers map to Bullhorn Corporate User accounts. We resolve by email match during import. Role and permission mapping requires pre-migration coordination — Talent Connects' single-role Growth tier maps to Bullhorn Standard User, while Enterprise multi-level permissions map to Bullhorn Corporate User roles and entity-level access controls. Bullhorn user provisioning is a separate admin step coordinated during the owner reconciliation phase.

Talent Connects bulk email campaigns and templates map to Bullhorn Email Template records. Email send history and engagement tracking (open rates, click rates) stored as campaign records do not migrate as Bullhorn does not have a native campaign engagement tracking object equivalent. We deliver a written inventory of the source email templates (subject, body, linked jobs, audience segments) for the customer's Bullhorn admin to rebuild using Bullhorn email template tools. Bullhorn's built-in email tracking via the Outlook Gadget requires separate Office 365 journaling setup post-migration.

The optional AI-Assistant add-on ($49/month) on Talent Connects generates AI-ranked candidate scores and suggested job-description text. These AI-derived signals are not stored as structured exportable fields — they are rendered UI data. We do not migrate AI scores. If the customer wants equivalent candidate ranking signals in Bullhorn, Bullhorn's own Amplify Search & Match product (part of the AI & Automation suite) provides this natively. We flag this gap and recommend an Amplify evaluation during Bullhorn onboarding.

Talent Connects records which job boards (LinkedIn, Indeed, Naukri, custom career pages) a job was distributed to. Bullhorn JobOrder has a postingSites field that tracks publishing destinations. We map the Talent Connects distribution list to Bullhorn postingSites values where equivalents exist (LinkedIn, Indeed), and note any custom career page distributions as a custom field tc_distribution_sites__c for manual re-publishing in Bullhorn.

Talent Connects analytics dashboards (funnel metrics, time-to-hire, source performance) are rendered from internal data stores with no raw data export. We do not attempt to migrate analytics. We instruct the customer to export screenshots of key dashboards before migration day. Bullhorn's built-in reporting (available on Core and above) covers pipeline analytics, placement metrics, and recruiter activity. We deliver a written report mapping document listing each Talent Connects dashboard metric and its Bullhorn equivalent for the admin to rebuild.

Talent Connects custom fields on Jobs and Candidates migrate to Bullhorn custom fields on JobOrder and Candidate. Bullhorn supports custom fields from Starter tier. We pre-create the Bullhorn custom field schema before any record import, matching Talent Connects field types (text, number, date, picklist) to Bullhorn field types. Validation rules and required-field constraints in Bullhorn are reviewed and temporarily adjusted during the migration load phase to prevent record rejection.