Migrate from eRecruiter to Zoho Recruit

eRecruiter Candidates map directly to Zoho Recruit Candidates. Core fields — FirstName, LastName, Email, Phone, CurrentTitle, CurrentCompany, CurrentLocation, Skills, Summary — migrate as standard Zoho Recruit Candidate fields. CV Parsing output (experience duration, education level, language proficiency, skills tags) migrates as custom candidate fields because eRecruiter's parsed schema varies by CV template and parsing version. We treat all parsed fields as custom during migration and validate the Zoho Recruit target schema (50 custom fields per module on Standard, 300 on Professional and Enterprise) before writing. GDPR consent flags and data retention metadata from eRecruiter's RODO module migrate to custom consent fields and are flagged in the delivery report for the customer to implement a re-consent workflow post-migration.

eRecruiter Applications link a Candidate to a Job and carry status, pipeline stage, rating, and notes. These map to Zoho Recruit Job Applications with Status mapped to Zoho's application stage values (New, Screening, Interview, Offer, Hired, Rejected). Custom application fields migrate to Zoho custom fields within the same field-count limit. The eRecruiter application rating (scorecard or thumbs up/down) migrates as a custom picklist or numeric field in Zoho Recruit. Application history — stage transitions with timestamps — migrates as a structured note or custom timeline field because Zoho Recruit Job Applications do not expose a native stage-history object.

eRecruiter Jobs (title, description HTML, location, department, employment type, publication status) map to Zoho Recruit Job Openings. We preserve HTML descriptions as-is, location as structured address fields, and employment type as a picklist value mapped to Zoho's Job Opening employment type field. The eRecruiter publication status (active, paused, closed) maps to Zoho Recruit's Opening Status. If eRecruiter jobs are linked to Pracuj.pl or other Polish job boards, the Zoho Recruit equivalent requires re-publishing manually or via Zoho's job board integrations (Indeed, LinkedIn, Glassdoor) post-migration; job board URLs and posting IDs do not carry forward.

eRecruiter Company entities map to Zoho Recruit Clients (in Staffing edition) or Accounts (in Corporate edition). The mapping is configuration-dependent: we confirm the destination edition during scoping. Company name, website, industry, size, and address fields map to their Zoho equivalents. eRecruiter's dedicated Company Import API endpoint with ExternalId matching translates to Zoho's Client or Account import using the same external ID as the dedupe key. Companies without a name receive a placeholder value ('Not Provided') per Zoho's mandatory field requirement.

eRecruiter Users (name, email, role, department) map to Zoho Recruit Users. Role naming differs between platforms, so we capture the eRecruiter role name in a custom field for reconciliation. We resolve users by email match against the Zoho Recruit destination. Any eRecruiter User without a matching Zoho Recruit account enters a reconciliation queue; the customer provisions missing users before record import resumes. Users with separate pre-existing Zoho Recruit accounts cannot be imported through Zoho's Data Migration wizard — they must close the separate account first.

Department is a referenced entity on Jobs and Users in eRecruiter. We migrate Departments as independent records and reattach them to the corresponding Job Opening records in Zoho Recruit. Zoho Recruit's Standard, Professional, and Enterprise editions include Department support; the Free edition does not. If the destination is on the Free plan, Departments are skipped and referenced as text fields on Jobs.

Location data on Jobs — city, region, country — migrates as structured address components in Zoho Recruit. If eRecruiter jobs use multi-location posting, we handle location mapping to Zoho's location field structure. Postal code and country code format differences (Polish KOD POCZTOWY versus Zoho's standard address fields) are normalized during the transform step.

Documents attached to Candidates are identified by DocumentTypeName, Filename, and the parent Candidate's ID in eRecruiter. The API does not expose a standalone document download endpoint that resolves attachments without parent context. We must migrate Candidates first, record the Zoho Recruit Candidate ID, then transfer binary attachments with the new Zoho Candidate ID as the parent reference. Orphaned documents — those without a valid parent record — cannot be reliably mapped and are listed in the delivery report for manual handling.

Application attachments follow the same parent-record constraint as candidate attachments. We migrate Applications after Candidates, record the Zoho Recruit Application ID, then transfer binary attachments with the resolved Zoho Application ID as the parent reference. CV files, cover letters, portfolio documents, and reference letters attach to the Application record where they were stored in eRecruiter.

eRecruiter structured evaluation ratings are stored as part of the Application record or as linked feedback entries. These migrate as custom fields on the Job Application in Zoho Recruit. If the customer uses Zoho Recruit's native Interview Feedback Form feature (available on Professional and Enterprise tiers), we document the field mapping so the customer's admin can configure equivalent evaluation templates post-migration. Rating scale differences (eRecruiter's thumbs versus stars versus numeric) normalize to a numeric scale or picklist during the transform step.

Both Candidate and Application records support custom fields in eRecruiter. We discover the complete custom field schema during the scoping phase and map each field to an equivalent Zoho Recruit custom field. Zoho Standard edition limits custom fields to 50 per module; Professional and Enterprise allow 300 per module. We confirm the destination edition and alert the customer if their custom field count exceeds the edition limit, so they can upgrade or consolidate fields before migration.

eRecruiter's native RODO compliance features — consent flags, data retention metadata, and candidate rights records — do not have direct Zoho Recruit equivalents. We migrate consent status as custom candidate fields (consent_given__c, consent_date__c, consent_source__c) and flag the full consent record set in the delivery report. The customer implements a re-consent workflow in Zoho Recruit post-migration to ensure GDPR/RODO compliance is maintained in the new platform, particularly for candidates in Poland and other EU jurisdictions.