Migrate from HROffice to BambooHR

HROffice Candidate records map to BambooHR Employee records. The mapping includes name fields, contact details (email, phone, address), and application status history. We use the candidate's email address as the dedupe key during import. Any candidate without a valid email address is held in a reconciliation queue for the customer's admin to resolve before the employee record is created in BambooHR.

HROffice Applications tied to a Candidate migrate as supplemental metadata on the BambooHR Employee record. The application date, status pipeline position, and recruiter notes attach as custom fields or as part of the employment history timeline. Branded career site content tied to the application does not migrate because it is tied to HROffice's CMS rather than the candidate record itself.

HROffice Job Postings carry department, location, employment type, and job description metadata. We export the posting content and structural metadata into BambooHR Job Openings. Branded career site formatting, custom career page fields, and employer branding assets tied to the posting do not migrate because they are platform-specific layout elements. The job description text and requirements migrate as the BambooHR Job Opening description.

HROffice Assignments (temporary placements, temp-to-perm arrangements, weekly timecard cycles) are the most structurally distinct object in this migration. BambooHR does not have an Assignment object. We export each Assignment as a separate supplemental record and attach it to the corresponding BambooHR Employee as a custom multi-row table or as structured custom fields (assignment_type, start_date, end_date, weekly_pay_rate, timecard_status). This preserves the staffing history without creating duplicate or conflicting employment records. The customer decides during scoping whether to display assignments as a history table or as discrete fields.

HROffice weekly timecard records (hours worked, submission date, status) migrate as a separate historical object or as part of the Assignment supplemental record. BambooHR's native time tracking module can receive hours data, but HROffice's weekly submission cadence does not map directly to BambooHR's time-off and hours tracking model. We export timecard history as structured data attached to the relevant Assignment or Employee so the customer's payroll team can use it as a reference during BambooHR payroll setup.

HROffice internal Users (recruiters, administrators) are separate from Candidates or temporary workers. User records carry role-based permissions that govern access within HROffice. We export user accounts by email match against the BambooHR User table. HROffice recruiter-level permissions and staffing workflow roles do not have direct BambooHR equivalents because BambooHR's permission model is HRIS-focused rather than ATS-staffing workflow-focused. We map HROffice admin users to BambooHR admin accounts and flag any staffing-specific role for the customer to configure post-migration.

HROffice benefit enrollment records, plan assignments, and effective dates may exist depending on the customer's module configuration. We export benefit data as supplemental employee properties in BambooHR. BambooHR's Benefits Administration module (an add-on) can receive enrollment data if the customer has it enabled; otherwise benefit records migrate as structured custom fields on the Employee record for the customer's HR team to re-enroll post-migration.

HROffice compensation records (pay type—hourly, salary—rate, and effective dates) migrate to BambooHR Employee pay-related custom fields. HROffice's weekly pay cycle for temporary placements does not map to BambooHR's standard pay frequency options, so we store the original pay rate and pay type as custom fields and flag the pay frequency discrepancy for the customer's payroll admin to configure.

HROffice's built-in referral recruitment tool generates candidate referrals tied to referring employees. Referral source data migrates to a custom Employee field (referral_source_employee) on the referred Candidate's Employee record in BambooHR. Employer-branded referral program mechanics (rewards, tracking links, referral thresholds) do not migrate because they are workflow configurations rather than candidate data.

HROffice employer profile data (company name, address, industry, size) migrates to BambooHR's company settings. This is a lightweight mapping covering the employer's organizational profile rather than individual employee records. Employer-branded content, logo assets, and CMS-specific fields do not migrate.