Migrate from Paradox to BambooHR

Paradox Candidates map to BambooHR Job Applicants. We extract the candidate's name, email, phone, address, work authorization, and EEOC fields from Paradox's native export and map them to the corresponding BambooHR application field. Candidates with a Paradox hired status migrate as employees in BambooHR only if the customer's BambooHR plan includes the onboarding module and the customer requests the post-hire employee record creation. GDPR-sensitive records with right-to-erasure flags are excluded from the migration set unless explicit consent documentation is provided.

Paradox Jobs (open positions with pipeline stages and hiring-team assignments) map to BambooHR Job Openings. We preserve the job title, department assignment, employment type (full-time, part-time, hourly), location, and open or closed status. BambooHR's job opening limits vary by tier (5 on Core, 25 on Pro, 50 on Elite); we verify the customer's tier accommodates the job opening count during scoping and flag any overage before migration begins.

Paradox Events (scheduled interviews, assessments, or time-bound hiring activities) map to BambooHR's interview records. We extract event type, scheduled date and time, participant assignments (interviewer names and emails), and outcome status from Paradox. Interviewer assignments resolve by email match to BambooHR Employee records. If the Paradox event has a scheduling link from Olivia, we document the link as a note for the admin to re-create in BambooHR's calendar integration.

Paradox Olivia screening Q&A logs do not map to a native BambooHR object. We export each screening response as a structured record (question text, candidate answer, timestamp, stage at which asked) and import them as BambooHR Application Notes attached to the Job Applicant. For multi-step screening with conditional branching, we flatten the answered path and note the branching decision in the Note body. Any screening logic (branch conditions, skip logic, score-weighted responses) is documented as a written configuration guide for the customer's BambooHR admin to implement using BambooHR's custom application questions.

Paradox Employee records (workers created after a successful hire in the Paradox HRIS layer) map to BambooHR Employee records. We migrate first name, last name, email, department, job title, location, employment status, and start date. Paradox's effective-date model for employment changes (promotions, title changes, status changes) is flattened to the current state at migration time; historical change logs are stored as BambooHR Employment History notes. If Paradox is the system of record for compensation data (salary, pay rate, bonus), we flag compensation as a migration add-on scope because BambooHR stores compensation in the Elite tier's Compensation Management module.

Paradox Groups (departments, locations, cost centers) map to BambooHR Departments. We preserve the group hierarchy (parent and child units) by creating a corresponding BambooHR Department with a parent-department relationship. Nested group depth beyond three levels is flattened into top-level departments with location-based subdivisions because BambooHR's department model supports two levels of nesting by default.

Paradox custom fields on Candidates are captured during pre-migration discovery and mapped to BambooHR custom application fields. Field types are converted to closest BambooHR equivalents: free-text to Text Field, multi-select to Multi-Select, date to Date, and numeric to Number. Conditional logic on Paradox custom fields (show field X only if field Y equals Z) is documented as a configuration guide for BambooHR's conditional field rules in the application builder.

Paradox custom fields on Jobs migrate to BambooHR custom fields on Job Openings. We map the field name, type, and default value. BambooHR's custom job fields are visible on the job posting and in the applicant tracking view but do not automatically surface in the employee record post-hire. Any job-field-to-employee-field propagation logic from Paradox is documented for the admin to implement in BambooHR's onboarding template.

Paradox candidate attachments (resumes, cover letters, portfolio files) are exported as binary files and re-uploaded to BambooHR as Employee Files (for post-hire records) or Application Attachments (for job applicants). File type, original filename, and upload timestamp are preserved. Any attachments stored outside Paradox's document layer (for example, in a linked S3 bucket or third-party storage referenced by Paradox) require a separate export step coordinated with the customer's IT team.

Paradox Offer records (compensation details, status, approval workflow data) map to BambooHR Job Offers in the ATS module. Compensation amount, offer status (pending, accepted, declined, withdrawn), and offer letter attachment migrate. Approval routing from Paradox (multi-step offer approvals) does not transfer as workflow configuration; we document the approval chain as a written step sequence for the customer's BambooHR admin to implement using BambooHR's approval workflow builder.

Paradox Schedule records (candidate availability windows and Olivia-scheduled calendar links) are exported as structured availability records and mapped to Interview records in BambooHR. Live calendar-linked scheduling links (Paradox's Calendar Sync feature) are documented as reconnection tasks for the customer's admin post-migration because BambooHR uses its own scheduling integration with Google Calendar and Outlook that requires re-authentication and re-configuration.