Migrate from Manitou ATS to Recruit CRM & ATS

Manitou's Applicant Bank maps to Recruit CRM's Candidate object. We preserve first name, last name, email, phone, address, skills, and application history. Custom candidate fields require field-level alignment in Recruit CRM's custom field settings before migration. Manitou's skill tags migrate as text tags; structured competency taxonomies from Manitou are normalized against Recruit CRM's tag taxonomy and documented in the scoping report for post-migration cleanup.

Manitou Job Requisitions map to Recruit CRM Job records with direct field mapping on title, description, department, status, and hiring manager. Internal pipeline configurations and stage-specific automation rules do not export as structured data from Manitou; we extract stage names per job and document them in the scoping report for manual reconfiguration in Recruit CRM's pipeline builder.

Manitou Applications (the join between Candidates and Jobs) map to Recruit CRM Applications with the candidate-to-job relationship preserved. Application status maps to Recruit CRM stage names, and timestamp history migrates as activity entries on the Application record. Stage transition timestamps transfer where the export supports them.

Manitou CRM Company records map to Recruit CRM Company. We preserve company name, address, industry, website, and associated contact links. Ownership assignments map to Recruit CRM team member records. Custom CRM fields on companies require field-level alignment during Recruit CRM configuration and are flagged in the scoping report.

Manitou Contact records map to Recruit CRM Contacts with name, email, phone, and role preserved. Linked company relationships migrate as Company lookups. Manitou's default person-type taxonomy (e.g., Keyholder) is mapped to Recruit CRM contact roles during migration. Custom contact fields are flagged for manual field-level alignment in Recruit CRM.

Manitou internal users map to Recruit CRM Team Members with role and permission set preserved. Owner references on Candidate, Job, Company, and Contact records resolve against Team Members by email match. Any Manitou user without a matching Recruit CRM Team Member is held in a reconciliation queue for the customer's admin to provision before migration resumes.

Skill tags from Manitou's candidate and job records migrate as Recruit CRM Tags. Manitou's structured competency taxonomies with hierarchy or rating levels are flattened to text tags during migration and documented in the scoping report for the customer's admin to re-establish as structured competencies in Recruit CRM if needed.

Manitou evaluations and recruiter notes attached to candidates or applications migrate as Candidate Notes in Recruit CRM. Evaluation scores and structured ratings migrate as custom fields where supported, otherwise as formatted text within the note body. We note any formatting differences that may require post-migration review.

Resume files, cover letters, portfolio documents, and other attachments linked to Manitou candidates migrate as attachments on the corresponding Recruit CRM Candidate record. We extract binary files from the export and re-attach them during the write phase. Document storage format constraints from Manitou's export are documented in the scoping report.

Manitou pipeline stage names and order are documented from per-job exports but do not migrate as structured data. We deliver a written stage inventory listing each stage name, its position in the pipeline, and any automation triggers observed, so the customer's Recruit CRM administrator can rebuild the pipeline configuration using Recruit CRM's visual pipeline builder post-migration.

Call, email, and meeting engagement records attached to Manitou candidates migrate to Recruit CRM candidate activity records where the export format supports them. Migration of engagement history is conditional on the vendor grant; if activities are absent from the export, we flag this in the scoping report and advise the customer before the production write phase begins.