Migrate from mploy to BambooHR

mploy Candidates map to BambooHR Candidate records using BambooHR's Candidates API endpoint. Standard fields (first name, last name, email, phone, status, rating) migrate directly. Source attribution from mploy becomes the BambooHR custom question field or a standard Source picklist value. We flag any mploy Candidate record without a valid email address for manual review before import because BambooHR requires a bestEmail value for the Candidate to be fully functional.

mploy Jobs map to BambooHR Job records using BambooHR's Jobs API. Active and archived jobs migrate with their status preserved; mploy's job description field maps to BambooHR's question set or a custom text field depending on the destination field configuration. Department and location from mploy map to BambooHR's department and location picklists, which the customer configures in the BambooHR admin panel before migration.

mploy Applications (the join records linking Candidates to Jobs) map to BambooHR Candidate records with an associated Application status. The application date, submission source, and pipeline stage migrate as BambooHR custom fields or application status values. Stage transition timestamps from mploy replay as BambooHR application status history entries. If mploy stores application-stage history as a separate data export, we replay it as structured notes on the BambooHR Candidate record.

mploy pipeline stage names and sequence map to BambooHR's hiring pipeline configuration. We preserve the ordered stage sequence (e.g., Applied, Phone Screen, Interview, Offer) as BambooHR pipeline stages, with custom stage names translated to the closest BambooHR status equivalent. Stage probability rates from mploy migrate as informational notes for the customer's admin to configure in BambooHR's pipeline settings.

mploy Users who are also employees (recruiters, hiring managers with employee records) map to BambooHR Employee records via the BambooHR Employees API. Admin-role Users without a corresponding employee record migrate as BambooHR user accounts with the recruiter role assigned. Role assignments (admin, recruiter, hiring manager) from mploy map to BambooHR role permissions that the customer configures in BambooHR Access Control before user provisioning.

Custom fields on mploy Candidates require explicit enumeration during discovery because no public schema documentation exists. We extract the field names, data types, and picklist values from the customer's mploy admin panel export, then map each to a BambooHR custom Candidate field. The customer must walk us through their custom field configuration before we can produce the mapping; this enumeration step adds one to two business days to discovery. We flag any mploy multi-select or checkbox fields for translation to BambooHR's custom field picklist format.

Custom fields on mploy Job postings migrate to BambooHR custom fields on Job records using the BambooHR Jobs API customField parameter. Like Candidate custom fields, Job custom fields require manual enumeration during discovery. We document the source field name, data type, and value set, then produce a field-level mapping to BambooHR's equivalent custom field configuration.

mploy Offer records (compensation, start date, acceptance status) map to BambooHR Candidate record fields or a custom Offer object depending on the customer's BambooHR configuration. Offer details migrate as structured data on the BambooHR Candidate record with custom fields for compensation, start date, and offer status. If the customer has configured BambooHR's built-in Offer Letter feature, we map to that feature's fields instead.

Interview records are not confirmed as a separately exportable object in mploy. Where interview data exists in mploy, it is typically embedded in the Application record or stored as free-text notes. We attempt to capture interview date, interviewer, and outcome as structured notes on the corresponding BambooHR Candidate record. We flag this as a manual-reconstruction item in the migration scope and recommend the customer's admin configure BambooHR's interview scheduling and feedback tools post-migration to rebuild the interview workflow natively.

Resume files and uploaded attachments from mploy require separate export handling because they may not be included in the standard candidate CSV export. We request a separate file archive from mploy (admin-panel or vendor-facilitated) and map each file to the corresponding BambooHR Candidate record using BambooHR's file upload API. Attachment file names are matched to candidate records by email address as the dedupe key. We flag any attachment archive that is unavailable or inaccessible before migration begins as a blocking item.