Migrate from Pinpoint to Zoho Recruit

Pinpoint Vacancies map to Zoho Recruit Job Openings as the top-level record. We map Vacancy title to Job Opening title, department to Department, location to Location, and status (Open/Closed/On Hold) to Job Opening status. Vacancies must exist in Zoho Recruit before any Candidate or Application import can reference them, so we sequence this as the first import phase. Pinpoint's Vacancy external ID becomes the Job Opening reference number for cross-system reconciliation.

Pinpoint Candidates map to Zoho Recruit Candidates for standard employer use cases. For staffing agencies, Pinpoint Candidates who represent client companies require mapping to Zoho Recruit Clients instead. We determine the split during scoping based on whether the Pinpoint organization uses Candidate for job applicants or client contacts. Candidate name, email, phone, and custom fields map to corresponding Zoho Recruit Candidate fields. Custom fields beyond Pinpoint's standard template require pre-creation in Zoho Recruit (50 custom fields per module on Standard, 300 on Enterprise) before migration.

Pinpoint Applications (the join table linking Candidate to Vacancy) map to Zoho Recruit Job Applications. We re-establish the Candidate-to-Job Opening relationship using the Vacancy identifiers created in phase one. Application stage, status, and source attribution (direct, agency referral, job board) migrate as typed Zoho Recruit fields. Source tracking in Zoho Recruit maps to the Source field on Candidate rather than Application, requiring a field-level redirect during transform.

Pinpoint Scorecards are structured evaluation forms with named criteria and numeric or rating values attached to Applications by interviewers. Zoho Recruit does not expose a native scorecard API, so we migrate scorecard data as custom fields on the Candidate or Job Application record. Each named Pinpoint scorecard criterion (e.g., Technical Skills, Communication, Cultural Fit) becomes a custom field in Zoho Recruit before migration. The overall score migrates as a numeric custom field. We flag that complex scorecard templates with conditional branching cannot be fully replicated in Zoho Recruit without manual rebuild.

Pinpoint Interview records (date, time, interviewer, format, status) map to Zoho Recruit Interview records. Format (video or in-person) maps to the Interview type field. We preserve the interviewer assignment by resolving the Pinpoint interviewer's email against the Zoho Recruit User table. Any scheduling links (Zoom, Teams, Google Meet) migrate as text fields because Zoho Recruit's native scheduling integration is configured post-migration rather than imported.

Pinpoint Offer records (salary, start date, conditional clauses, status) map to Zoho Recruit Job Offers. Key terms migrate as typed fields (annual salary as currency, start date as date, status as picklist). Conditional clauses and bespoke offer letter documents migrate as attachments to the Job Offer record. Zoho Recruit's Offer Letter Templates (50 on Standard, 100 on Enterprise) are a post-migration configuration item; existing Pinpoint templates are documented for manual rebuild.

Pinpoint Reference Check records (status, responses, ratings, notes) map to Zoho Recruit Reference Check records associated with Candidates. Reference check outcomes migrate as structured data. Custom reference check templates require manual rebuild in Zoho Recruit because the template structure does not have an importable API representation. We deliver a written inventory of the source template fields for the customer's admin to configure post-migration.

Pinpoint Job Postings track where a Vacancy has been distributed (internal careers page, Indeed, LinkedIn, other job boards). We migrate posting status and destination as structured data on the Job Opening record in Zoho Recruit. Third-party job board posting IDs and posting performance metrics (views, clicks, applications) are not importable into Zoho Recruit as native fields; we export them as a CSV attachment for the customer's admin to reference in Zoho Recruit's Job Board Posting module post-migration.

Pinpoint Users map to Zoho Recruit Users by email match. Active and inactive status is preserved. Pinpoint's role-based permissions (Admin, Hiring Manager, Recruiter, Interviewer) map to Zoho Recruit's role structure, with the caveat that Zoho Recruit's role granularity is different. We flag any Pinpoint permissions that have no direct Zoho Recruit equivalent during scoping.

Pinpoint Pipeline Reports are aggregate views of vacancy pipeline health and hiring metrics. Zoho Recruit Standard includes Standard Reports and Dashboards while Professional adds Custom Reports. We export Pinpoint pipeline report data as structured CSV at migration time and deliver it as a reference document. The customer rebuilds the reporting views in Zoho Recruit's reporting module post-migration because aggregate report definitions do not have a portable API representation.

Pinpoint custom fields beyond the standard template require explicit field mapping and pre-creation in Zoho Recruit. Zoho Recruit Standard allows 50 custom fields per module; Professional allows 300. We map field types (text, number, date, picklist, checkbox, currency) to their Zoho Recruit equivalents. Fields exceeding the module limit on the customer's target tier are flagged for either consolidation (combining related fields) or manual post-migration entry.

Candidate CVs, resumes, cover letters, offer letter documents, and other file attachments migrate as Zoho Recruit attachments linked to the parent record (Candidate, Job Application, Job Offer). We preserve file names and upload dates. Large file batches are chunked for upload; Zoho Recruit's attachment size limits apply (default 20 MB per file). Pinpoint PDF exports must be confirmed enabled by a Customer Success Manager before we extract attachments; if not yet enabled, CSM approval adds to the critical path.