Migrate from PageUp to Recruit CRM & ATS

PageUp Candidate records (applicant data, evaluations, hiring process status, resume files) map directly to Recruit CRM Candidate. The Exports API provides structured candidate exports with configurable field selections. We preserve resume files as document attachments. Custom fields on the PageUp candidate record map to Recruit CRM custom fields on the Candidate object. PageUp's candidate status pipeline stages map to Recruit CRM's stage configuration on the Job Order.

PageUp Position records (job postings, sourcing channels, candidate metrics, pipeline analytics) map to Recruit CRM Job Order. We export active and historical positions, preserving job board associations and posting metadata. Recruit CRM's Job Order carries the position title, description, assigned recruiter, client association, and current pipeline count. The position status (active, on hold, filled, cancelled) migrates as the Job Order status field.

PageUp Employee Records (employment history, organisational structure, effective-dated employment changes) map to Candidate records in Recruit CRM when the use case covers internal mobility or re-hire tracking. We extract the current employment state and flag any historical employment records for explicit customer consent before migration, as individual-level employment history may require GDPR consideration depending on the datacentre region.

PageUp recruiting workflows define approval chains, stage progressions, and automation triggers as tenant-specific configurations. These are configuration data, not record data, and do not export from the PageUp Exports API. We document every active workflow, map each stage to an equivalent Recruit CRM stage or pipeline, and provide a workflow recreation guide. The customer's PageUp administrator reviews and reconfigures stages in Recruit CRM's pipeline builder post-migration.

Recruit CRM has no native performance review module. PageUp performance review cycles, ratings, goals, and feedback notes map to a combination of Candidate custom fields (for recent ratings and scores) and Note attachments (for narrative feedback and historical review text). We extract review template structures and apply the most recent review data as structured fields; full review history is preserved as a dated note attachment per employee record.

Recruit CRM does not include a learning management system. PageUp courses, training records, and learning paths (completion status, scores, enrollment history) cannot map to native objects in Recruit CRM. We extract these records and create a Learning History section on the Candidate record using custom fields for completion dates and course names, with the full training record as an attached summary document.

PageUp electronic forms handle new hire onboarding, compliance acknowledgements, and HR transactions. Form templates and submitted responses export from PageUp but require field-level mapping to Recruit CRM custom fields on the Candidate or Job Order. We document the form structure, identify each form field's data type, and map it to the nearest Recruit CRM field type. Custom form logic and conditional routing do not migrate.

Background check status and summary fields export cleanly from PageUp via the Exports API and map to Recruit CRM candidate custom fields (check status, check type, completion date, result summary). The actual PDF or image files (background check reports, criminal record checks, verification documents) are stored as attachments requiring a separate file-level extraction pass via PageUp's document endpoints. We package these alongside the candidate record export and attach them to the corresponding Recruit CRM candidate record.

PageUp onboarding tasks, checklist progress, and new hire document completions track per employee. We export onboarding status and completed task records. Recruit CRM's Job Order checklist and Task objects serve as the destination for onboarding task records. Step sequencing and automated task triggers are tenant-specific configurations that we document as a separate onboarding workflow guide for the customer's administrator to rebuild in Recruit CRM.

Recruit CRM has no native succession planning module. PageUp succession planning records (role mappings, identified successors, readiness ratings) export from the Employee Record and Position objects. We map these to Candidate custom fields (succession role, readiness score, development target) and preserve the full succession plan as a note attachment on the relevant Position record. The destination succession module concept is replaced with structured custom fields in Recruit CRM.

PageUp survey results, participation rates, and trend data export by cycle. We export aggregate and anonymised results where applicable, flagging individual-level response data for explicit customer consent before migration. Survey aggregate scores migrate to Position or Job Order custom fields; cycle-level trend data migrates as a report note attachment. Recruit CRM has no native survey module.

PageUp stores employee documents including contracts, signed forms, and performance records. We extract document metadata and binary files via PageUp's document endpoints. Recruit CRM stores documents as attachments linked to Candidate or Job Order records via its document management tool. We preserve the original document naming convention and folder hierarchy as metadata fields in Recruit CRM, and attach the binary files directly to the relevant record.