Migrate from Voyse to BambooHR

Voyse employee records map directly to BambooHR Employee. The core fields (first name, last name, email, hire date, department, job title, employment status) migrate as typed BambooHR Employee fields. Any custom properties on the Voyse employee record are flagged during scoping, and undocumented field types are written to a custom field inventory for the customer's admin to decide whether each maps to a BambooHR custom field or is excluded. The BambooHR Employee API requires an active employment status to populate the employee directory correctly.

Voyse ATS candidate records map to BambooHR Applicants when the BambooHR ATS module is in scope. The Voyse candidate stage pipeline maps to BambooHR Job Application Status values. If the destination BambooHR instance does not include the ATS module, candidate records are migrated as Employee records with a custom field voyse_candidate_source__c set to TRUE and the original application date preserved. Resume files migrate as ContentDocument records attached to the Applicant.

Voyse job postings map to BambooHR Jobs. The Voyse job status (open, closed, archived, draft) maps to BambooHR Job Status. Job description, requirements, and department assignments migrate to the corresponding BambooHR Job fields. Job openings are created in BambooHR before any Applicant records are imported so that the Job lookup is satisfied at the time of Applicant insert.

Voyse department assignments on employee and job records map to BambooHR Department. Department is a lookup in BambooHR; we extract every distinct department value from Voyse during scoping, create the corresponding BambooHR Department records first, and use the resolved BambooHR Department ID as the foreign key on every Employee record. This ordering is required because BambooHR enforces referential integrity on the Department lookup.

Voyse location data (office name, city, region) maps to BambooHR Location. Location in BambooHR is a standalone object used for org chart placement and time-off scheduling context. We extract distinct location values from Voyse employee records during scoping and pre-create the corresponding Location entries before Employee import.

Voyse employment status values (active, inactive, on leave, terminated) map to BambooHR Employment Status with a direct enumeration match. Termination date and termination reason from Voyse migrate to BambooHR Termination Date and Termination Type fields. We preserve the original Voyse employment status as a custom field voyse_original_status__c for audit purposes if the enumeration values do not map cleanly.

Voyse onboarding documents (uploaded files, signed forms, stage completion timestamps) migrate as ContentDocument records attached to the corresponding BambooHR Employee via ContentDocumentLink. Document names are preserved with a voyse_onboarding_ prefix. If Voyse stores onboarding stage completion as a structured field rather than a document, we map it to a BambooHR custom field onboarding_stage__c. The BambooHR New Hire Packet template is outside migration scope and is configured by the customer's admin post-cutover.

Voyse onboarding workflows do not migrate as automation code. We deliver a written inventory of every active Voyse onboarding workflow with its trigger, stage sequence, and assigned tasks. BambooHR's Onboarding Checklist builder is the replacement tool; the customer's HR admin recreates the workflow as a checklist template in BambooHR. Stage history (completed steps and timestamps) migrates as a custom field voyse_onboarding_history__c holding a JSON log of the original stage progression.

Voyse custom properties on Employee records (beyond the standard fields) are enumerated during scoping. We create matching BambooHR custom fields on the Employee object before migration begins. Field types are mapped: Voyse text properties become BambooHR short-text or long-text fields; Voyse date properties become BambooHR date fields; Voyse numeric properties become BambooHR number fields; Voyse multi-select properties become BambooHR multiple-select fields. Custom field naming follows the voyse_ prefix convention for traceability.

Voyse custom properties on candidate records map to BambooHR Applicant custom fields when the ATS module is active. If the destination BambooHR instance does not include ATS, candidate custom properties are stored as Employee custom fields with a voyse_candidate_field__c naming prefix. We enumerate every distinct custom property during scoping and create the destination schema before any record import.

Voyse Owners (recruiters, HR admins, hiring managers) referenced on candidate and job records map to BambooHR User by email address match. We extract every distinct Voyse owner email during scoping, match against the BambooHR User table, and hold any unmapped owners in a reconciliation queue. The customer's BambooHR admin provisions missing Users before record import resumes. Active/inactive status in BambooHR is set to match the original Voyse owner status.

Voyse time-off records (PTO, sick leave, approved absences) map to BambooHR Time Off entries. The Voyse absence type maps to BambooHR Time Off Type, the start and end dates migrate directly, and the status (approved, pending, denied) maps to BambooHR status values. If Voyse stores accrual balances, we create BambooHR Time Off policies as a setup step before balance records are imported.