Migrate from EMP Trust HR to BambooHR

EMP Trust HR Employee records map directly to BambooHR employee profiles. Standard fields (name, date of birth, hire date, employment status, department, location) migrate as typed fields. Custom employee properties migrate as BambooHR custom fields. BambooHR custom fields do not sync with integrations per their documentation, so any custom fields that represent integration-derived data must be reconciled separately after migration.

I-9 Section 1 (employee completion) and Section 2 (employer/agent verification) records are split across two migration targets. E-Verify case number, verification date, and case status code (Verified, Tentative Nonconfirmation, DHS/DOJ Query) migrate as read-only custom fields on the BambooHR employee record for compliance visibility. The completed I-9 PDF and supporting document images migrate as BambooHR document records tagged with the document type (I-9 Section 1, I-9 Section 2, supporting identification). BambooHR does not have native E-Verify integration; the case status is maintained as a custom field, not a live status, so the customer's compliance team must monitor E-Verify directly for any in-progress Tentative Nonconfirmation resolutions.

E-Verify case status codes migrate as a custom picklist field ev_case_status__c on the BambooHR employee record with values matching the DHS E-Verify codes. The E-Verify case number migrates as a text field ev_case_number__c. Any Tentative Nonconfirmation (TNC) record is flagged in a migration summary document so the customer's compliance team can document the resolution date in BambooHR's custom field after migration.

EMP Trust HR New Hire Portal instances map to BambooHR's onboarding workflow. Portal state (started, in-progress, completed) maps to BambooHR's onboarding status tracking. Task sets within the onboarding package map to BambooHR onboarding tasks assigned to the new hire, manager, and HR admin. We preserve the portal completion timestamp and map any custom task due dates to BambooHR task due date fields. Portal branding assets (logo, color scheme) do not migrate; BambooHR uses its own onboarding branding settings.

EMP Trust HR forms (offer letters, NDAs, non-competes, policy acknowledgements, W-4, direct deposit, beneficiary forms) migrate as BambooHR document records tagged by form type. Each document record is linked to the corresponding employee. The e-signature metadata (signer ID, timestamp, IP address, certificate hash) is extracted from EMP Trust HR's proprietary storage and written into a structured envelope schema as a JSON attachment to the document record, flagging any forms where the certificate chain cannot be fully reconstructed. BambooHR does not support native e-signature audit trail reconstruction; the customer should review any flagged forms with their legal or compliance team to determine whether re-signing is required.

EMP Trust HR custom form definitions do not have a direct BambooHR equivalent. BambooHR uses a combination of onboarding tasks (for information-gathering steps) and document templates (for repeatable forms) for this purpose. We deliver a written inventory of every EMP Trust HR form definition with its field list, conditional logic, and e-signature requirement so the customer's BambooHR admin can rebuild the forms in BambooHR's onboarding builder. Conditional branching is not preserved in the migration; it is documented for manual rebuild.

Onboarding tasks assigned to new hires, managers, HR staff, and IT migrate as BambooHR onboarding tasks. Task status (pending, in-progress, completed), due dates, and assignees map directly. Task hierarchy within EMP Trust HR onboarding packages flattens into a sequential task list in BambooHR. We preserve completion timestamps. Task assignment rules (auto-assign by department, location, or job title) do not migrate; they are documented for the admin to rebuild in BambooHR's onboarding workflow configuration.

Courses assigned via the EMP Trust HR new hire learning portal with completion flags, scores, and assignment timestamps migrate as custom fields on the BambooHR employee record (e.g., training_completion_course_name__c as a checkbox or date field) or as tagged document records with completion metadata. BambooHR does not have a native learning management system; for organizations with extensive training histories, we recommend migrating course completion records as structured documents or as custom table data, with the LMS functionality handled by a separate platform.

Background check results sourced through EMP Trust HR's pre-built integrations (CastleBranch, AccurateBackground, BirdDogHR) migrate as summary records. We map the result status (Clear, Pending, Adverse Action) and order date as custom fields on the employee record. Raw vendor report PDFs migrate as document records. The background check integration itself does not migrate; the customer must establish a new integration with their chosen background check provider in BambooHR or continue using the vendor directly.

Benefits selections captured during onboarding (plan choices, dependent information, beneficiary designations) migrate as historical records attached to the employee profile. We map plan names and coverage tiers as custom fields or structured table data in BambooHR. BambooHR's native benefits administration module can be configured for ongoing enrollment management, but active ongoing changes in EMP Trust HR (life events, mid-year elections) must be captured as a separate data pull before migration and manually reconciled. BambooHR does not maintain a live feed to benefits carriers without a third-party integration (e.g., via their benefits partner network).

Candidate fields pushed from Greenhouse or Lever through the EMP Trust HR integration are limited to the fields configured in the integration mapping. Any source ATS fields not included in the EMP Trust HR integration configuration are not available in the source export. We document the integration field map during scoping, flag any candidate source fields that were not mapped, and recommend that the customer pull a full candidate export from the original ATS before migration to preserve any fields that should follow the employee into BambooHR. BambooHR's native Greenhouse and Lever integrations are configured fresh post-migration with the customer's chosen field mapping.