Migrate from mploy to Bullhorn ATS & CRM

mploy Candidates map directly to Bullhorn Candidate records via the Bullhorn REST API. Standard fields (name, email, phone, address) migrate as typed fields. The absence of a published mploy schema means we enumerate all standard fields by requesting a sample CSV export during discovery and mapping field names by header inspection. Custom fields on Candidate require explicit enumeration by the customer's mploy admin before mapping can begin.

mploy Job records map to Bullhorn JobOrder. Fields including title, department, location, description, status (open/closed), and created date migrate to Bullhorn's corresponding JobOrder fields. We preserve open/closed status and reactivate archived jobs in Bullhorn as needed. JobOrder owner (recruiter assignment) resolves via email lookup against Bullhorn User records after User provisioning.

mploy Application records (the join between Candidate and Job) map to Bullhorn Submission. We preserve submission date, current pipeline stage, source attribution, and status. Pipeline stage names in mploy are customer-configured and must be mapped to Bullhorn Submission status values during discovery. Source attribution (job board, referral, direct) migrates to the Submission's source field.

mploy hiring pipeline stages map to Bullhorn Submission status values. We design a Bullhorn Submission Record Type per mploy pipeline configuration and whitelist the relevant status values per Record Type. Stage ordering is preserved as the ordered SubmissionStatus sequence. This mapping requires a screenshot or export of the mploy pipeline stage configuration during discovery.

mploy User accounts (admin, recruiter, hiring manager roles) map to Bullhorn User records. We resolve by email match. Any mploy user without a matching Bullhorn User goes to a reconciliation queue for the customer's Bullhorn admin to provision. Role mapping (admin, recruiter, standard) translates to Bullhorn department and user-type entitlements.

mploy custom fields on Candidates are undocumented and must be enumerated manually during discovery. We request a screenshot or live walkthrough of the Candidate record's field configuration. Each enumerated custom field maps to a Bullhorn custom field created via Admin > Field Mappings before migration. Field data type (text, number, date, picklist) is inferred from sample values in the export CSV.

Same enumeration requirement applies to custom fields on mploy Job records. We create equivalent Bullhorn JobOrder custom fields before migration and map values during the CSV-to-API ingestion phase. Custom fields that exceed Bullhorn's standard field character limits are flagged for split or truncation during scoping.

mploy Offer records (compensation details, start date, acceptance status) map to Bullhorn Placement records or custom fields on Submission depending on the customer's configuration. We clarify the target object during discovery because Placement creation in Bullhorn requires an existing Submission and JobOrder in scope. If mploy stores offers separately from Applications, we merge them during transformation before Bullhorn ingestion.

Resume files and uploaded attachments stored in mploy require a separate export from field data because binary assets are typically not included in CSV field exports. We request the attachment archive as a separate download (or confirm it is included in the bulk export). Bullhorn stores resumes as ContentDocument records linked to the Candidate via ContentDocumentLink. Resume parsing is re-triggered by Bullhorn on ingestion if the customer enables Bullhorn's built-in resume parsing.

Closed and archived mploy Job records migrate to Bullhorn JobOrder with status set to Closed to preserve historical requisition data. Archived jobs do not appear in active job lists but are accessible in Bullhorn's reporting and search. We recommend preserving at minimum the last 24 months of closed job history for compliance and reporting continuity.

If mploy records stage-transition timestamps or candidate activity history as log entries, these migrate as Bullhorn Note records or Task records linked to the Candidate. The format depends on what the mploy CSV export contains under history or activity columns. We inspect the sample export during discovery to determine whether this data is present and how to structure it in Bullhorn.

mploy does not confirm Interview as a separately exportable object. Interview data, where present, may be stored in Notes or calendar fields. We flag interview records as candidate notes during discovery and migrate them as Note records in Bullhorn rather than as standalone Event records. The customer's Bullhorn admin should configure Bullhorn's calendar integration or Bullhorn Automation for ongoing interview scheduling post-migration.