Migrate from ClearCompany to Zoho Recruit

ClearCompany Candidate records map directly to Zoho Recruit Candidates. We map first_name, last_name, email, phone, source, application status, and any custom fields. Zoho Recruit requires a Last Name value on every Candidate import; records without one are flagged during staging and assigned 'not provided' as a placeholder per Zoho's migration documentation. Candidate-to-Job association is preserved through the job_opening_id reference migrated as a lookup field.

ClearCompany Job records (title, department, location, status, description) map to Zoho Recruit Job Openings. Active and closed positions migrate. The job-to-candidate association migrates as a lookup relationship so historical applicant counts remain intact. Job Opening owner resolves against the Zoho Recruit User table by email match during migration.

ClearCompany Employee records (employment details, department, manager assignment, start date) do not have a native Zoho Recruit equivalent since Zoho Recruit is ATS-focused rather than a full HRMS. We map employees as Candidate records with a custom field employee_status__c set to 'Active' or 'Former', preserving employment details as reference fields. If the customer uses Zoho People (a separate Zoho HRMS product), we scope a parallel migration for those records as a distinct engagement.

ClearCompany Departments (org structure, offices, reporting relationships) map to Zoho Recruit Departments for reference integrity. Parent-child department hierarchy migrates. Departments without a Zoho Recruit equivalent as a data record (ClearCompany's nested org chart) are exported as a structured JSON hierarchy document delivered alongside the CSV import so the customer's admin can reconstruct the org chart manually.

ClearCompany User accounts (name, email, role, active/inactive status) map to Zoho Recruit Users. We resolve by email match. Zoho Recruit flags duplicate email addresses during import; if a Zoho Recruit User account already exists for a given email, the record is held in a reconciliation queue for the customer's admin to close the existing account per Zoho's migration documentation before re-import.

ClearCompany onboarding task checklists and new-hire workflows are exported as structured task definitions with completion status. Zoho Recruit has no native onboarding workflow module. We deliver the onboarding task list as a Zoho Recruit Task export and a written onboarding workflow map documenting task order, assignee role, conditional branching, and completion criteria for the customer's admin to rebuild as Zoho Recruit workflow rules (Professional and above) or manual task checklists.

ClearCompany performance reviews, goals, and calibration data have no Zoho Recruit equivalent. Zoho Recruit is an ATS platform without a performance management module. We export review records as structured reference data and deliver a written performance review inventory with field mapping so the customer's admin can evaluate Zoho Perform (a separate Zoho product) as a rebuild destination if performance tracking is required post-migration.

ClearCompany LMS content (courses, learning paths, completion records, compliance data) has no Zoho Recruit equivalent. We export course metadata and completion records as structured CSV and flag SCORM packages as a separate handling decision: customers choose between importing SCORM packages as static file references (no playback), migrating to Zoho Learn separately, or discontinuing the content library. SCORM is a packaging format requiring a learning platform runtime; it cannot be re-imported as active learning content in Zoho Recruit.

ClearCompany custom fields on Candidates, Employees, and Jobs vary by module tier and tenant configuration. We discover field definitions during scoping, map data types to Zoho Recruit field types (Text, Picklist, Multi-select Picklist, Date, Number, Checkbox), and verify the target Zoho Recruit edition's field limit. Standard edition caps at 50 custom fields per module; Enterprise allows 300. Custom fields on the Standard tier that exceed the cap are held for admin review and mapped to a Notes field as a fallback.

Documents attached to ClearCompany candidate, employee, and job records are exported by reference with file content. We migrate attachments alongside parent records using Zoho Recruit's attachment import path. Files exceeding Zoho Recruit's attachment size threshold are flagged during staging and delivered as a separate file package with reference mapping for manual upload.

ClearCompany integration configurations including connected accounts (ADP, LinkedIn, Indeed, assessment vendors) cannot export credentials for security reasons. We export integration reference data (connected account names, sync rules, configured field mappings) as a written integration inventory. The customer's admin re-establishes each connected integration manually at the destination, re-authenticates via OAuth, and re-maps sync rules per Zoho Recruit's connector configuration.

ClearCompany custom objects (module-tier dependent) map to Zoho Recruit Custom Modules. We pre-create the destination module schema in Zoho Recruit, including custom field definitions, before any data import. Lookup relationships between custom modules and standard modules (Candidate, Job Opening) are resolved at migration time. Note that Lookup and formula fields are gated to Zoho Recruit Professional and above; Standard edition migrations with custom objects that include lookups require an edition upgrade or schema redesign.