Migrate from Manitou ATS to BambooHR

Manitou Candidates (stored in the central Applicant Bank) map to BambooHR Applicant records. We preserve name, email, phone, address, skills, and application history. Manitou's applicant-level custom fields map to BambooHR custom applicant fields, though any structured evaluations tied to the candidate record require field-level alignment during import. Duplicate candidates identified by email or name matching are presented to the customer for canonical-record selection before insert.

Manitou Job Requisitions map to BambooHR Jobs. We preserve job title, department, location, employment type, and job description. Manitou's job status (active, paused, archived) maps to BambooHR's job status field. Internal job IDs from Manitou are preserved in a custom field for cross-reference during reconciliation. Custom fields on Manitou jobs map to BambooHR job custom fields.

The Manitou join table between Candidates and Jobs maps to BambooHR Application records. We preserve the application date, current pipeline stage, rejection reason (if applicable), and any stage-change timestamps. Stage names from Manitou are mapped to BambooHR's stage taxonomy; if the names differ significantly, we document the mapping in the scoping report and apply it during import. BambooHR flattens applications as records attached directly to job openings rather than using a shared applicant bank.

Manitou Company records from the CRM module map to BambooHR Company records. We preserve company name, address, website, industry, and associated contact links. Manitou's custom CRM fields map to BambooHR Company custom fields. Note that BambooHR's Company object is primarily used for applicant company history (prior employment) rather than a full CRM account model; the customer should confirm whether client-facing company records from Manitou's CRM need to be stored externally or if BambooHR's employee company tracking is sufficient.

Manitou Contact records (individual people linked to Companies or standalone) map to BambooHR Employee records. Manitou person-type taxonomies (Keyholder default, candidate-type, client-type) are normalized into BambooHR's employee profile with employment status and hire date fields. Standalone candidate-type contacts from Manitou who have not been hired do not migrate to Employee; they remain as Applicants attached to jobs.

Manitou internal user accounts representing recruiters, hiring managers, and administrators map to BambooHR User accounts. We preserve user name, email, and role assignments. Owner references on Candidate, Job, and Application records are resolved by matching the Manitou user email against the BambooHR user email during migration. Any Manitou user without a matching BambooHR user is placed in a reconciliation queue for the customer's admin to provision before record import.

Manitou skill tags and competency tags attached to Candidates and Jobs migrate as text tags. We extract skill names from Manitou's structured skill taxonomy and map them to BambooHR job requirements (for requirements) and custom fields on the applicant record (for candidate skills). Any skill taxonomies requiring normalization against BambooHR's flat text-tag model are documented in the scoping report with the customer's input on preferred tag format.

Recruiter notes and structured evaluations attached to Manitou Applications or Candidates migrate to BambooHR Notes attached to the corresponding Applicant record. Structured evaluation scores migrate to custom applicant fields if BambooHR's data model supports typed fields, or as formatted note body text if not. We flag any evaluation formats that do not map cleanly to BambooHR's flat note model in the scoping report.

Resume files, cover letters, portfolio documents, and other attachments linked to Manitou Candidates or Jobs migrate as Files attached to the corresponding BambooHR Applicant or Job record. We extract documents from the Manitou export bundle (typically a ZIP folder alongside CSV data) and re-attach them during import. Document file types are preserved; file naming conventions are normalized to avoid import rejections. Document storage limits in BambooHR's plan tier are validated before migration to avoid post-import storage warnings.

Manitou pipeline stage names and ordering are configured per-job or globally and extracted from individual job records during export. We document the existing stage taxonomy (stage names, order, and probability values where available) in the scoping report. BambooHR's job stages are reconfigured by the customer's admin in the BambooHR ATS settings; we do not migrate stage configurations as code. The documentation we deliver lists each Manitou stage with its BambooHR equivalent for manual reconfiguration before go-live.