Migrate from Pinpoint to Crelate

Pinpoint Vacancies map to Crelate Opportunities. The Vacancy title becomes the Opportunity name, department and location map to custom Opportunity fields, and the Vacancy status (open, paused, closed) maps to Crelate's Opportunity status values. Pinpoint Vacancies must exist in Crelate before any Candidate or Application records are imported because Crelate links candidates to Opportunities rather than maintaining a separate join table. We create all Opportunities first, capture their Crelate Opportunity IDs, then use those IDs when importing Candidate-to-Vacancy relationships.

Pinpoint Candidate records map to Crelate Contacts. Name, email, phone, address, and custom properties migrate to Crelate Contact fields. Custom properties beyond Pinpoint's standard template require pre-creation of Crelate custom fields before migration. Any Candidate documents (CVs, resumes) migrate as Crelate Resume Toolbox attachments linked to the Contact record via ContentDocumentLink. Candidates without an assigned Vacancy are imported first into a holding status and linked to the appropriate Opportunity once that is created.

Pinpoint Applications are the join table between Candidate and Vacancy. Crelate does not have a direct Application object — candidates are linked to Opportunities via the candidate pipeline view. We reconstruct the application relationship by mapping each Pinpoint Application to a Crelate candidate record with an Opportunity association, carrying the application stage, source attribution (direct, agency, referral), and submission timestamp. The Candidate-Vacancy pairing resolves to Contact-Opportunity linkage in Crelate's data model.

Pinpoint Scorecards are structured evaluation forms with rating fields attached to Applications. Crelate does not have a native Scorecard object — evaluations are handled via Activity Forms or custom fields on the Contact or Opportunity. We transform Pinpoint scorecard templates into Crelate Activity Forms during configuration, and individual evaluator ratings migrate as structured custom field data on the Contact record. Where scorecards reference specific interviewers or rating criteria, we map those to Crelate User records and custom picklist values respectively. Complex scorecard templates with conditional logic require manual rebuild in Crelate's Activity Form builder post-migration.

Pinpoint Job Postings track where a Vacancy has been distributed (internal careers page, Indeed, LinkedIn, Monster, etc.) with posting status and destination tracking. Crelate has native job board integrations (Indeed, Dice, CareerBuilder, Monster, LinkedIn) configured in its Settings. We migrate the posting destination and status as custom fields on the Crelate Opportunity. Some third-party job board posting IDs and granular posting metrics (impressions, clicks) do not have direct equivalents in Crelate's integration data and are treated as informational fields. Active posting distributions are re-enabled in Crelate's job board integration settings post-migration.

Pinpoint Offers bundle salary, start date, conditional clauses, and status. We migrate Offer records as structured data mapped to Crelate Opportunity custom fields (offered salary, proposed start date, offer status, conditional terms). Offer letter documents migrate as ContentDocument attached to the Opportunity. Complex conditional clauses and bespoke offer letter formatting require manual review post-migration; we flag any offer record with non-standard terms in the migration report for admin attention.

Pinpoint Interviews are individual scheduled events with date, time, interviewer, format (video or in-person), and status. We migrate Interview records as Crelate Event records with StartDateTime, EndDateTime, and Location preserved. Interview format maps to a custom field on the Event record. Scheduling links (Calendly, Zoom, Teams) are preserved as text fields on the Event. Interview status from Pinpoint maps to the Crelate Event status field. Interviewer assignment migrates by resolving the Pinpoint interviewer's email to the corresponding Crelate User record.

Pinpoint Reference Checks carry status (pending, completed), responses, and any attached notes or ratings. We migrate Reference Check records as custom fields on the Crelate Contact (reference check status, overall rating, date completed) and migrate any response text as an Activity Note attached to the Contact. Custom reference check templates with non-standard question sets require manual rebuild in Crelate's Activity Form builder post-migration.

Pinpoint Candidates may have an employer or current company association. We extract employer data from Candidate records and map it to Crelate Company records. Crelate requires Companies to be created before Contacts can be fully associated with them via a lookup. We sequence the import so that any Crelate Companies derived from Candidate employer data are created first, then Contacts are imported with the Company lookup resolved. If Pinpoint does not have a distinct Company entity, we create Crelate Companies from Candidate employer text fields and flag duplicates during deduplication.

Pinpoint Owners (hiring managers, recruiters, TA team members) map to Crelate User records. We resolve Owners by email match. Any Pinpoint Owner without a matching Crelate User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Pinpoint Owners (departed employees) are mapped to an inactive Crelate User record to preserve the assignment history on migrated records.

Pinpoint Pipeline Reports are aggregate views of vacancy pipeline health and hiring metrics. We export pipeline report data as structured CSV at migration time and deliver it as a reference document. Crelate's Advanced Reports and Analytics module provides native reporting on pipeline health, recruiter performance, and sourcing efficiency, but Pinpoint's specific report configurations do not migrate. We document the metrics present in each Pinpoint pipeline report so the customer's admin can rebuild equivalent reports in Crelate's report builder post-migration.

Pinpoint custom fields on Candidates, Vacancies, Applications, and Scorecards migrate to Crelate custom fields on the corresponding core records (Contacts, Opportunities). Custom field creation in Crelate must precede data import. Crelate supports Text, Number (Integer), Number (Decimal), Number (Money), Date, Boolean, Picklist, and Multi-Select Picklist types. We map each Pinpoint custom field type to the nearest Crelate equivalent. Lookup fields referencing other Pinpoint objects require manual configuration in Crelate as Crelate's lookup relationships must be explicitly defined in Settings before import.