Migrate from Eploy to Zoho Recruit

Eploy Jobs map directly to Zoho Recruit Job Openings. We preserve job title, department, location, salary bands, and the associated workflow assignment. Custom job fields (Eploy's custom property schema) map to Zoho Recruit custom fields on the Job Opening module; Zoho Standard allows up to 50 custom fields per module on the Standard plan, and up to 300 on Enterprise. If Eploy custom field count exceeds the destination limit, we collapse secondary fields into a JSON blob stored in a Notes field and document the collapse for the customer's admin to address post-migration.

Eploy Candidate records map to Zoho Recruit Candidates with a critical gap: Last Name is mandatory in Zoho Recruit and any record without a Last Name value is silently ignored during import. We detect missing Last Name values during extraction, flag them in the migration report, and either split full-name fields where available or write 'Not Provided' as a placeholder per Zoho Recruit's own migration documentation. Contact details, skills, application history, and status fields map 1:1. Duplicate candidate detection uses email as the dedupe key, consistent with Zoho Recruit's standard import behaviour.

Eploy workflow stages are fully custom per organisation with no canonical list in the API; we discover them by querying active job records and aggregating distinct stage values into a mapping table during scoping. Each Eploy stage maps to a Zoho Recruit pipeline stage value that we configure in Setup > Recruit > Pipelines before migration. Stage transition timestamps from Eploy migrate as audit timestamps on the candidate record. We require customer confirmation of the stage mapping table before any candidate records are written to Zoho Recruit.

Eploy Offer records (salary, start date, role details, e-signature status) map to Zoho Recruit Offer records, which are available from the Standard plan upwards. We migrate active offers and preserve the e-signature audit trail where the API exposes it. Zoho Recruit's Offer module supports offer letter templates (50 at Standard, 100 at Enterprise); we map Eploy's offer letter references to the nearest equivalent template or store the original Eploy document as an attachment on the Offer record.

Eploy's Hiring Manager Portal assignments (specific users tied to jobs and workflow stages) map to Zoho Recruit User assignments on Job Openings and as Hiring Manager portal access. Role-based permissions in Eploy may not translate directly; we flag any role that has no Zoho Recruit equivalent (for example, Eploy-specific workflow escalation roles) in the migration report. Customer admin resolves these during the post-migration configuration window.

Eploy's onboarding module lives in a separate schema that may not expose all fields via the standard API. New hire information, reference collection, and contract status that are accessible via API migrate as structured fields on the Zoho Recruit Candidate record. We flag any onboarding objects that return partial schemas and recommend manual CSV export for compliance documents and reference records that cannot be extracted automatically, because Zoho Recruit does not have a separate onboarding module and converts candidates directly to employees in Zoho People.

Eploy referral records link an employee to a referred candidate with reward status. We preserve referral attribution by writing the referring employee's name to a Zoho Recruit custom field (for example, referral_source__c) and setting the Candidate Source to 'Employee Referral'. The reward status maps to a custom picklist or text field since Zoho Recruit's standard Source field does not carry reward status natively.

Eploy Talent Pools are saved candidate collections used for future roles. We migrate pool memberships by writing each pool name as a Zoho Recruit Tag on the Candidate record, preserving the candidate-to-pool association. If the customer uses Talent Pools as formal segments with shared attributes, we alternatively create a custom multi-select picklist field on the Candidate module to represent pool membership, with the choice made during scoping.

Eploy organisations add custom fields to jobs, candidates, and other objects. We detect the full custom property schema during discovery and create corresponding custom fields in Zoho Recruit's module builder before migration. Field type mapping applies: text maps to single-line text, multi-select maps to multi-select picklist, date maps to date, and numeric maps to number. Fields that cannot map directly (for example, Eploy-specific structured data types with no Zoho equivalent) are serialised into a JSON text field with documentation provided to the customer's admin.

Assessment scores and results attached to candidate records in Eploy migrate as structured custom fields on the Zoho Recruit Candidate module where the API exposes numerical or categorical scores. Visual assessment scores that lack a structured API equivalent are migrated as attachments with the original filename preserved, so the information is not lost even if the scoring format does not transfer cleanly. The customer admin can then configure Zoho Recruit's native assessment integration post-migration if desired.

Resume and document attachments in Eploy are served as download URLs rather than inline blobs. We enumerate all attachment URLs per candidate record, download each file to temporary encrypted storage, then upload to Zoho Recruit's attachment endpoint linked to the corresponding Candidate or Job Opening record. Filenames and the association back to the parent record are preserved. For compliance-heavy sectors with hundreds of attachments per candidate, this pass extends migration time and requires storage headroom; we scope this separately during discovery.

Email and SMS threads tied to candidates in Eploy migrate as Zoho Recruit Notes linked to the Candidate record, preserving email content and timestamps. Formatting may flatten in transit; we document the formatting transformation for the customer's admin. SMS content migrates as Notes with an sms: prefix in the note title to distinguish it from email threads. This approach mirrors Zoho Recruit's own data migration documentation, which maps communication history to the Notes module.