Migrate from Ceipal ATS to Zoho Recruit

Ceipal Applicants map to Zoho Recruit Candidates with full profile data: name, email, phone, skills, location, and source attribution. We extract parsed resume fields (structured skills, work history, education) via Ceipal's API and populate Zoho Recruit's corresponding candidate fields directly, triggering Zoho's parsing pipeline for any raw resume attached. Pre-migration profiling flags records where Ceipal's email field contains a Dice or job board portal address rather than the candidate's personal or professional address, preserving the source email in a secondary field for manual correction.

Ceipal Jobs (title, description, location, requirements, pipeline stages) map to Zoho Recruit Job Openings. Ceipal's custom job stages migrate as Zoho Recruit stage values in the vacancy workflow. Job status (Open, On Hold, Closed, Filled) maps to Zoho Recruit's status field. If the Ceipal job record contains a Client or Lead association, we preserve that as a Zoho Recruit Client lookup.

Submissions link an Applicant to a Job with submission date, status, and recruiter assignment. This is the most relationship-sensitive record in the migration: breaking the Applicant-to-Job link leaves candidates unattached to requisitions in Zoho Recruit. We build a Submission lookup table during the staging phase that maps each Ceipal submission to the resolved Zoho Candidate ID and Zoho Job Opening ID, then creates the association in Zoho Recruit's candidate-to-job pipeline during import.

Ceipal Client records (company name, contact info, billing details) map to Zoho Recruit Client. All associated address data, industry, and client-specific notes transfer as structured fields. The Client record is created before any Candidate or Job Opening import so that lookups are satisfied at the moment of insert.

Ceipal Leads are distinct from Clients and carry separate status fields and source attribution. We map Ceipal Lead records to Zoho Recruit Candidates, preserving the original lead status in a custom field ceipal_lead_status__c to maintain segmentation logic post-migration. Source attribution (job board, referral, direct) migrates to Zoho Recruit's Source field on the Candidate.

Ceipal Placements tie an Applicant to a Job under a Client, with start date, compensation, and billing details. Zoho Recruit does not have a native Placement object; we map Placements to a combination of Zoho Candidate records with custom fields for compensation, start_date__c, placement_status__c, and a lookup to the related Job Opening and Client. The customer chooses whether to store placement history on the Candidate record or in a Zoho custom module configured during staging.

Ceipal stores documents against Applicants, Jobs, and Placements (resumes, offer letters, contracts). We transfer binary blobs via Ceipal's document API where available, falling back to URL-based document retrieval from Ceipal's storage. Each document is attached to the corresponding Zoho Recruit record (Candidate for resumes, Client for contracts, Job Opening for job descriptions) with the original file name and MIME type preserved.

TalentBench is Ceipal's searchable resume repository containing parsed resume fields alongside raw documents. We migrate the parsed fields (skills, experience, education, certifications) into Zoho Recruit's structured Candidate fields and attach the raw resume as a Zoho Recruit attachment. This preserves searchability in Zoho Recruit from day one without requiring candidates to be re-parsed in the UI, which would create a double-processing gap during the migration window.

Ceipal allows admins to add custom columns to grids and custom properties on Applicants, Jobs, and Placements. These are organization-specific and must be enumerated during discovery scoping. We create matching custom fields in Zoho Recruit before data import begins. Custom fields that do not have a Zoho Recruit equivalent are flagged in the mapping document for the customer to decide whether to map to an existing field, create a new custom field, or archive the data.

Ceipal WorkForce stores employee profiles, compensation, department, and location under a separate pricing tier. Zoho Recruit does not have a native HR or workforce module. We scope WorkForce migration based on the customer's use case: if the records represent placed contractors or staffing employees, they map to Zoho Recruit Candidates with custom fields for department__c, employment_type__c, and hourly_rate__c. If the customer requires a full HR module, we recommend a parallel Zoho People implementation and migrate WorkForce data there as a separate scope.

Ceipal WorkForce timesheet records track hours per employee per period with approver metadata. Zoho Recruit has no native timesheet object. We map timesheet entries to Zoho Recruit Task or Event records with custom fields period__c, hours_logged__c, and approver__c, preserving the date, hours, and approval status. This requires a WorkForce module license on the source and a Zoho custom field configuration on the destination.

WorkForce expense records capture amount, category, employee, and submission date. We map expense records with full line-item detail (amount, category, submission date, employee reference) to Zoho Recruit Notes attached to the corresponding Candidate or Client record, or to a Zoho custom module if the customer's compliance workflow requires structured expense records. Category labels map to a Zoho picklist that we configure during staging.

Ceipal Users (recruiters, hiring managers, administrators) are mapped to Zoho Recruit Users by email address match. We enumerate all distinct Ceipal users referenced on Applicant, Job, Submission, and Placement records during discovery. Any Ceipal user without a matching Zoho Recruit User account enters a reconciliation queue for the customer's admin to provision before record import resumes.