Migrate from PCRecruiter to Zoho Recruit

PCRecruiter People records with candidate roles map directly to Zoho Recruit Candidate. The primary challenge is records that serve dual roles as both candidate and client. We split these at migration time: the candidate portion migrates as a Candidate record, and a corresponding Client record is created with a cross-reference preserved in a custom field pcr_person_id__c. Last Name is mandatory in Zoho Recruit; any PCRecruiter Person record without a last name receives a Last Name value of 'Not Provided' per Zoho's import requirements.

PCRecruiter People records marked as both candidate and client split into a Zoho Recruit Candidate record and a Zoho Recruit Client record. The client side preserves company affiliation, and the candidate side links to the same Client via the Client Name lookup. We flag these dual-role records during extraction and confirm the split strategy with the customer during scoping before the first import pass.

PCRecruiter Company records map to Zoho Recruit Client. The Company record is the parent entity for associated People and Placements. We extract the full company profile including address, industry, and client-specific fields, then import as a Client before any associated People or Position records to satisfy Zoho's dependency order. Companies without a Client contact person receive a placeholder primary contact created during migration.

PCRecruiter Position records map to Zoho Recruit Job Opening. Position pipeline stage definitions (step names, order, and any associated requirements) map to Zoho Job Opening custom stage fields if the Professional or Enterprise tier is selected. Standard tier uses Zoho's built-in pipeline stages. The Position's status (Open, On Hold, Filled, Cancelled) maps directly to Zoho Job Opening status values.

PCRecruiter configurable pipeline templates are extracted during scoping. On Zoho Professional or Enterprise, we configure matching stage names and probabilities as custom pipeline stages in the Job Opening module. On Standard tier, stages are limited to Zoho's built-in pipeline; we document the delta between PCRecruiter stage definitions and Zoho's default stages so the customer's admin can adjust hiring workflows accordingly.

PCRecruiter Placement records represent successful hires and contain billing information, start dates, employee details, and client associations. We migrate Placement data to a Candidate record linked to the hiring Job Opening with Hired status, and the billing details (fee, start date, employee name) are preserved in custom fields on the Candidate record since Zoho Recruit does not have a dedicated Placement object equivalent.

PCRecruiter Activity records (calls, emails, meetings, tasks, notes) logged against People or Positions map to Zoho Recruit's corresponding activity types. Activity history preserves timestamps, descriptions, and owner assignments. We map PCRecruiter activity types to Zoho's Tasks, Events, or Notes based on the activity subtype detected during extraction. Large activity histories require chunked import to respect Zoho's API rate limits.

Resume files and documents associated with People, Positions, or Companies migrate via Zoho's document attachment API. We extract attachment binaries from PCRecruiter's attachments endpoint, map each file to its parent record (Candidate, Job Opening, or Client), and preserve the original filename and association. Binary attachments over 10 MB are flagged for manual handoff since Zoho's attachment API has size constraints.

PCRecruiter tags on People, Companies, and Positions migrate to Zoho Recruit Tags. Tags are a flat taxonomy in both systems, so the mapping is direct. We extract the full tag list from each source module, import as Zoho Tags, and associate them with the corresponding migrated records. Tags used for candidate segmentation map to Zoho Candidate Tags; tags used for job categorization map to Job Opening Tags.

PCRecruiter custom fields on Person, Company, Position, and Placement records require pre-creation in Zoho Recruit before data import. We extract the full custom field schema (field name, type, and picklist options) from the PCRecruiter account, compare against Zoho's supported field types (text, picklist, date, number, checkbox), and create matching custom fields in Zoho during the pre-migration phase. Dropdown picklist values are translated explicitly where PCRecruiter options differ from Zoho defaults.

PCRecruiter User accounts map to Zoho Recruit Users by email match. We extract every distinct owner referenced on People, Company, Position, and Placement records and cross-reference against the destination Zoho Recruit account's User list. Any owner without a matching Zoho User is held in a reconciliation queue; the customer's admin provisions missing users in Zoho before record import resumes since OwnerId lookups are required on standard Zoho records.

PCRecruiter accounts with multiple independent databases require an explicit consolidation strategy before migration. We offer two paths: consolidate all databases into a single Zoho Recruit account using Zoho Departments for isolation, or migrate each database to a separate Zoho Recruit workspace account. The customer confirms the strategy during scoping. Each database's custom field schema, pipeline templates, and user roles are treated as separate migration scopes with independent field mapping documents.