Migrate from Manatal to Crelate

Manatal Candidates map to Crelate People records. All profile fields (name, email, phone, address, employment history) migrate directly. Custom fields organized under custom categories in Manatal map to Crelate custom fields, preserving field names, data types, and values. Stage history (candidate-to-job pipeline stages) migrates as Crelate Activity records with stage-transition timestamps. Resume files migrate as Crelate Document records attached to the Person. Tags migrate as-is and appear in Crelate's tag system.

Manatal Jobs map directly to Crelate Jobs. The job name, description, status, assigned users, and creation date transfer. Manatal's configurable pipeline stages per Job map to Crelate pipeline stages, preserving custom stage names and ordering. Candidate-to-stage assignments migrate as Crelate Activities or Job Application records linked to the Person and Job. Job vacancy limits from Manatal (differing by plan) are not enforced in Crelate migration; the customer's Crelate plan limits apply post-migration.

Manatal Organizations (clients or internal departments) map to Crelate Clients. Manatal's Organization import uses name-only deduplication and silently skips matching names. We preprocess the source dataset to identify and resolve naming conflicts before generating the Crelate import file, preserving all records. Organization contact information, address, and custom fields migrate to equivalent Crelate Client fields.

Manatal custom fields organized under custom categories migrate to Crelate custom fields on the Person object. We preserve field names, data types, and values. Some legacy custom field structures with non-standard IDs from older Manatal accounts may require remapping if the field schema has drifted. Admin-level access is required in Manatal to view custom field definitions; we coordinate this access during scoping.

Manatal pipeline stages are defined per Job. We migrate the full stage sequence including custom stage names and ordering. Each Manatal pipeline becomes a Crelate pipeline with stage values configured to match. Stage-to-candidate assignments at migration time are preserved as Crelate Job Application records or Activity entries depending on Crelate's data model at the destination.

Manatal activity logs capture user actions on candidates and jobs. These map to Crelate Activity records with activity type (call, email, meeting, task), timestamp, actor attribution, and notes. All timestamps in Manatal exports are in UTC; we normalize them during mapping and flag any timezone-sensitive date fields for customer review before final import. High-volume activity logs may require API pagination chunking to avoid rate limit responses.

Tags are flat label objects in Manatal applied to candidates and jobs. We migrate all tag assignments preserving the tag names across the dataset. Tags appear in Crelate's tag system attached to the corresponding Person, Job, or Client record.

Manatal user accounts with roles and permissions migrate as Crelate User records. The Manatal internal user ID and role assignments are preserved as custom properties in Crelate for audit. SSO configuration and User Groups in Manatal do not migrate; SSO must be reconfigured in Crelate's settings by the customer's admin post-migration.

Resume files and other attachments referenced in Manatal candidate profiles migrate as Crelate Document records attached to the Person. We migrate document metadata (filename, file type, upload date, attached-to record). Binary file transfer depends on Manatal's export capabilities for the Professional/Enterprise tier (non-API export may require manual file download for binary attachments).

Manatal includes CRM features for agencies tracking client relationships, placements, and commission revenue. These records map to Crelate Client records supplemented with custom fields for placement data and revenue tracking. If Manatal uses dedicated CRM objects (separate from Organizations) for placement records, we map them to Crelate Jobs or a custom CRM object depending on Crelate's configuration at the destination.

Manatal Workflow automations trigger on events such as stage transitions or candidate actions. They are available only on Enterprise and Enterprise Plus plans with undocumented fair-usage limits. We document every active automation rule including its trigger, conditions, and actions in a written inventory delivered to the customer for rebuild in Crelate's workflow builder. We do not migrate automation logic as executable code because Manatal and Crelate use different automation models.

Manatal's candidate-to-job assignments, including pipeline stage assignments and application date, map to Crelate Job Application records linking the Person to the Job. We resolve the Person and Job references during migration so that the Crelate Job Application record is created with the correct foreign key references. Application status and source tracking migrate as Activity records or custom fields on the Job Application.