Migrate from Team Engine to BambooHR

Team Engine Jobs (title, description, location, requirements, posting status, post-date, closing date) map 1:1 to BambooHR Job. BambooHR's job posting includes fields for employment type, department, and location that we map from Team Engine's job requirements. Active versus closed status maps to BambooHR's open/closed job state. Post-date and closing date preserve as standard date fields in BambooHR's job posting date fields.

Team Engine Applicant records (name, contact info, application date, status: applied/screening/hired/rejected, source, rejection reason) map to BambooHR Candidate records in the ATS. The applicant status pipeline in Team Engine (applied, screening, hired, rejected) maps to BambooHR's candidate status values. Application source and rejection reason migrate as custom fields on the BambooHR candidate record because BambooHR's standard ATS does not expose these as native fields. We flag any applicants in hired status for direct Employee record creation in the same migration pass.

Team Engine Employee records (name, contact details, hire date, group membership) map 1:1 to BambooHR Employee records. BambooHR's employee record includes fields for job title, employment status, department, supervisor, and compensation that we populate from Team Engine where available. Hire date maps to BambooHR's hire date field. We flag any employees with missing or partial contact data for customer review before insert because BambooHR requires a valid work email for self-service activation.

Team Engine Employee Groups organize employees by role, shift, location, or trade with custom naming conventions per organization. We map these to BambooHR Departments where the naming aligns (shift-based groups may map to BambooHR location or custom fields instead). Group names that conflict with existing BambooHR Department names require customer confirmation during scoping. We flag all group memberships as separate custom fields on the Employee record to preserve the full organizational context beyond what BambooHR's single-department assignment supports.

Team Engine organizes SMS/WhatsApp conversations by contact phone number, not by the Employee object directly. We reconcile each message thread to its corresponding Team Engine Employee record by matching the contact phone number to the employee's phone number. Once matched, we create BambooHR Note records or Employee File attachments containing the thread content with timestamps. Unlinked contacts (applicants who were not hired, or crew members without a full employee record) are flagged for customer decision: create stub employee records or exclude message history from migration scope.

Team Engine Referral records track which employee referred an applicant and the referral status. BambooHR does not have a native referral object, so we migrate referral source (referring employee name or ID) and referral status as structured custom fields on the BambooHR Employee record. We also attach referral context to the hired employee's record for retention and recognition use cases. The customer defines the custom field labels during scoping.

Team Engine automated onboarding survey responses migrate as structured data. We map responses to BambooHR custom fields on the Employee record where the survey questions map to known fields (e.g., emergency contact, work authorization). For open-ended or narrative responses, we attach the response as a PDF document to the employee file. Survey questions themselves are not migratable as forms; we deliver a list of active survey questions for the customer to rebuild in BambooHR's onboarding workflow builder.

Team Engine exit survey responses migrate similarly to onboarding survey responses. We attach exit survey PDFs to the employee record for offboarding documentation. Structured exit data (departure reason, exit interview date) maps to custom fields on the inactive employee record. Exit survey question forms do not migrate as templates; we deliver a configuration inventory for rebuild in BambooHR's offboarding workflow.

For Team Engine Applicants who reached hired status, we create both a BambooHR Candidate record (for ATS audit trail) and a BambooHR Employee record in the same migration pass. The application date becomes the hire date on the employee record. The application source (referral, job board, direct) populates the referral source custom field on the employee record.

Team Engine automated triggered messages (new hire alerts, milestone reminders, survey triggers) are stored as platform configuration, not data records. There is no documented export for these automation rules. We do not migrate workflow logic to BambooHR's workflow engine because the automation models differ. We deliver a written configuration audit log listing every active trigger with its name, trigger event, conditions, and actions, so the customer's admin can rebuild them manually in BambooHR's Workflow or custom workflow builder post-migration.