Migrate from Manatal to Zoho Recruit

Manatal Candidates migrate to Zoho Recruit Candidates with all profile fields, tags, stage history, and activity logs. Zoho Recruit requires Last Name as a mandatory field; any Manatal candidate without a Last Name value is flagged during preprocessing and assigned a placeholder value ('Not Provided') per Zoho Recruit's own migration documentation. We preserve the full original name in a custom Last Name extension field for audit. Resume files migrate as attachments linked to the Candidate record.

Manatal Jobs map to Zoho Recruit Job Openings. The Manatal job's pipeline stages map to Zoho Recruit's hiring pipeline stages on a per-job basis. If Manatal uses multiple pipelines, we configure Zoho Recruit's job-specific pipeline accordingly. Job status (Active/Closed/Draft) migrates to Zoho Recruit's Opening Status field. Assigned recruiters migrate as Owner lookups resolved by email match.

Manatal Organizations (representing clients or departments) map to Zoho Recruit Client records. Manatal's Organization import deduplicates by name only, silently skipping matches, so we preprocess the source dataset to merge or rename conflicting organization names before generating the Zoho Recruit import file. Client records must exist before Candidates with Client associations are imported to satisfy the lookup dependency.

Manatal custom fields on Candidates migrate to Zoho Recruit custom fields per module (50 field limit on Standard, 300 on Enterprise). If the source account exceeds the target tier's field limit, we identify the overflow fields during scoping and recommend consolidation or placement in a custom module. Field types are mapped: Manatal text to Zoho Recruit single-line or multi-line text, Manatal date to Zoho Recruit date, Manatal picklist to Zoho Recruit dropdown.

Manatal's per-job pipeline stages migrate to Zoho Recruit's hiring pipeline stages. Each Manatal stage becomes a Zoho Recruit stage with the original stage name and order preserved. Custom stage colors from Manatal are not transferred; Zoho Recruit's default stage coloring applies. We configure stage order before any Candidate migration so that stage assignments are valid at insert time.

Manatal activity logs (calls, emails, meetings, notes, tasks) migrate to Zoho Recruit equivalent objects: call logs become Tasks with TaskSubtype=Call, meeting logs become Events, email logs become Notes attached to the Candidate, and standalone tasks become Tasks. Timestamps are preserved in UTC; Zoho Recruit displays them in the org's configured timezone. Very high-volume activity logs may require chunked import due to API pagination limits.

Manatal tags on Candidates and Jobs migrate to Zoho Recruit Tags. Tags are flat labels; no tag hierarchy exists in either platform. We preserve the full tag name across the dataset. Tags used for candidate classification become Zoho Recruit Tags that can be applied to Candidates, Job Openings, and Clients.

Manatal resume files attached to Candidates migrate as Zoho Recruit Attachments linked to the Candidate record. We migrate file metadata including filename, upload date, and file size. Binary file transfer depends on Manatal's export capabilities for the Professional or Enterprise plan. If the account is on Professional without API access, we coordinate CSV/XLS export workflows via the admin panel.

Manatal user accounts with roles and permissions migrate to Zoho Recruit Users. We match Manatal users by email address to existing Zoho Recruit users. Any Manatal user without a matching Zoho Recruit account goes to a reconciliation queue for the admin to provision. Manatal role assignments (Admin, Recruiter, Hiring Manager) are preserved as custom fields on the User record for reference.

Manatal workflow automations (available on Enterprise and Enterprise Plus) are documented for rebuild in Zoho Recruit. We deliver a written inventory of every active Manatal automation rule including its trigger, conditions, actions, and recommended Zoho Recruit equivalent (Workflow Rule or Blueprint). We do not migrate automation logic programmatically because Manatal's automation model is structurally different from Zoho Recruit's. Rebuild is performed by the customer's admin post-migration.

Manatal's built-in CRM features for agencies tracking placements, commission revenue, and client relationships migrate to Zoho Recruit custom modules (Enterprise) or as structured custom fields on Candidate and Client objects (Standard/Professional). We assess the source CRM data volume and destination tier during scoping to determine the appropriate schema.

Manatal's AI candidate scoring and recommendation data does not migrate because Zoho Recruit's AI model (Zia) operates independently and recalculates scores based on its own matching logic against job requirements. We flag the AI scoring fields in the source data and note them for the customer's admin to review post-migration. The raw candidate profile data that feeds AI scoring migrates normally.