Migrate from Pinpoint to BambooHR

Pinpoint Vacancies map to BambooHR Job records if the customer has BambooHR ATS licensed. If BambooHR ATS is not part of the scope, Vacancy data (title, department, location, status) is mapped to a structured CSV inventory delivered to the customer's admin for manual entry or as custom fields on a Hiring Tracker object in BambooHR. Vacancies must be resolved first because Candidates and Applications reference Vacancy identifiers during export. Open Vacancies with active pipelines are inventoried but not fully migrated to BambooHR ATS without an explicit ATS scope decision.

Pinpoint Candidates with a final Hire decision map to BambooHR Employee records. The mapping uses Candidate name, email, phone, and address fields to populate BambooHR's standard Employee fields (firstName, lastName, workEmail, workPhone, and address fields). Custom Candidate properties from Pinpoint that have no standard BambooHR equivalent (such as source channel, referral type, or screening score) are mapped to BambooHR custom fields created in the destination account before import. Candidates who were not hired (rejected, withdrawn, or disqualified) are inventoried as a separate record set; they do not become Employees in BambooHR by default unless the customer requests otherwise.

Pinpoint Applications are the join table linking Candidates to Vacancies with stage, status, and source attribution. For hired Candidates, the Application captures the Vacancy they accepted and their source (direct, agency, referral, job board). This data is mapped to a combination of BambooHR Employee fields and a custom Employment History table: the source field maps to a custom field hireSource__c, and the accepted Vacancy title maps to jobTitle or a custom field originalVacancyTitle__c. The Application stage progression is preserved as an audit trail rather than an active pipeline state.

Pinpoint Scorecards are structured evaluation forms attached to Applications by interviewers. We migrate the scorecard outcome — evaluator name, rating, and written feedback — as notes attached to the BambooHR Employee record. If the customer uses a consistent scorecard template across Vacancies, we map specific rating fields to named custom fields on the Employee (interviewRating_hiringManager__c, interviewRating_recruiter__c) to enable reporting on evaluation outcomes post-migration.

Pinpoint Offers bundle salary, start date, conditional clauses, and status. We map salary to BambooHR's payRate or a custom pay fields section, start date to the Employee hireDate field, and conditional clause outcomes (background check passed, drug screen completed) to custom fields or the onboarding checklist. Bespoke offer letter PDFs are attached to the Employee record via BambooHR's document attachment on the onboarding tab. Complex conditional clauses are flagged in the migration inventory for the customer's HR admin to review post-migration.

Pinpoint Interview records are standalone scheduled events with date, time, interviewer, format, and status. These are hiring-specific records that do not map to any standard BambooHR object. We export interview records as a structured data set in the migration inventory for the customer's records, but they do not become part of the BambooHR HRIS. If BambooHR ATS is in scope, interview scheduling would be rebuilt using BambooHR ATS interview tools rather than carried over from Pinpoint.

Pinpoint Reference Checks carry status, responses, and any attached notes or ratings from nominated referees. We map reference check status (pending, completed, passed, failed) and high-level outcomes to a custom referenceCheckStatus__c field on the Employee record. Full referee response text migrates as notes attached to the Employee. Custom reference check templates do not carry over; BambooHR's onboarding checklist tool replaces the reference check template workflow.

Pinpoint Job Postings track where a Vacancy was distributed — internal careers page, Indeed, LinkedIn, or other job boards — with posting status and posting metrics. We export posting destination and status as a structured inventory (CSV) but do not create records in BambooHR because BambooHR HRIS has no Job Posting object. If BambooHR ATS is in scope, job postings are created fresh in BambooHR ATS rather than imported from Pinpoint.

Pinpoint custom Candidate properties beyond the standard name/email/phone template require explicit mapping to BambooHR custom fields. We use BambooHR's Custom Field Builder to pre-create equivalent fields before import: short answer Pinpoint properties map to BambooHR Short Answer fields; list-based properties map to Single-Select or Multi-Select List fields depending on the Pinpoint field type. We confirm field creation and placement (tab and section) with the customer during scoping. Custom fields do not sync with BambooHR integrations, so any downstream automation relying on custom fields is noted for the admin to reconfigure post-migration.

Pinpoint Owners (recruiters and hiring managers) who are active in BambooHR as Employees are mapped by email match. Owner name and email are preserved in a custom field recruitingOwner__c on the Candidate record during import. Any Pinpoint Owner without a matching BambooHR Employee is flagged in the reconciliation report for the customer's admin to provision or map manually.