Migrate from Workday HCM to BambooHR

Workday Workers (employees, contractors, contingent workers) map to BambooHR Employees. The Workday Worker record contains personal data, employment terms, supervisory organization, job profile, and compensation all in one object; we split these into BambooHR's Employee profile fields (personal info), Job Info tab (title, department, manager, hire date), and Compensation block (pay rate, frequency). The Workday hire_date becomes BambooHR's hire date. Terminated workers map with their termination_date preserved.

Workday Positions represent organizational staffing slots that may be filled, vacant, or held by multiple workers over time. BambooHR has no Position object; job title, department, and manager attach directly to the Employee record. We handle the split by mapping the primary incumbent's Position title and supervisory organization to the Employee's Job Info block. For positions held by multiple workers (same job, same org), we create one BambooHR Employee record per incumbent. Vacant positions do not have a migration equivalent in BambooHR and are flagged as excluded from scope.

Workday Supervisory Organizations define the manager-to-worker reporting chain and can nest multiple levels deep. BambooHR represents hierarchy through the manager field on each Employee record. We extract the full supervisory org tree from Workday via the Organizations WQL query, map each manager's Worker ID to the corresponding BambooHR Employee manager_id lookup, and set the top-level manager's manager_id to null. Matrix reporting relationships (dotted-line) are noted as unsupported in BambooHR and excluded from scope.

Workday Organizations form a hierarchical graph (cost centers, business units, regions) that maps to BambooHR's flat department list. We extract the full org hierarchy and flatten it into BambooHR departments, preserving department names and, where supported, the top-level parent organization. Sub-department nesting beyond two levels is collapsed into the closest BambooHR-supported hierarchy. The customer selects a naming convention during scoping.

Workday compensation entries (pay changes, bonuses, stock grants) carry effective dates and are effective-dated compensation entries tied to a Worker. BambooHR stores only the current pay rate in the Compensation block. We export each compensation event with its effective date, type (base salary, bonus, equity), amount, currency, and change reason, then map these to a structured Employee File attachment named 'Compensation History.pdf' or a custom field set if the customer prefers tabular data. We sequence compensation events chronologically during export so retroactive adjustments land in the correct order.

Workday benefit elections (health, dental, vision, life, 401k) store plan names, coverage tiers, and dependent relationships with enrollment dates. BambooHR's Benefits module supports health, dental, vision, life, and supplemental plans with coverage levels (employee, employee+spouse, family). We map Workday benefit plan types to BambooHR plan categories, and Workday coverage levels to BambooHR coverage options. Where BambooHR does not support a specific benefit type (e.g., FSA, HSA, commuter benefits), we document the gap and recommend a manual enrollment review post-migration.

Workday leave accruals, balances, and pending requests are tied to Worker and Plan combinations with accrual rates, carryover rules, and pending approvals. BambooHR Time Off supports accrual-based and unlimited plans with configurable policies. We export current accrual balances per Worker per Plan and import them as BambooHR time-off balances. Pending requests are recreated as BambooHR pending requests with the original request dates and hours. BambooHR's plan types (Annual, Accrual, etc.) are mapped from Workday plan configurations during scoping.

Workday Job Profiles define qualifications, skills, and competencies associated with a Position. BambooHR's Jobs module holds job title, department, employment status, and an optional job description. We extract Workday profile attributes (required skills, education, experience) and append them as structured text to the BambooHR job description field. Competency ratings and skills taxonomies that cannot fit in the job description are noted as unsupported and documented for manual follow-up.

Workday Custom Objects extend the delivered schema and are tied to business objects like Worker or Position. BambooHR supports custom fields on Employee and a limited set of other objects. We discover every Workday Custom Object via WQL schema queries before migration, then create equivalent BambooHR custom fields (text, number, date, dropdown, checkbox) during the destination schema build. Any Custom Object field that cannot map to a supported BambooHR field type is flagged with the customer for a manual alternative (Employee File attachment or external record).

Workday Worker documents (offers, contracts, performance reviews, I-9s) are stored as binary attachments with document category metadata. BambooHR Employee Files support file uploads per employee with category tagging. We export each document as a binary blob, map the Workday document category to a BambooHR file category (Offer Letter, Employment Contract, Performance Review, Onboarding), and upload to the corresponding BambooHR Employee Files section. Large document stores require storage estimation before migration to confirm the destination tenant has adequate capacity.

Workday payroll registers (gross pay, deductions, taxes, net pay, direct deposit) are gated by the Payroll system role and exported via payroll-specific APIs. BambooHR does not include native payroll at its Core tier and uses integrations with ADP, Gusto, or Paychex for payroll processing. We scope payroll summary export as a structured record block only if the customer has payroll-reader API access and a destination payroll integration already configured. Otherwise, payroll data is excluded from migration scope and flagged as a pre-requisite for post-migration setup.