Migrate from eArcu to Zoho Recruit

eArcu candidate records (name, contact details, work history, custom profile fields) map to Zoho Recruit Candidate. Zoho requires Last Name as a mandatory field; candidates without a last name in eArcu receive the value 'not provided' as a migration placeholder. We preserve any custom profile fields as Zoho custom fields on the Candidate module, subject to the edition field-count limit (50 on Standard, 300 on Enterprise). Assessment scores stored as linked records on the candidate in eArcu migrate to Zoho custom fields on the Candidate record because Zoho Recruit has no native assessment-results object.

eArcu requisitions (title, department, location, employment type, pipeline assignment) map to Zoho Recruit Job Opening. We preserve the source requisition status and any internal requisition ID as a Zoho custom field for audit traceability. Zoho Recruit's active job opening limit scales by tier (1 on Free, 10 on Standard, 20 on Enterprise per recruiter license); we verify the customer's seat count and job volume against these limits during scoping.

eArcu application records link a Candidate to a Requisition with timestamps for each stage transition. Zoho Recruit models applications as part of the Candidate record's related list rather than a standalone object. We create a Candidate-Job Opening association for each application and preserve the stage-entry date timestamps. The original eArcu application status maps to Zoho's pipeline stage status values.

eArcu's configurable pipeline stages per requisition type do not have a direct data export; they are platform-native pipeline configurations. We extract the full stage label and sequence from each requisition's pipeline definition and deliver a Zoho Recruit Pipeline configuration guide that the customer's admin uses to rebuild the pipeline stages in Zoho's visual pipeline editor. Stage-entry timestamps per application migrate as date fields on the Candidate record.

eArcu cognitive test results, personality questionnaire scores, and situational judgement data are stored as linked records attached to the candidate. Zoho Recruit does not have a native assessment-results object; we map raw scores and assessment types to custom fields on the Candidate record. The Zoho Professional tier includes an Assessments module for running new assessments post-migration, but historical scores from eArcu must land as custom fields. We recommend assigning assessment fields to a dedicated field group during mapping for logical grouping in Zoho's layout editor.

eArcu user accounts with roles and permissions map to Zoho Recruit Users. Zoho requires that users with an existing separate Zoho Recruit account must close that account before they can be imported into the company's Recruit account. We extract the full user roster (name, email, role, department) and coordinate with the customer's admin to provision any missing Zoho Users and resolve duplicate account issues before the user import phase. Permissions and department hierarchy map to Zoho's Role and Department structure.

CVs, cover letters, and supporting files attached to candidates or applications in eArcu are binary blobs that we extract from the platform's document store and re-upload to Zoho Recruit as Candidate Attachments. We preserve the original filename, file type, and attachment date. Large-volume attachment migrations (over 2 GB total) may require chunking and a dedicated upload session to avoid timeout errors in Zoho Recruit's import tool.

eArcu offer records (compensation details, start dates, approval status) map to Zoho Recruit's Offer object if the customer's Zoho Recruit edition supports it, or to custom fields on the Candidate record as a fallback. Zoho Recruit's Offer Letter Templates (50 on Professional, 100 on Enterprise) are post-migration assets for generating new offers; historical offer data migrates as read-only records. We map offer status (accepted, rejected, pending) to Zoho's offer status field where available.

eArcu career portal pages, job board widgets, and branding assets are HTML and CSS configurations stored as platform-native content rather than structured database records. These do not export as discrete data and cannot be meaningfully transferred to Zoho Recruit. We flag the existence and structure of the eArcu career site in the migration scope document. Zoho Recruit's Branded Careers Site builder (available on Standard and above) is the replacement vehicle; the customer's web team or a Zoho partner rebuilds the careers page content post-migration.

Animated onboarding packages and structured onboarding task sequences are platform-native eArcu configurations that cannot be exported as discrete records. We do not migrate these. We document the existing onboarding structure (task list, sequence, assigned content) as a reference guide that the customer's HR admin uses to configure equivalent onboarding steps in Zoho Recruit or a separate onboarding tool. Any offer-to-onboarding handoff data already captured in eArcu offer records is preserved in the offer migration.

If eArcu contains custom objects beyond the standard schema, we map each to a Zoho Recruit Custom Module created via Setup > Customization > Modules. Custom module field types (text, picklist, lookup, etc.) are matched to Zoho's available field types. The Standard edition limits custom fields to 50 per module; Enterprise allows 300. We verify the target edition's field-count ceiling against the total custom fields in the migration scope during discovery and recommend Enterprise if the scope exceeds Standard's limits.

eArcu's configurable approval workflow configurations on requisitions are platform-native rules that do not export. We document each approval chain (approver role, threshold, conditions) as part of the Zoho Recruit Workflow Rules handoff package. Zoho Recruit's Workflow Rules run on module-level triggers and support approval-type actions on Professional and above. The customer's Zoho admin rebuilds the approval logic post-migration using Zoho's Blueprint or Workflow Rules builder.