Migrate from Workday Recruiting to BambooHR

Workday's Supervisory Organization hierarchy has no structural equivalent in BambooHR. BambooHR has no org tree concept; all organizational structure is implicit in the Job and Employee relationship. We flatten the Workday Supervisory Organization tree into a flat list of Jobs during migration, preserving the top-level org name as metadata on the Job record. Any supervisory chain context that must survive migration is serialized as a structured note attached to the first Job created in each org branch.

Workday Positions represent headcount slots and are a prerequisite for Job Requisitions. BambooHR Jobs are the recruiting container for a single open role. We map each Workday Position to a BambooHR Job record, using the Position's Job Profile to populate the Job title, and the Supervisory Organization to populate department and location fields in BambooHR. If a Position has a headcount greater than one, we create that many BambooHR Job records to preserve the approved headcount.

Workday Job Requisitions map directly to BambooHR Jobs. The requisition's title, department, location, employment type, and job description migrate to the BambooHR Job fields. Confidential Requisitions in Workday have no direct BambooHR equivalent; we flag them during scoping and recommend the customer either opens them post-migration or uses a restricted-access BambooHR user role to approximate confidentiality. Workday's requisition status (Draft, Open, On Hold, Cancelled, Filled) maps to BambooHR Job status.

Workday Candidates are pre-hire talent pool records separate from Workers. BambooHR Employee records serve both purposes. We map Workday Candidates to BambooHR Employee records with an Applicant status before the hire action. The Candidate's contact information, address, source, and any talent pool tags migrate directly. Note that BambooHR Employee records are shared with the HRIS module, so any post-hire HR data (compensation, time-off, performance) is a separate migration scope if the customer also moves from Workday HCM.

Workday Job Applications link Candidates to Job Requisitions and carry the scorecard, interview rating, and evaluation data. In BambooHR, Applications are a sub-record of the Job object. We map every Workday Application to a BambooHR Application linked to the corresponding Job, preserving application status (New, Screening, Phone Interview, On-site, Offer, Hired, Rejected) and the submission date.

Free-form Candidate Notes in Workday migrate to BambooHR Employee Notes. We preserve the note body, author, and original timestamp where available. Notes that reference specific Workday objects (requisition ID, application ID) are preserved as-is with the reference text intact, since BambooHR note links are not structured object references.

Workday's structured Interview Kit templates and submitted Scorecards have no equivalent in BambooHR's ATS data model. BambooHR does not support structured interview plans or typed scorecard submissions. We serialize every Interview Kit PDF and submitted Scorecard as a file attachment on the corresponding BambooHR Application or Employee record, and write the evaluator name, score, and structured feedback as a formatted Employee Note. This is the closest available representation; the customer should configure BambooHR's rating and evaluation fields during onboarding to approximate the workflow.

Workday Background Checks are typically managed via third-party integrations (HireRight, Checkr) or as attachments on the hire record and have no first-class BambooHR object equivalent. We migrate background check records as PDF file attachments on the corresponding BambooHR Employee record, preserving the check date, provider, and result status in the filename for searchability. We flag any records where the source check file URL has expired and cannot be re-downloaded.

Workday offer letters are generated via business processes tied to the Requisition and stored as records with PDF attachments. BambooHR does not have a native offer letter generation or storage business process object. We migrate offer letter PDFs as file attachments on the BambooHR Employee record, with the offer details (salary, start date, offer status) preserved in the filename and in a custom Employee Note. BambooHR's e-signature module can replace the live offer generation workflow post-migration.

Workday effective-dated Custom Objects (which track changes over time with entry and effective dates) have no equivalent in BambooHR, which supports only flat custom fields without effective-date versioning. We flag every effective-dated Workday Custom Object during scoping, preserve the current (as-of-migration-date) value as a standard BambooHR custom field, and document the full effective-dated history as a structured note or file attachment for compliance record-retention purposes. The customer decides whether to create a manual historical record process post-migration.

Workday non-effective-dated Custom Objects (simple stored values without date-based history) map to BambooHR custom fields on the corresponding Employee record. We pre-create the destination custom fields in BambooHR before migration, mapping the Workday custom object API name to a CamelCase BambooHR field name. If a Workday custom object is multi-instanced (multiple records per parent, such as vaccination records), we recommend a separate BambooHR integration or spreadsheet-based archival rather than an in-system migration, since BambooHR has no multi-instance custom object concept.