Migrate from Manitou ATS to Crelate

Manitou's Applicant Bank candidates map to Crelate Contacts. We extract name, email, phone, address, skills, and application history from the Applicant Bank export. Crelate requires Name as a required attribute; we map the candidate's full name into Crelate's name fields. We preserve the original Manitou candidate ID in a custom field manitou_candidate_id__c for reconciliation purposes. Duplicate candidates identified during deduplication (same name and email across multiple application records) are resolved before Crelate import to avoid creating orphaned Contact records.

Manitou Job Requisitions map to Crelate Job records. We preserve job title, description, status, department, and hiring manager. Crelate's Job object represents an open requisition that candidates apply to; the migration maps the job's active or archived status accordingly. Custom fields on job requisitions migrate to Crelate custom fields on the Job record if the Crelate plan supports custom fields on Jobs. Internal job board URLs and external posting URLs are preserved as text fields.

Manitou Applications (the join between Candidate and Job Requisition with pipeline stage and timestamp history) map to Crelate Opportunities. Each application represents a placement process that moves through pipeline stages; in Crelate's model, the Opportunity represents the candidate's progression toward placement. We map the original Manitou application date and stage history into Opportunity fields and activity timeline entries. The Opportunity is linked to the Contact (from the Candidate mapping) and optionally to a Company if the placement is for a client.

Manitou pipeline stage names and order are documented during scoping from individual job records because they do not export as structured data. We produce a written stage taxonomy inventory listing every unique stage name, its position in the workflow, and any automation triggers documented in Manitou. Your Crelate administrator configures matching Opportunity pipeline stages in Crelate before go-live. Stage-specific automation triggers in Manitou do not migrate and are documented for rebuild in Crelate's automation rules.

Manitou CRM Companies map to Crelate Companies. We preserve company name, address, website, industry, and associated contact links. Crelate requires Name as a required attribute for Company records. Company records are created before Contact records with linked Company relationships so that the lookup reference is satisfied at import time. Custom CRM fields on Manitou companies require Crelate custom field configuration before migration.

Manitou CRM Contacts map to Crelate Contacts. These are distinct from Applicant Bank candidates (which also map to Contacts) but represent client or prospect contacts rather than job applicants. We deduplicate against candidate Contacts during the transform phase using name and email; if the same person appears as both a candidate and a client contact, we preserve both records and link them. Crelate's lookup model supports multiple Contact roles per Company.

Manitou internal users (recruiters, hiring managers, administrators) map to Crelate Users. We resolve users by email match against the destination Crelate tenant's User list. Crelate requires an administrator to enable API access for the migration user in Settings | Advanced Settings | User Roles before any API-based import begins. Manitou role assignments are documented and mapped to Crelate role equivalents during configuration.

Manitou skill tags and competency tags attached to candidates migrate to Crelate Tags. Crelate's Tag system uses category keys (with 'Default' for the default category) and tag names. We extract skill names as plain text and create corresponding Tags in Crelate during migration. If Manitou uses a structured skill taxonomy with hierarchies, we flatten to the most granular level and document the taxonomy structure for the customer's admin to optionally configure as Crelate Tag categories post-migration.

Manitou recruiter notes and structured evaluations attached to applications or candidates migrate to Crelate Notes. Crelate requires Body as a required attribute for Note records. We preserve evaluation scores as text within the Note body or migrate them to custom fields if Crelate custom fields are configured on the Contact record. Notes are linked to the parent Contact record via Crelate's ContentDocumentLink model. Evaluation timestamps are preserved in the Note creation date field.

Resume files, cover letters, portfolio documents, and other attachments linked to candidates or jobs migrate to Crelate as ContentDocument records attached to the relevant Contact or Job record via ContentDocumentLink. We extract binary attachments from the Manitou export and re-attach them to the corresponding Crelate records. Document formatting (PDF versus Word) is preserved. We note that Crelate's storage limits vary by plan tier; large resume libraries may require Business Plus or Enterprise for adequate storage headroom.

Manitou Time and Expenses records do not map to a Crelate object. Crelate is an ATS and recruiting CRM; it does not include time tracking or billing modules. We flag all Time and Expenses records during scoping and deliver them as a separate CSV inventory for the customer's finance or operations team to import into their preferred time-tracking tool. This is a conscious scope boundary, not a data loss gap.

Manitou Invoicing and Accounting records do not map to a Crelate object. Crelate does not include financial or accounting modules. We flag all Invoicing and Accounting records during scoping and deliver them as a separate CSV inventory. Customers who use Manitou's full suite for billing should evaluate dedicated accounting platforms (QuickBooks, Xero, NetSuite) post-migration; this is explicitly scoped as outside ATS migration scope.