Migrate from Pinpoint to Bullhorn ATS & CRM

Pinpoint Vacancies map directly to Bullhorn JobOrder records. We migrate title, department, location, employment type, salary range, and status fields. The Bullhorn JobOrder requires a ClientCorporation reference, which Pinpoint does not provide as a separate object; we either derive the client from the Vacancy name or workspace context, or create ClientCorporation records from the Vacancy workspace during migration. Status values (open, on-hold, filled, cancelled) map to Bullhorn JobOrder status with a custom field pinpoint_original_status__c preserving the source value.

Pinpoint Candidate records map to Bullhorn Candidate records with a direct field-to-field mapping for name, email, phone, LinkedIn URL, and custom properties. Pinpoint custom fields outside the standard template require Bullhorn custom field pre-creation before migration. We validate email addresses and flag duplicates using Bullhorn's dedupe rules during import so that the same candidate appearing across multiple Vacancies does not create duplicate Candidate records.

Pinpoint Applications (the join table linking Candidate to Vacancy) map to Bullhorn JobSubmission. We resolve the CandidateId and JobOrderId references during migration using the lookup IDs established during Vacancy and Candidate import. Application status maps to JobSubmission status; source attribution (direct, agency, job board) migrates as a custom field pinpoint_application_source__c on JobSubmission.

Pinpoint Scorecards are structured evaluation forms attached to Applications by interviewers. Bullhorn does not have a native Scorecard object; we migrate Scorecard ratings to Bullhorn CandidateReference records, mapping each evaluator's rating to a custom field on CandidateReference. Scorecard template structure (rating criteria, weightings) migrates as a structured note attached to the JobSubmission for the customer's Bullhorn admin to rebuild as a custom object or intake form if needed.

Pinpoint Interview records (date, time, interviewer, format, status) map to the Interview section of Bullhorn CandidateReference. Format (video, in-person, phone) migrates as a text field; interviewer name and scheduling notes migrate as structured fields. Bullhorn's separate scheduling integration (Bullhorn Scheduling or Calendly connector) replaces Pinpoint's native scheduling for future interviews.

Pinpoint Offer records (salary, start date, conditional clauses, status) map to Bullhorn Placement records with a custom field pinpoint_offer_status__c tracking whether the offer is pending, accepted, declined, or withdrawn. Complex conditional clauses and bespoke offer letter documents require validation; offer letter PDFs migrate as ContentDocument attached to the Placement. Once a Placement is confirmed, it transitions to an active placement record in Bullhorn's placement lifecycle.

Pinpoint Reference Check records (status, responses, ratings, notes) map to the Reference Check section of Bullhorn CandidateReference. Reference contact name, relationship, and response outcome migrate as structured fields. Custom reference check templates from Pinpoint migrate as a template note for the customer's Bullhorn admin to configure as Bullhorn forms post-migration.

Pinpoint Job Postings track where a Vacancy has been distributed (internal careers page, Indeed, LinkedIn, etc.). Bullhorn JobOrder does not have a native multi-destination posting object; we migrate posting status and destination list as a multi-select picklist field on JobOrder (pinpoint_posting_destinations__c). Third-party job board posting IDs and engagement metrics (impressions, clicks) do not transfer because Bullhorn does not have an equivalent metric field.

Pinpoint pipeline reports are aggregate views of vacancy pipeline health and hiring metrics. Bullhorn has a native reporting engine with standard reports for pipeline health, submission activity, and placement analytics. We export Pinpoint pipeline report data as structured CSV at the time of migration. These are treated as report data snapshots for the customer's analytics team to manually recreate in Bullhorn's reporting environment post-migration.

Pinpoint Vacancies have workspace and team associations that govern who can view and edit them. Bullhorn JobOrder has an Owner (User) and supports team-based access via Bullhorn's Share functionality or Bullhorn Teams. We map the Pinpoint workspace owner to Bullhorn User by email match and configure JobOrder sharing rules to replicate the workspace access scope.

Pinpoint CVs, resumes, and attachments on Candidate records migrate as Bullhorn ContentVersion and ContentDocument records linked to the Candidate via ContentDocumentLink. We extract documents from Pinpoint's export, validate file formats, and attach them to the corresponding Bullhorn Candidate record using Bullhorn's REST API file upload endpoint.

Pinpoint custom Candidate properties beyond the standard template require Bullhorn custom fields pre-created on the Candidate object before migration. We work with the customer during scoping to identify all active custom properties, map them to Bullhorn field types (text, picklist, number, date, checkbox), and deploy the custom schema into a Bullhorn Sandbox for validation before production migration.