Migrate from PageUp to Zoho Recruit

PageUp Candidate records (applicant data, evaluations, hiring process status, resume files) map to Zoho Recruit Candidates module. We extract structured candidate exports via PageUp's Exports API with configurable field selections, preserving candidate IDs as a cross-reference field zoho_migration_source_id__c. Resume files are extracted separately as binary attachments and uploaded to Zoho Recruit via the Document Library API, linked to the Candidate record via ContentDocumentLink.

PageUp Position records (job postings, sourcing channels, candidate metrics, pipeline analytics) map to Zoho Recruit Job Openings. Active and historical positions migrate with job board associations preserved as source tracking fields. Posting metadata (publication date, expiry, job board identifiers) maps to Zoho Recruit's Opening_Date, Target_Date, and custom source fields.

Background check status and summary fields from PageUp migrate as custom fields on the Zoho Recruit Candidate record. The actual PDF or image files (background check reports, verification documents) require separate file-level extraction via PageUp's document endpoints. We package these as binary files alongside the candidate export and attach them to the Zoho Recruit Candidate record. Customers must verify that background check vendor agreements permit data transfer before migration.

PageUp custom recruiting workflows (approval chains, stage gates, automation triggers) are configuration data, not record data, and do not migrate as executable rules. We export workflow definitions and document each stage, trigger condition, and action as a Zoho Recruit Workflow Rule equivalent. The customer's PageUp administrator reviews and rebuilds workflows in Zoho Recruit's Workflow Rules editor (5 per module in Standard, 50 in Enterprise; Blueprint visual workflow only in Enterprise).

PageUp Employee records (current employment state, organisational structure, effective-dated changes) map to Zoho Recruit Contacts with custom fields for employment-specific data. Current employee status, job title, department, manager relationship, and hire date migrate as custom Contact fields. Historical employment changes (prior titles, department moves, compensation effective dates) are flagged during scoping; the customer chooses whether to migrate current state only or current plus most-recent historical record.

PageUp Performance Review cycles, ratings, goals, and feedback notes migrate as custom fields on Zoho Recruit Contacts for the most recent review cycle, with historical reviews preserved as linked Note records. Custom review criteria and competency frameworks require manual mapping to Zoho Recruit's custom field structure; we document the full review template and provide a field creation guide for the customer's administrator.

PageUp LMS records (courses, training records, learning paths, completion status, scores, enrollment history) migrate as custom fields on Zoho Recruit Contacts with the most recent completion data, and as Notes for historical enrollment. Zoho Recruit does not have a native LMS module; training data is stored as structured custom fields rather than as a standalone object.

PageUp E-Form templates (new hire onboarding, compliance acknowledgements, HR transactions) are configuration data that do not migrate as templates. Submitted form responses migrate as Notes linked to the relevant Contact record. We document the form structure, field list, and submission data so the customer's administrator can recreate equivalent Forms for Candidates in Zoho Recruit's form builder (1 form in Free, 5 in Standard, 10 in Professional, 20 in Enterprise).

PageUp Onboarding tasks, checklist progress, and new hire document completions migrate as Zoho Recruit Tasks linked to the Contact record, with onboarding status preserved as custom Contact fields. Task checklist items become individual Task records with Status, Priority, and due dates. Step sequencing and automated task triggers are tenant-specific configurations; we document the onboarding flow and provide a Task-creation guide for the customer's administrator to rebuild.

PageUp Succession Planning records (roles mapped to identified successors with readiness ratings) migrate as custom fields on Zoho Recruit Contacts. The successor name, readiness level, and development target date map to custom Contact fields. Zoho Recruit does not have a native succession planning module; this data requires a custom field structure that we design during schema design and deploy before migration.

PageUp Employee Engagement Survey results, participation rates, and trend data migrate as Notes attached to a parent Organisation or Department record, or as aggregate data in a custom Zoho Recruit report. Individual-level response data is flagged for explicit customer consent before migration; we do not migrate individual survey responses without documented authorisation from the customer's HR leadership.

PageUp employee documents (contracts, signed forms, performance records) migrate as files in Zoho Recruit's Document Library, linked via ContentDocumentLink to the relevant Contact record. Document metadata (file name, type, upload date, author) is preserved. We extract document binary files and metadata together, then upload via Zoho Recruit's Document Library API. Document naming conventions and storage hierarchy from PageUp may require normalisation during migration.

PageUp Owners referenced on Candidate, Position, and Employee records map to Zoho Recruit Users. We resolve by email match. Any PageUp Owner without a matching Zoho Recruit User goes to a reconciliation queue; the customer's Zoho Recruit administrator provisions missing users before record import resumes. Users must have the Field-level Access permission to receive migrated records.