Migrate from Pinpoint to Recruit CRM & ATS

Pinpoint Vacancies map to Recruit CRM Jobs as the top-level record. We extract Vacancy title, department, location, employment type, and status fields and create matching Jobs in Recruit CRM via the Jobs API endpoint. The Pinpoint Vacancy ID becomes an external_id field on the Recruit CRM Job for downstream Candidate-to-Job lookups. Vacancies must be created first because Candidate records in Pinpoint are uploaded against existing Vacancies; we enforce this sequencing rigorously.

Pinpoint Candidate records map to Recruit CRM Candidates. We migrate name, email, phone, address, social profiles, custom properties, and document attachments. Custom fields beyond Pinpoint's standard template require explicit field mapping against Recruit CRM's Custom Fields API, with field type translation (text to text, date to date, dropdown to picklist). We deduplicate by email match against existing Recruit CRM records before insert.

Pinpoint Applications (the join table between Candidate and Vacancy) map to Recruit CRM Applications. We preserve the Candidate-to-Job relationship by resolving the Pinpoint Vacancy ID to the Recruit CRM Job external_id created in the first migration phase. Application stage, status, source attribution, and rejection reason migrate as fields. Source attribution data from Pinpoint may require cleanup if the source field contains free-text or mixed-format values.

Pinpoint Scorecards are structured evaluation forms attached to Applications by interviewers. We migrate the scorecard template structure and individual evaluator ratings as JSON-serialized fields within a Recruit CRM custom field or as linked Note records depending on the scorecard complexity. Where scorecards reference specific Candidates or Vacancies, we resolve those IDs to Recruit CRM Candidate and Job IDs before insert. Complex nested scorecard sections may require truncation or reformatting to fit Recruit CRM's field structure.

Pinpoint Interview records (date, time, interviewer, format, status) map to Recruit CRM Meeting records linked to the Application or Candidate. We preserve interview duration, format (video or in-person), interviewer name, and scheduling status. Any scheduling link URLs in Pinpoint migrate as a text field; external calendar links are not guaranteed to function post-migration and should be validated by the customer's admin.

Pinpoint Offer records bundle salary, start date, conditional clauses, and status. We migrate Offer records with their key terms into Recruit CRM's Offer object. Complex conditional clauses and bespoke offer letter documents migrate as attached files; the document content itself transfers if PDF export is enabled in Pinpoint (requires CSM opt-in). Offer status history migrates as a text log field if available.

Pinpoint Reference Checks (status, responses, attached notes, ratings) map to Recruit CRM Reference records associated with the Candidate. Custom reference check templates that use non-standard field structures may require field mapping to Recruit CRM's default reference fields. Reference check outcome ratings migrate as numeric or picklist fields depending on Recruit CRM's configured scale.

Pinpoint Job Postings track where a Vacancy was distributed (internal careers page, Indeed, LinkedIn, third-party boards). We migrate posting status and destination as fields on the Recruit CRM Job record. Third-party job board posting IDs and granular posting metrics (impressions, clicks) may not map directly and are migrated as notes or skipped depending on data availability.

Pinpoint custom fields added to the New Job form migrate to Recruit CRM custom fields created via the Custom Fields API before migration begins. We define field type, required/optional status, and picklist values during the schema phase. Custom fields referencing external systems (e.g., background check IDs, assessment tool scores) require the customer's admin to validate post-migration integration setup.

Pinpoint pipeline reports are aggregate analytics views of vacancy pipeline health. These are report data rather than transactional records and do not migrate as live dashboards. We export pipeline report snapshots as CSV at migration time and deliver them as a structured data package for the customer's admin to rebuild as Recruit CRM reports or import into a BI tool. Active pipeline metrics should be re-created post-migration in Recruit CRM's analytics builder.