Migrate from Workstream to BambooHR

Workstream Employees map directly to BambooHR Employee records. Standard fields (first name, last name, email, phone, hire date, job title) migrate as typed fields. Workstream lifecycle status (Active, Onboarding, Offboarded) maps to BambooHR employment status: Active and Onboarding map to Active, Offboarded maps to a terminated status with the termination date and reason carried into BambooHR's termination_date and termination_reason fields. Workstream's location assignment migrates to a custom BambooHR field (e.g., assigned_location__c) since BambooHR organizes by department rather than physical location.

Workstream Position records (job openings linked to a specific location with title, pay rate, schedule type, and job description) map to BambooHR job titles and department assignments. The position's location becomes a custom location field on the employee record rather than a native BambooHR organizational unit. We extract pay rate and schedule type from the Position record and map them to BambooHR's compensation fields and a schedule custom field respectively. Active positions with no assigned employee become job opening records in BambooHR's ATS if the add-on is active; otherwise they are documented as positions requiring job opening setup.

Workstream Applications (candidate submissions tied to a specific Position with contact info, screening answers, communication history, and pipeline status) map to BambooHR Job Opening and Applicant records. The migration requires the BambooHR ATS add-on ($99-$199/month extra). If the ATS add-on is not active at the destination, we migrate application metadata as custom fields on the originating Position record for the customer's admin to create job openings manually. Pipeline stage names and order migrate from Workstream to BambooHR job opening statuses.

Workstream Position Templates are reusable job definitions that feed multiple Position instances. We flatten Position Templates into their instantiated Position records during export, preserving the template origin as a custom field (e.g., position_template_source__c) on each position or employee record. BambooHR does not have a native template concept, so reusable job definitions are recreated as BambooHR job titles and documented in the handoff package for the customer's admin to configure as templates if needed.

Workstream custom fields (text, date, number, and dropdown formats scoped by role, location, or department) map to BambooHR custom employee fields. Because Workstream custom fields can be present on one employee record and absent on another within the same organization, we profile field-level presence during scoping and create BambooHR custom fields only for fields that exist on at least one record. Field visibility in BambooHR is set org-wide with field-level access rules applied post-migration. Dropdown fields map to BambooHR dropdown custom fields; text and date fields map to their equivalents.

Workstream Locations are the primary organizational unit with their own configuration, manager, and address. BambooHR does not have a native Locations concept. We map Workstream location names and addresses to a custom employee field (assigned_location__c) or, if the customer has a small fixed set of physical locations, we create BambooHR Departments named after each Workstream Location and assign employees accordingly. Location manager information migrates as a custom field on the location or to a manager reference field.

Workstream Role assignments scoped to locations determine pay rates and schedule authority per role-location combination. Since BambooHR ties each employee to a single job title and department, multi-role employees (common in Workstream for part-time hourly workers who cover multiple shifts or roles) are handled by creating a custom multi-select text field (e.g., roles_and_locations__c) that concatenates the role-location combinations with pay rates, preserving the compensation and scheduling context that exists separately in Workstream.

Workstream stores pay rates, pay schedules, and payroll sync status as employee properties because Workstream integrates with third-party payroll providers rather than running payroll internally. We map pay rate fields, pay frequency, and payroll sync status to BambooHR compensation custom fields. BambooHR Payroll (a separate product with its own pricing) may be the destination payroll system; if so, we coordinate pay rate mapping to BambooHR's native compensation fields. If the customer uses a third-party payroll outside of BambooHR, the pay rate fields migrate as custom fields for the customer's payroll admin to configure.

Workstream's data export separates Active, Onboarding, and Offboarded employees into distinct tabs. Offboarded records contain termination date, termination reason, and final status. We include offboarded history in the migration scope by default (unless the customer opts out) and migrate these records as BambooHR Employee records with status set to terminated, termination_date populated, and termination_reason carried into a custom field. Preserving this history is critical for compliance records and for maintaining accurate employment verification data.

Workstream's configurable hiring pipeline stages (Applied, Screening, Interview, Offer, Hired) map to BambooHR job opening statuses. We extract the full pipeline definition including stage names, order, and any conditional logic and document it in the migration handoff package. If BambooHR ATS is active, we configure the corresponding job opening statuses in BambooHR's ATS settings during the schema setup phase. Stage-level customization (e.g., stage-specific questions or automated actions in Workstream) does not migrate and is documented for admin rebuild.

Workstream stores tax forms, ID scans, and signed onboarding documents as binary attachments not accessible via the CSV export tool. We do not migrate binary document files. Employee metadata about document submission status (which forms were completed, submission dates) migrates as a field on the employee record, and we provide the customer with a document download checklist specifying all document packets to retrieve manually from Workstream before cutover. BambooHR supports file attachments on employee records via its UI and API for post-migration manual upload.