Migrate from PageUp to Bullhorn ATS & CRM

PageUp Candidate records (applicant data, evaluations, hiring process status, resume files) map to Bullhorn Candidate. The Exports API provides structured candidate exports with configurable field selections. We preserve all standard candidate fields, map PageUp custom candidate fields to Bullhorn custom fields (via Admin > Field Mappings) or to Bullhorn Custom Objects if the customer's Bullhorn edition supports them and the data requires structured grouping. Resume files are extracted as binary and attached as Bullhorn ContentDocument records linked to the Candidate.

PageUp job postings and position records (sourcing channels, candidate metrics, pipeline analytics) map to Bullhorn JobOrder. Active and historical positions migrate with job board associations and posting metadata preserved as custom fields on the JobOrder. The JobOrder status field maps from PageUp position status, and published date migrates as an external reference date for reporting continuity.

PageUp custom recruiting workflows (approval chains, stage progressions, automation triggers) are tenant-specific configuration data and do not export as record data. The Exports API extracts workflow definitions for documentation purposes only. We deliver a written inventory of every active PageUp workflow with its stages, conditions, and recommended Bullhorn Field Mappings and Bullhorn Automation equivalents. The customer's Bullhorn administrator rebuilds workflows post-migration; we do not migrate workflow logic as code.

PageUp employee data (performance history, compensation, organisational structure with effective-dated changes) requires schema design for the Bullhorn destination. Active employees who are also candidates in PageUp's recruiting module map to Bullhorn Candidate records with a custom object for employment history. We extract the current employment state and flag historical records for the customer to decide retention scope. Succession plan incumbents migrate as Candidate records with a custom object tracking readiness ratings.

Performance review cycles, ratings, goals, and feedback notes stored per employee in PageUp do not have a direct Bullhorn standard object equivalent. We map these to Bullhorn Custom Objects attached to the Candidate entity if the Bullhorn edition supports Custom Objects (Front Office Growth/Enterprise: 10; Bullhorn ATS: 2; ATS Growth: none). Custom review criteria and competency frameworks are documented separately for the customer's Bullhorn administrator to configure as picklist values.

PageUp courses, training records, and learning paths (completion status, scores, enrollment history) migrate to Bullhorn Custom Objects on the Candidate record. Learning module structure maps as a custom object with fields for course name, completion date, score, and enrollment status. The customer's Bullhorn administrator configures the custom object tab visibility and department-level access per Bullhorn's custom object permissions.

PageUp electronic forms (new hire onboarding, compliance acknowledgements, HR transactions) store form templates and submitted responses. Form structure and custom fields do not migrate as functional forms in Bullhorn because Bullhorn's form model differs. We extract submitted form response data as structured records and map field values to Bullhorn custom fields or custom objects. The customer's Bullhorn administrator rebuilds active forms in Bullhorn using Bullhorn's standard field configuration.

Background check status and summary fields export via PageUp's standard API cleanly. The associated PDF or image files are stored as attachments requiring separate document retrieval. We extract files via PageUp's document endpoints and attach them as ContentDocument records to the corresponding Bullhorn Candidate. Customers must verify that background check vendor agreements permit data transfer before migration. We flag any records where vendor agreement restrictions apply and document the restriction in the migration handoff.

PageUp succession planning records (roles mapped to successors with readiness ratings) migrate to Bullhorn Custom Objects on the Candidate record. We export plan definitions and current incumbency data. The readiness rating scale may differ between PageUp and Bullhorn; we document the rating mapping in the migration spec and leave the decision to the customer's administrator during configuration.

PageUp onboarding tasks, checklist progress, and new hire document completions tracked per employee migrate to Bullhorn Custom Objects on the Candidate record. Task status and completion dates migrate as structured data. Step sequencing and automated task triggers are tenant-specific configuration that do not export; we document the onboarding workflow for the customer's Bullhorn administrator to rebuild using Bullhorn Automation if licensed.

Survey results, participation rates, and trend data stored by cycle export as structured records. We export aggregate and anonymised results where applicable and flag individual-level response data for explicit customer consent before migration. The customer's administrator decides whether engagement data migrates as a custom object on Candidate or is held for manual handoff if GDPR or regional data-privacy requirements apply.

PageUp employee documents (contracts, signed forms, performance records stored within the platform) are extracted as document metadata and binary files. We extract all documents and attach them to the corresponding Bullhorn Candidate or ClientCorporation record via ContentDocumentLink. Document naming conventions and storage hierarchy from PageUp are preserved in the file naming or metadata fields to maintain discoverability in Bullhorn.