Migrate from PageUp to BambooHR

PageUp Candidate records contain applicant data, hiring stage status, evaluations, and resume file references. BambooHR does not have a native Candidate object in its base Core or Pro tiers—the ATS module creates a separate applicant tracking schema. We assess whether BambooHR's ATS is in scope during scoping. If ATS is licensed, candidates migrate as Applicants linked to Job Openings; if ATS is not in scope, we extract candidate contact information (name, email, phone, resume) and map it to Employee records with a source_candidate__c custom flag, and the recruiting history is documented as a manual import using BambooHR's CSV import tool. Resume file extraction requires separate file-level handling via PageUp's document endpoints.

PageUp Positions include job postings, sourcing channel metadata, candidate pipeline metrics, and posting status. If BambooHR's ATS module is in scope, Positions map to Job Openings with status, department, and location preserved. If ATS is not licensed, Positions are documented as a separate record set requiring manual entry or a CSV import post-migration. Job board association metadata from PageUp (e.g., which board a position was posted to) has no direct BambooHR equivalent and is noted as a gap requiring manual documentation.

PageUp Employee records include personal data, employment history, organisational structure, compensation effective dates, and custom fields. We map standard fields (first name, last name, work email, hire date, termination date, job title, department, location) to BambooHR's employee fields. Custom fields on PageUp are fetched by dynamic field ID during export and must be mapped to BambooHR custom fields created via GET /v1/meta/fields before import. BambooHR does not paginate employee list responses—all employees return in a single API call, so large organisations produce substantial payloads requiring chunked processing.

PageUp Performance Review cycles, ratings, goals, competency scores, and feedback notes are stored per employee. BambooHR's Performance Management module (Pro and Elite tiers only) supports review cycles, 360-degree feedback, 1:1s, and goal tracking. We extract review templates and historical review data from PageUp. If the customer has BambooHR Performance licensed, reviews migrate as Performance Review records; if not, we map review ratings and goals to custom fields on the Employee record and document the gap in the performance module as a post-migration configuration item.

PageUp Onboarding tasks, checklist progress, and new hire document completion status migrate to BambooHR's onboarding checklist feature, which is included in Core. We extract the current onboarding task state per employee and map open tasks to BambooHR's task format. Step sequencing, automated task triggers, and new hire document e-signature flows in PageUp are tenant-specific workflow logic and do not migrate as automation; we document the original step sequence for the customer's admin to reconfigure in BambooHR.

PageUp time-off entitlements and request history migrate to BambooHR Time Off management, which is included in Core. We extract accrual balances, approved requests, and pending requests. Note that PageUp may track time off within a broader absence management module; BambooHR's Time Off uses separate Allowance and Request objects. We resolve the mapping between PageUp absence types and BambooHR policy types during scoping and apply the conversion at import time.

PageUp stores employee documents (contracts, signed forms, performance records) with binary file content and metadata. We extract document metadata and binary files via PageUp's document endpoints. BambooHR's employee file storage accepts documents attached per employee record via the Files feature. We map document type from PageUp (e.g., employment contract, compliance acknowledgement) to BambooHR file category or custom employee field. Document naming conventions and folder hierarchy in PageUp are flattened into flat file attachments per employee in BambooHR.

PageUp Background Check status and summary fields export cleanly, but PDF or image report files require separate file-level extraction via document endpoints. We extract background check status data and map it to a custom employee field (background_check_status__c) or a Note attachment in BambooHR. Customers must verify that their background check vendor agreements permit data transfer before migration, as vendor contracts often restrict movement of screening reports across systems.

PageUp custom recruiting workflows, approval chains, stage gates, and automation triggers are tenant configuration data, not record data. The Exports API extracts record-level data only. We document every active PageUp workflow with its trigger conditions, stage sequence, and action list and deliver this as a written workflow recreation guide for the customer's PageUp administrator. BambooHR does not have a workflow engine comparable to PageUp's; customers seeking automation after migration use BambooHR's workflow approvals for time-off and document signing, but custom hiring pipelines and approval chains require manual rebuild or a third-party automation layer.

PageUp courses, training records, completion status, scores, and enrollment history are stored in its LMS module. BambooHR has no native learning management capability. We extract training completion records and map them to a custom field group on the Employee record (training_completed__c, training_date__c, course_name__c) or to a custom Learning History object. The customer should evaluate a dedicated LMS (Docebo, TalentLMS, or similar) for ongoing learning management; we flag this as a parallel system decision rather than a direct migration target.

PageUp Succession Planning records map roles to identified successors with readiness ratings. BambooHR does not have a native succession planning module. We extract succession plan definitions and incumbency data as a structured export and deliver it as a CSV mapping document for the customer's HR team to maintain in a spreadsheet or evaluate BambooHR's partner ecosystem for succession-specific tools. This is a gap that requires a business-process decision rather than a data migration.