Migrate from Recooty to Zoho Recruit

Recooty Job records map to Zoho Recruit Job Opening. We map Recooty's title, description, location, department, employment type, and publishing status to Zoho's Job Opening fields. The Recooty job ID is preserved as a custom field recooty_job_id__c for cross-reference. Job Requisition Management fields in Zoho (req_number, hiring_team, approval status) are set to defaults unless the customer has structured requisition data in Recooty.

Recooty Candidate records map to Zoho Recruit Candidate. Pre-flight is required: Zoho mandates Last Name as a non-null field. Recooty does not enforce Last Name, so candidates with null or placeholder last names are flagged during scoping and resolved with a 'Not Provided' default or by splitting a full-name field. Email address becomes the primary deduplication key across the Zoho Candidate table.

Recooty visual pipelines per job (Applied, Screening, Interview, Offer, Hired or customer-configured stages) map to Zoho Recruit's customizable pipeline stages on the Job Opening. Stage names and order transfer directly. We preserve the stage transition timestamps as candidate activity history in Zoho's interview and task records.

Recooty Interview records (date, time, type, interviewer, candidate link) split into Zoho Recruit Interview records and a linked Task record for interviewer preparation. Calendar sync links from Recooty do not transfer; Zoho's own Google Calendar and Zoho Calendar integration is configured post-migration. Self-scheduling links are not migrated and must be rebuilt in Zoho.

Recooty application records (candidate ID + job ID + application date + source) map to the Zoho Candidate's association with a Job Opening. The application source field (Indeed, LinkedIn, direct) migrates as a text field; Zoho's Source Booster integration is configured separately post-migration to replace Recooty's board-level posting history.

Recooty custom candidate fields on Business and Enterprise plans map to Zoho Recruit custom fields on the Candidate module. Zoho Standard allows 50 custom fields per module; Enterprise allows 300. We pre-create destination fields during schema design, match data types (text, number, date, picklist), and flag any fields that exceed Zoho's tier limit for tier upgrade or field consolidation.

Recooty custom job fields on Business and Enterprise plans map to Zoho Recruit custom fields on the Job Opening module. Same tier limits apply (50 Standard, 300 Enterprise). Job-level custom fields used for department classification or employment type encoding are mapped before job import begins.

Recooty team members map to Zoho Recruit Users. Matching is by email address. Any Recooty owner not found in the Zoho destination org is placed in a reconciliation queue for the customer's admin to provision before candidate import begins, since OwnerId references on Candidate records must be valid Zoho User IDs.

Recooty GDPR consent records (opt-in status, consent date, retention policy) map to custom fields on the Zoho Candidate record and an accompanying note with audit detail. Any candidate whose consent record shows a lapse or expiry during the migration window is flagged in the reconciliation report so the customer's admin can re-obtain consent before the candidate is contacted from Zoho.

Recooty candidate notes migrate to Zoho Recruit Note records linked to the Candidate. Rich text formatting is preserved where possible; embedded file attachments migrate as separate Zoho Document Library entries linked to the Candidate.

Recooty tasks linked to candidate records map to Zoho Recruit Task records with Status, Priority, and due date preserved. Task assignment migrates by resolving the Recooty owner email to the corresponding Zoho User ID. Completed status and timestamp transfer directly.

Recooty's drag-and-drop branded career page builder (Growth and above) generates hosted pages with builder state that cannot be exported as structured data. We preserve the job content and branding metadata but treat the career site URL, page layout, and builder state as non-migratable. The customer rebuilds the career page in Zoho Recruit's native Career Site builder post-migration.

Recooty's board-level posting history (which job was published to which board at what time) is stored in Recooty's internal logs and is not exportable as structured data. We preserve the job content and the list of boards the customer reported using, but board publishing history is treated as non-migratable. The customer re-publishes jobs through Zoho Recruit's own job board integrations and Source Booster post-migration.