Migrate from PageUp to Crelate

PageUp Candidate records map to Crelate Contact. We extract applicant core data, contact information, source channel, pipeline stage status, and evaluation scores via the PageUp Exports API. Crelate's field mapping feature (Settings | Custom Forms) lets us map candidate custom fields to Contact columns at the form level. We preserve the original PageUp candidate ID in a custom Crelate field for audit traceability and to support referential integrity if any historical cross-references exist.

PageUp Position records map to Crelate Opportunity. We export job posting data including title, department, location, employment type, salary range, sourcing channels, candidate metrics, and posting metadata. Crelate Opportunity captures the position as a recruiting placement or requisition, with job board associations and pipeline metrics preserved as custom fields. Active and historical positions migrate; closed positions migrate with a status flag so they can be excluded from active views.

PageUp recruiting workflows define approval chains, stage progressions, and automation triggers as tenant-specific configuration. These do not export as record data. We document every active workflow: trigger conditions, stage definitions, approver assignments, and automation actions. We map each to Crelate's workflow builder equivalent on Business Plus or Enterprise. The customer's PageUp administrator reviews the workflow inventory document and rebuilds in Crelate, which we support through the documentation handoff.

Background check status and summary fields from PageUp migrate as structured data mapped to a Crelate custom Contact field or Activity record. The PDF/image files attached to background check records require separate file-level extraction via PageUp's document endpoints. We package these alongside the candidate record export as a separate document bundle. Customers must verify that background check vendor agreements permit data transfer before migration; we flag any records flagged as vendor-restricted in the migration scope.

PageUp Employee records spanning employment history, compensation changes, and organisational structure migrate as historical Contact records in Crelate. PageUp stores effective-dated employment changes; we extract the current state and flag historical employment records in a custom field to preserve audit context. Note that Crelate is an ATS/CRM, not an HRIS; employees without an active recruiting record may be archived rather than carried as active contacts.

Performance review cycles, ratings, goals, and feedback notes are stored per employee in PageUp. Crelate has no native performance review module. We export review templates and historical review data as structured records, then map them to Crelate Activity Notes with a custom review type flag, or to a Crelate custom object if the customer's Business Plus/Enterprise plan supports one. Custom review criteria and competency frameworks require manual mapping to whatever structure the customer defines post-migration.

PageUp E-Forms handle new hire onboarding, compliance acknowledgements, and HR transactions. Form templates and submitted responses are structured data, but form logic and custom field behaviour are tenant-specific configuration. We export submitted form response data as structured records mapped to the corresponding Crelate Contact or Activity. We document form structure and field types for the admin to rebuild using Crelate's custom form builder and field mapping feature.

PageUp Learning modules store courses, training records, and learning paths. Crelate has no native learning management system. We export learning completion status, scores, and enrollment history as structured data for the customer's HR team to store externally or import into a dedicated LMS. We provide a written inventory of active courses, learning paths, and completion records. This data does not map into Crelate's schema without a custom object implementation.

PageUp succession planning records map roles to identified successors with readiness ratings. Crelate has no native succession planning module. We export plan definitions and incumbency data as structured records and deliver them as a written inventory for the customer's HR team to manage in a dedicated succession tool or a Crelate custom object built post-migration. Readiness rating scales may differ between platforms and require normalisation if a custom object is created.

PageUp onboarding tasks, checklist progress, and new hire document completions migrate as Crelate Activity records with a custom onboarding type flag attached to the Contact. Step sequencing and automated task triggers are tenant-specific configuration that do not export. We document active onboarding sequences and map completed tasks to Activity records; the customer's admin rebuilds automated onboarding task triggers using Crelate Workflow on Business Plus or Enterprise.

Employee documents including contracts, signed forms, and performance records stored within PageUp are extracted as binary files via the document endpoints. We migrate document metadata (type, date, related record) alongside the binary files and attach them to the corresponding Crelate Contact record. Document naming conventions and storage hierarchy may differ; we standardise file names during extraction using a consistent naming pattern (CandidateID_DocType_Date).

PageUp engagement records (call dispositions, email content, meeting attendees, interview notes) export via the standard API where available. We map these to Crelate Activity records with the appropriate type: Call, Email, Meeting, or Note. Activity timestamps and disposition data transfer as custom fields on the Activity record. Note that Crelate's engagement tracking is scoped to recruiting activity; broad talent management interactions from PageUp's performance or learning modules may not have a direct Crelate equivalent and are flagged during scoping.