Migrate from Personio to Zoho Recruit

Personio recruiting positions map to Zoho Recruit Job Openings. The position title, department, location, status (open/closed/draft), and hiring manager transfer directly. We resolve the Personio hiring_manager attribute to a Zoho Recruit User by email match during import. Custom attributes on the recruiting position (such as employment type, remote policy, or salary band) transfer as custom fields if enumerated during scoping; Zoho Recruit Professional and Enterprise support up to 300 custom fields per module.

Personio applications map to Zoho Recruit Candidates. The candidate name, email, phone, source, current stage in the pipeline, and application date transfer directly. The Personio application status (new/applied/screening/interview/offer/hired/rejected) maps to Zoho Recruit's candidate status field with the customer choosing the specific status value mapping during scoping. Notes and attachments on the application migrate as Zoho Recruit Notes and file attachments respectively.

Custom attributes on Personio job application forms are not accessible via the Personio API. During scoping, we explicitly request the customer to provide the list of all custom application form fields and their data so we can map them manually into Zoho Recruit custom fields. Without this step, custom candidate data is missed entirely. We create the corresponding custom fields in Zoho Recruit before migration and map each attribute value by candidate email match. This enumeration step adds one to three days to discovery but is required for data completeness.

Personio departments and sub-departments export as a flat or nested list. They map directly to Zoho Recruit Departments, which are used to categorize Job Openings and to configure department-based access controls. We preserve the org hierarchy by creating parent-child Department relationships in Zoho Recruit matching the Personio structure.

Personio employees who originated from a recruiting application are the inverse of the typical migration direction. We extract the employment_start_date and original_application_id from Personio Employee records and flag candidates in Zoho Recruit who have been hired. If the customer uses Zoho People alongside Zoho Recruit, we map hired candidates to Zoho People Employee records via the Convert to Employee integration. If Zoho People is not in scope, we add a custom field hired__c with the employment start date on the Candidate record in Zoho Recruit.

Resume files and attachments on Personio applications export as binary files. We map each attachment to the corresponding Zoho Recruit Candidate record via the candidate email key. Zoho Recruit supports attaching documents to candidates via the attachment API, with file versioning available on Professional and Enterprise tiers. CV files from Personio map to the Resume field on the Candidate record in Zoho Recruit for parsing by Zoho's resume extractor.

Personio absence records are an HRMS feature with no equivalent in Zoho Recruit's ATS data model. Interview scheduling conflicts arising from candidate absences are better managed in Zoho Recruit's interview scheduler. We do not migrate absence records to Zoho Recruit. If the customer requires absence tracking post-migration, we recommend Zoho People as the complementary absence management tool and map Personio absence categories to Zoho People absence types during a separate engagement.

Personio performance review cycles, ratings, and form question text are not migratable to Zoho Recruit because Zoho Recruit is an ATS without a performance management module. We do not migrate performance reviews. We deliver a written inventory of active review cycles, form questions, and rating distributions so the customer's HR admin can plan rebuild in Zoho People, a dedicated performance tool, or a spreadsheet.

Personio payroll records — salary, bonus, compensation effective-dated entries — are HRMS data with no schema in Zoho Recruit. We do not migrate payroll records. If the customer uses Zoho Payroll or Zoho People for payroll, compensation history migrates separately in a payroll-focused engagement. We flag this boundary clearly during scoping.

Personio goal hierarchies (company-level to individual employee objectives), progress percentages, and goal alignments do not map to Zoho Recruit's ATS data model. We do not migrate goals. We deliver a written inventory of active goals, OKR frameworks, and linkage hierarchies for the customer's HR admin to evaluate Zoho People Goals or a dedicated OKR tool.

Personio approval chains for absence, onboarding, and document signing are not exposed via the API in a migration-ready format. Candidate-stage automation (moving a candidate from screening to interview based on a score threshold) defined in Personio Recruiting similarly does not export. We document every active Personio recruiting workflow with its trigger, conditions, and actions and provide a recommended Blueprint or Workflow Rule equivalent in Zoho Recruit. The customer's admin rebuilds these post-migration.

Personio supports custom attributes on Recruiting Positions such as employment type, remote policy, or department-specific fields. These export via the Personio API schema introspection. We create matching custom fields in Zoho Recruit Job Openings (up to 50 on Standard, 300 on Professional/Enterprise) and map values by position ID during migration. Positions with custom attributes that exceed the destination tier's custom field limit require field consolidation during scoping.

Personio employee self-service portal data — personal information updates, manager requests, time-off requests in flight — is transient session data that does not constitute a permanent record. We do not migrate self-service data. We flag any absence requests pending approval at cutover time for the customer's HR admin to handle manually in Zoho Recruit or Zoho People.

Personio effective-dated compensation entries per employee — salary changes, bonus awards, stock vesting records — are HRMS payroll data with no schema in Zoho Recruit's ATS model. We do not migrate compensation history. If the customer requires compensation tracking post-migration, Zoho People with the compensation module is the recommended destination, and compensation history migrates in a separate engagement scoped to payroll data.