Migrate from Webrecruit to BambooHR

Webrecruit Candidates map to BambooHR Employees in the HRIS core with application records tracked separately in BambooHR Hiring. The candidate's name, email, phone, address, and work history migrate to the BambooHR Employee profile. GDPR consent timestamp and withdrawal flag migrate to the BambooHR opt-out field and a custom field capturing the original Webrecruit consent date. Candidates with withdrawn or expired consent are flagged but not migrated unless the customer explicitly requests otherwise. CVs and cover letters attach as files to the employee record.

Webrecruit Job records (title, description, department, location, status, posting dates) map to BambooHR Job Openings. The job status (active, paused, closed) migrates directly. Department and location map to BambooHR's Department and Location fields. Inactive or archived jobs are migrated as closed Job Openings with a flag for the customer's admin to review relevance before reposting.

Each Webrecruit Application links a Candidate to a Job with a timestamp and current stage. This maps to a BambooHR Applicant record attached to the corresponding Job Opening. The full application timeline including submission date, rejection dates, and withdrawal status migrates. Stage progression history is preserved as a custom multi-line text field or as note attachments since BambooHR Hiring's native stage timeline is a simplified pipeline view rather than a full audit trail.

Webrecruit's fixed pipeline stages map to BambooHR Hiring pipeline stages. Where Webrecruit has bespoke stage types such as aptitude or competency tests, we map them to the closest BambooHR stage (e.g., Assessment or Interview) and flag them for the customer's review. BambooHR Hiring does not support arbitrary custom stage types; any Webrecruit stages that have no equivalent must be tracked as notes or attachments on the Applicant record. We document the complete stage mapping during scoping.

Webrecruit Hiring Managers are assigned to jobs and leave feedback. We map these to BambooHR Employee records flagged with a reviewer role. If the hiring manager email matches an existing BambooHR User, we link directly. If no match exists, we create a reviewer entry and flag it for the customer's admin to provision access and permissions in BambooHR Hiring.

Webrecruit approval workflows define how a job requisition moves from creation to posting. These configurations do not migrate as code. We export workflow step definitions and document them in a written handoff for the customer's admin to recreate in BambooHR's approval workflow builder or BambooHR Hiring's job approval settings. Any job-category-specific workflow variations are captured separately during scoping.

CVs, cover letters, and attachments stored per Webrecruit application migrate as file attachments to the corresponding BambooHR Employee or Applicant record. We export document blobs and re-attach them with the original filename preserved. Large documents exceeding BambooHR's attachment limits are flagged for the customer's admin to store externally with a link recorded in BambooHR.

Webrecruit custom fields vary by account. We export field definitions and values, then attempt to map them to equivalent custom fields in BambooHR (which supports custom employee fields in HRIS and custom applicant fields in Hiring). Fields with no matching type (e.g., multi-select dropdowns that BambooHR does not support) are flagged for the customer's admin to either re-create manually or decide on an alternative representation as text fields or attached notes.

Webrecruit user accounts (name, email, role, permissions) map to BambooHR User records. We extract all distinct user emails and match them against the destination BambooHR account. If BambooHR accounts are not yet provisioned, we export a user list with roles and permissions for the customer's admin to set up before the candidate and job data migration begins.

Webrecruit integrations with BreatheHR and CIPHR are connection-level configurations that do not carry over to BambooHR. We document which integrations are active and their purpose, then include re-connection steps in the post-migration checklist. This requires the customer to re-authenticate and re-configure each integration in BambooHR using BambooHR's App Directory (150+ native integrations) or API-based connections.