Migrate from Eddy to Zoho Recruit

Eddy Employee records map to Zoho Recruit Candidate records. Core fields (first name, last name, email, phone, hire date, employment status) migrate to their Zoho Recruit equivalents. The Eddy job title maps to a custom Candidate field (e.g., edd_previous_title__c) since Zoho Recruit Candidates represent applicants, not employees, and do not natively store employment history without custom fields. Eddy department assignment maps to Zoho Recruit's Department picklist or a custom field. Last Name is mandatory in Zoho Recruit; any Eddy employee record without a last name is flagged and given a 'not provided' placeholder during import per Zoho Recruit's import requirements.

Eddy Employee records may also map to Zoho Recruit Contacts if the organization's Zoho Recruit plan includes the Staffing Agency module and the customer wants to maintain a client-facing Contact record separate from the Candidate recruiting record. We implement this split only when specified in scoping; in most HRMS-to-ATS migrations, a single Candidate record per employee is sufficient. The mapping type is documented as a split decision during scoping rather than a default.

Eddy PTO balances (accrued, used, pending, carry-over) have no native equivalent in Zoho Recruit's ATS object model. We create a custom field group (e.g., edd_pto_accrued__c, edd_pto_used__c, edd_pto_balance__c, edd_pto_policy__c) on the Candidate object to carry balance snapshots at migration time. Active PTO requests are documented as a Note attached to the Candidate record. Balance snapshot is time-stamped at migration export. We flag that any ongoing accrual calculations require the destination to configure Zoho Recruit's workflow rules or a connected time-off tool post-migration.

Eddy Employee documents (offer letters, contracts, signed agreements, tax forms) migrate as Zoho Recruit Candidate attachments. PDF and standard document formats are fully supported. We preserve original file names and apply a directory naming convention (e.g., /EddyMigration/[EmployeeName]/[DocumentType]_[Date].pdf) to maintain organization. Document metadata (document type, upload date, associated employee) migrates as fields on the attachment record where supported by Zoho Recruit's file versioning API.

Eddy onboarding step checklists and task assignments do not have a direct Zoho Recruit equivalent. We extract active onboarding tasks and their completion status, then map these to Zoho Recruit Tasks attached to the Candidate record with the original task name, assignee, due date, and completion status preserved. The workflow structure (sequence of steps, conditional branches) is documented in a written handoff guide; Zoho Recruit's Workflow Rules and Assignment Rules are the closest native replacement, but the customer's admin rebuilds these as they require ATS-specific logic rather than HR-specific logic.

Eddy training completion records (course name, completion date, status, certification expiration) migrate to custom fields on the Zoho Recruit Candidate record or as Notes with structured templates. The field naming convention (e.g., edd_training_[courseid]_completed__c) handles multiple training records per employee. Zoho Recruit's Assessments module (available on Standard and above) can store formal assessment results, but training completion history is typically maintained as custom fields or notes unless the customer licenses a dedicated learning management integration.

The Eddy employee directory (name, title, department, email, phone, location) maps to Zoho Recruit's Contact record and Department configuration. Organizational hierarchy (reporting structure) is preserved as a Note attached to the Contact or as a custom lookup field (edd_manager_id__c) pointing to the manager's Contact record. We extract the full org chart as a JSON structure during scoping and deliver it as a reference document for the customer's admin to configure Zoho Recruit's organizational reporting structure.

Eddy departments map directly to Zoho Recruit Departments. Both platforms store department as a picklist on the primary record. We extract department names and any associated cost center codes and map them to the Zoho Recruit Department object during initial configuration. Parent-child department relationships (division > department > team) are preserved in Zoho Recruit's department hierarchy where the plan supports it.

Eddy payroll data (pay run history, salary information, benefit deduction amounts) cannot migrate into Zoho Recruit because Zoho Recruit has no native payroll module. We extract available payroll records as a CSV export from Eddy (where payroll module data exists) and deliver it as a structured reference file. Pay run history, salary bands, and compensation details are documented as Notes on the Candidate record or stored in a custom field group (edd_salary_band__c, edd_pay_frequency__c) for reference. The customer must configure a payroll system post-migration—Zoho Payroll, Gusto, Rippling, or a similar HRIS integration are the standard replacements.

Eddy company-level settings (org policies, approval rules, locations, benefits configurations, time-off policies) export in limited formats and cannot migrate programmatically to Zoho Recruit. We extract the settings data as a structured reference document and deliver a written configuration guide mapping each Eddy setting to its nearest Zoho Recruit equivalent (Workflow Rules, Assignment Rules, Department configuration, or a Note documenting the original setting for manual reconfiguration). We do not configure these settings inside Zoho Recruit as part of the migration scope.

If Eddy contains internal job postings or requisitions, these map to Zoho Recruit Job Openings. The job title, description, requirements, and posting status migrate directly. Posting channels (internal job board, external job boards) require manual reconfiguration in Zoho Recruit's job distribution settings because Zoho Recruit manages multiposting through its own integrations rather than as a property of the job record.

Eddy benefits enrollment data (health plan selection, 401k participation, dependent information) has no equivalent object in Zoho Recruit's ATS data model. We extract benefits enrollment records as structured Notes attached to the Candidate record with plan name, enrollment date, and coverage level preserved. The customer configures benefits management in a dedicated HRIS (Rippling, Gusto, ADP, or Zoho People) and links it to the employee record via Zoho Recruit's custom field or integration post-migration.

Eddy stores employment history (previous titles, previous employers, promotion dates) as part of the Employee record timeline. Zoho Recruit Candidate does not natively track prior employment history for already-employed candidates. We create a custom multi-line field group (edd_prev_title__c, edd_prev_employer__c, edd_prev_start_date__c, edd_prev_end_date__c) on the Candidate object to carry employment history data. For candidates who were hired via Zoho Recruit and then onboarded in Eddy, the onboarding employment details are preserved as these custom fields.