Migrate from Aperio to Zoho Recruit

Aperio Employee records map directly to Zoho Recruit Candidate records. Core fields migrate as-is: First Name, Last Name, Email, Phone, Department, Job Title, Manager, and Hire Date map to their Zoho Recruit equivalents. Note that Last Name is a mandatory field in Zoho Recruit — any Aperio employee record without a Last Name value requires a placeholder ('Not Provided') before import to avoid record rejection. The Aperio Employee Status (active/inactive/terminated) maps to the Candidate Status picklist.

Aperio Department records with their hierarchy (parent-department references) map to Zoho Recruit Departments module. Department Name and the parent-department relationship preserve as-is. We reconstruct the hierarchy in Zoho Recruit using the Department module's native parent-field structure during import.

Aperio Job Title records are not a standalone object in Zoho Recruit — job titles are stored as a field on the Candidate record. We export the Aperio job title roster and create a custom picklist field Job_Title__c on the Candidate module (50 custom fields allowed on Standard, 300 on Enterprise), populating values from the Aperio roster. If the Aperio organization uses titles as criteria within review templates, those associations are noted in the review template mapping.

Aperio Performance Review records link to Employees and contain structured ratings against competencies, reviewer comments, and cycle metadata. Zoho Recruit has no native performance review object. We map reviews to Candidate Notes (for organizations with fewer than 100 historical reviews, preserving the review period, overall rating, and reviewer name in structured note headers) or to a custom PerformanceReviews module (for organizations with higher review volume, requiring pre-configuration of the custom module with fields for review period, competency ratings, and comments before migration). Review cycle status and dates migrate to custom fields.

Aperio Goal records can be standalone or linked to Performance Reviews and Employees. Goals with parent-child hierarchies export from Aperio as flat records with parent_goal_id fields. We extract all goal_id and parent_goal_id pairs, reconstruct the hierarchy in the destination as nested Note titles (e.g., 'Goal: Q1 Sales Target > Q1 North Region') or as structured fields on a custom Goals module, and flag any circular references or orphaned child goals detected during reconstruction. Goal status, due date, and progress percentage migrate as custom fields.

Aperio goal parent-child relationships do not self-describe in CSV export — the hierarchy is implicit in parent_goal_id references. We run a pre-migration analysis pass to extract all goal_id and parent_goal_id pairs, detect any circular references or orphaned child goals, and produce a mapping table of goal hierarchy links. These are reconstructed in Zoho Recruit as a custom module with a self-lookup field or as structured Note relationships on the Candidate record.

Aperio competency libraries define the rating scales and competency definitions used within reviews and templates. Zoho Recruit has no native competency object. We export competency definitions and their associated rating scales and map them to a custom Competencies module in Zoho Recruit, or to a picklist field on the custom PerformanceReviews module if that structure is used. Custom competency definitions are flagged if their rating scale values do not map cleanly to the destination picklist options.

Aperio Development Plan records track growth actions linked to employees and tied to review outcomes, with associated milestones and timelines. Zoho Recruit has no development plan equivalent. We map development plans to Candidate Notes with structured headers (plan title, start date, end date, associated review cycle) or to a custom DevelopmentPlans module pre-configured with fields for action items, milestones, and timelines. The association to the original Performance Review record is preserved via a custom lookup field if the custom module infrastructure is used.

Aperio Review Templates define the structure of reviews including competency sections, rating scales, and mandatory fields. Zoho Recruit does not have a review template concept for performance management. We export the template configurations and document them in a written template inventory. If the customer uses Zoho Recruit's custom module infrastructure for performance reviews, the template structure can inform the field layout of the custom module, but template reuse and automated assignment are not natively supported in Zoho Recruit without manual rebuild.

Aperio Review Cycles are the temporal container for batches of reviews, with start and end dates, status, and associated templates. Zoho Recruit has no native review cycle concept. For organizations migrating performance reviews, we map review cycle metadata (name, start date, end date, status, associated template) to a custom ReviewCycles module with start_date, end_date, status, and template_name fields. If the organization also uses Zoho Recruit for job openings, the Job Opening module's structure is noted as a separate use case.

Aperio custom fields on Reviews, Goals, and Development Plans require identification during discovery, as they do not self-document in CSV exports. We extract all active custom field definitions, their data types (text, picklist, multi-select, date, numeric), and their value sets during scoping, then map them to equivalent Zoho Recruit custom fields on the respective custom modules. Note that Zoho Recruit Standard edition allows 50 custom fields per module while Enterprise allows 300 — if the Aperio custom field count exceeds the destination plan limit, we flag the overflow fields for customer resolution before loading. Custom fields are not available in the Zoho Recruit Free edition.

Aperio organizations commonly add custom fields to Performance Reviews, Goals, and Development Plans with picklist or multi-select values that differ from platform defaults. These do not self-document in CSV export. We identify all custom field definitions during discovery scoping, export sample values, and map them explicitly to Zoho Recruit field definitions by type. Picklist and multi-select fields map to Zoho Recruit picklist and multi-select picklist types with value sets created before data import. Text fields map to Zoho Recruit text fields. Where value sets differ significantly between Aperio and Zoho Recruit, we flag the discrepancy for customer resolution before loading.