Migrate from Manitou ATS to Bullhorn ATS & CRM

Manitou Candidate records (the applicant bank) map to Bullhorn Candidate. We deduplicate by email and phone before writing to Bullhorn, presenting a deduplication report to the customer for any records that match on both fields. Candidate contact info, skills (as text tags), application history, and custom fields migrate. We flag any structured competency taxonomies in Manitou that require normalization against Bullhorn's flat tag model. Note that Manitou's person-type taxonomy (e.g., Keyholder default on contact records) may create Candidate records that should be ClientContact in Bullhorn; we resolve the entity split during scoping using Manitou's person-type flag.

Manitou Job Requisitions map to Bullhorn JobOrder. We preserve job title, description, status (active, on-hold, filled, archived), department, and any custom fields. Internal hiring manager assignments from Manitou map to Bullhorn JobOrder's hiringOwner or a custom user reference field. Status values require mapping during scoping: Manitou's internal status labels must be mapped to Bullhorn's JobOrder status codes (Open, Interview, Offer, etc.) and any custom status values created in Bullhorn before import.

The Manitou join table between Candidate and Job Requisition maps to Bullhorn JobSubmission, which links the Candidate record to the JobOrder. We preserve application status, the Manitou pipeline stage the candidate occupied at time of migration, and the timestamp of stage entry. If the candidate was moved through multiple stages, we preserve the most recent stage name and date as a custom field on JobSubmission since Bullhorn's standard JobSubmission does not expose full stage history in the same way.

Manitou CRM Company records map to Bullhorn ClientCorporation. We preserve company name, address, industry, and any custom CRM fields. Associated contacts from Manitou's CRM link to the ClientCorporation via ClientContact records. If Manitou stores multiple address types (billing, shipping, office) on a single company, we map the primary address to ClientCorporation address fields and store additional addresses in custom fields or notes for Bullhorn admin to resolve post-migration.

Manitou individual Contact records map to Bullhorn ClientContact when they represent client-side contacts (hiring managers, client stakeholders). We preserve name, email, phone, and custom properties. ClientContact records are linked to a ClientCorporation via the corporationID field. We resolve this linkage during migration by matching Manitou's company-to-contact relationship to the ClientCorporation records migrated in the previous phase.

Manitou internal user accounts (recruiters, hiring managers, administrators) map to Bullhorn User records. We resolve ownership on migrated Candidates, JobOrders, JobSubmissions, ClientCorporations, and ClientContacts by matching Manitou user email addresses to Bullhorn User email addresses. Any Manitou user without a matching Bullhorn User goes to a reconciliation queue; the customer's Bullhorn admin provisions missing users before record import resumes. Role and permission data from Manitou maps to a Bullhorn custom field for the admin to configure role parity post-migration.

Manitou's configurable hiring stages (Screening, Interview, Offer, Hired, etc.) do not export as structured data. We extract stage names from individual job records where available and document the existing stage taxonomy in the scoping report. Bullhorn's candidate pipeline stages are configurable per job order type. We deliver a written stage configuration guide that maps each Manitou stage name to a Bullhorn CandidatePipeline or JobOrder custom status value, enabling the Bullhorn admin to implement parity before go-live.

Manitou skill tags and competency tags attached to candidates and jobs migrate as text tags to Bullhorn Candidate.skillList. We flag any structured skill taxonomies in Manitou that use hierarchical or categorized skill groupings; these require normalization to a flat tag list for Bullhorn import. The customer chooses whether to use Bullhorn's standard skillList field or a custom multi-select picklist during scoping.

Manitou recruiter notes and structured evaluations attached to applications or candidates migrate as Bullhorn Note records linked to the Candidate or JobSubmission. Evaluation scores and structured fields from Manitou map to custom fields on the Note record or to a custom Candidate-level field depending on the evaluation's intended use in Bullhorn. We preserve the author (linked to the migrated User), timestamp, and full note body.

Resume files, cover letters, portfolio documents, and other attachments linked to Manitou candidates or jobs are extracted and re-attached to Bullhorn Candidate or JobOrder records. Bullhorn stores candidate attachments as CandidateAttachment records linked to the Candidate entity. We extract binary files from the Manitou export, map file type (resume, cover letter, portfolio), and upload to Bullhorn via the REST API with the attachment linked to the corresponding Candidate record.

Manitou's Time & Expenses module stores timesheet and expense data tied to placements or internal projects. Bullhorn does not have a native Time & Expenses module in the standard ATS & CRM product; Bullhorn Time & Expense is a separate product (formerly myPeopleNet). We document time-and-expense record counts and field schemas in the scoping report and flag that placement-linked expense records may need to map to a custom Bullhorn object or remain in a separate billing system post-migration. This is a migration boundary decision the customer makes during scoping.

Manitou's Invoicing and Accounting modules store client billing records tied to placements. Bullhorn's billing context lives in the Placement entity with billing rate, pay rate, and invoice status fields, but not full accounting ledger functionality. We migrate Placement records with their associated billing fields from Manitou's invoicing module, but we flag that accounting ledger details (GL codes, accounts payable/receivable, invoice PDFs) may exceed Bullhorn ATS & CRM scope and recommend a separate accounting system migration if those records are needed in the new stack.