Migrate from Manitou ATS to Zoho Recruit

Manitou's central Applicant Bank maps directly to Zoho Recruit's Candidates module. We extract every candidate record including name, email, phone, skills, application history, and evaluation scores. Candidate deduplication runs before write using name, email, and phone matching to surface duplicate candidates for customer decision. Zoho Recruit requires Last Name as a mandatory field; candidates without a last name are written as 'not provided' in that field per Zoho's import requirements. Skills migrate as text tags and can be converted to Zoho Recruit's skills taxonomy post-migration.

Manitou job records map to Zoho Recruit Job Openings, preserving job title, description, department, status (active/closed/archived), and any custom fields. We extract stage names from individual job records during the export phase and document the complete stage taxonomy in the scoping report. Zoho Recruit enforces a specific import sequence: Job Openings import after Candidates and Contacts so that association records can link candidates to jobs correctly.

Manitou's Applications are the join table between Candidates and Jobs tracking pipeline stage progression and timestamps. These map to Zoho Recruit's association records that link Candidates to Job Openings, including application status, stage assignment, and application date. We preserve stage progression timestamps and present the stage name mapping table to the customer during scoping so Zoho pipeline stages can be configured before the association import runs.

Manitou Company records from the CRM module map to Zoho Recruit's Clients module. We preserve company name, address, industry, and associated contacts. Custom CRM fields require field-level mapping against Zoho Recruit's standard Client fields plus any custom Client fields the customer pre-creates. Client records must be imported before Contacts to satisfy the lookup dependency in Zoho's import sequence.

Manitou Contact records map to Zoho Recruit Contacts. We preserve name, email, phone, title, and custom contact properties. Manitou's default person-type taxonomy (e.g., Keyholder) is stored as a custom field in Zoho Recruit rather than a required type classification because Zoho Recruit does not enforce a person-type taxonomy on Contact records.

Manitou internal user accounts (recruiters, hiring managers, administrators) map to Zoho Recruit Users with role assignments and ownership links. Zoho Recruit requires at least two Users to be pre-created in the account before the migration tool can run; we coordinate with the customer's admin to provision the migration user with Data Migration permission. Users without an existing Zoho account cannot be migrated and are flagged in the reconciliation queue.

Manitou's configurable hiring stages (e.g., Screening, Interview, Offer, Hired) are documented as a named taxonomy during scoping. Zoho Recruit's hiring pipeline stages are configured inside the Job Opening module. We do not migrate pipeline automation rules or visual stage layouts because Manitou does not export these as structured data. We deliver a stage mapping table and a written recommendation for each Zoho Recruit pipeline stage the customer's admin should create to approximate the existing Manitou hiring process.

Skill tags and competency tags attached to candidates migrate as text tags linked to Zoho Recruit Candidate records. Skill taxonomies in Manitou that are structured (hierarchical or categorized) are flattened to plain text tags during migration and flagged as candidates for Zoho Recruit's skills taxonomy normalization during post-migration admin review.

Recruiter notes and structured evaluations attached to candidates or applications migrate to Zoho Recruit Notes linked to the corresponding Candidate record. We preserve evaluation scores and content as free-text Note bodies. Any structured evaluation rubrics from Manitou are documented as a field mapping note for the customer's admin to configure as custom Candidate fields in Zoho Recruit if the scoring model should remain structured post-migration.

Resume files, cover letters, portfolio documents, and other attachments linked to candidates migrate as Zoho Recruit Attachments. Zoho Recruit's migration tool requires a specific zip file structure with a Data folder containing CSV files and an Attachments folder containing source files with values in the CSV pointing to attachment filenames. We ensure this structure is maintained during the transform phase. Document formatting and storage path names may change during migration; we document original storage paths for audit purposes.

If Manitou's ATS includes campaign or sourcing initiative records tied to job postings, these map to Zoho Recruit Campaigns. Campaign records must be imported before Candidates per Zoho's import sequence. We flag any campaign-like objects in the Manitou export for customer confirmation during scoping because Manitou's campaign object may be scoped to the CRM module rather than the ATS module.

Manitou's Time & Expenses module, which serves staffing agencies billing candidates on a time-and-materials basis, does not have a direct equivalent in Zoho Recruit's ATS module. We flag Time & Expenses records during scoping and recommend the customer evaluate Zoho Invoice or Zoho Books as a separate integration or migration scope if historical billing data must be preserved. We do not migrate this module as part of the standard ATS migration scope.