Migrate from Mercu to Zoho Recruit

Mercu employee records map to Zoho Recruit Candidates with the employee name split into First Name and Last Name. For Indonesian names that lack a clear first/last distinction, we use the primary name field as Last Name and place the full display name in a custom field. Employment status, academic rank, and tenure type migrate as custom fields on the Candidate record. The Candidate Status field in Zoho Recruit reflects the employee's current employment standing at migration time.

Mercu department affiliations migrate to Zoho Recruit's native Departments module. Each Mercu faculty or administrative unit becomes a Zoho Recruit Department record. The Candidate record in Zoho Recruit then references the department via a lookup field. For Mercu records that include secondary department assignments (joint appointments), we store the secondary affiliation in a custom Candidate field. Department hierarchy depth in Mercu maps to the Zoho Recruit Departments parent-child structure.

Historical job requisitions from Mercu migrate as Zoho Recruit Job Opening records. The job title, department assignment, hiring manager, and requisition status map to the corresponding Zoho Recruit fields. Candidates associated with a specific requisition in Mercu link to the migrated Job Opening via the Applications module. Job Opening capacity (number of open slots) and employment type (full-time, part-time, adjunct) migrate as custom fields on the Job Opening record.

Mercu employment status values (active, on leave, suspended, terminated) have no direct Zoho Recruit standard field equivalent because Zoho Recruit tracks hiring status rather than employment lifecycle. We create a custom Candidate field of type picklist with the original Mercu status values preserved. For active candidates, we set the Zoho Recruit Candidate Status to reflect their recruiting stage.

Mercu employment contract documents (PDFs, scanned agreements) attach to the corresponding Zoho Recruit Candidate record via the Document Library attachment feature. We extract contract metadata (contract type, start date, end date, renewal clause) into custom Candidate fields. Contract documents migrate as individual file attachments rather than embedded records, maintaining the document's integrity and accessibility within the Candidate profile.

Mercu leave balance records have no native Zoho Recruit equivalent since Zoho Recruit is an ATS and does not include leave management. We create a set of numeric custom fields on the Candidate record to capture annual leave balance, sick leave balance, and any accrued carry-over. Leave transaction history (individual leave entries) does not migrate as a related list; we store the current balance snapshot only. The customer's HR admin can set up Zoho Recruit's workflow rules for leave request tracking post-migration if required.

Mercu payroll data (salary grade, step, deductions, bank account) migrates to custom fields on the Zoho Recruit Candidate record. These fields are informational within the Candidate profile and do not trigger any Zoho Recruit payroll processing since Zoho Recruit does not support payroll management natively. The customer should confirm whether payroll data is intended for recruiting reference or should remain in a separate payroll system.

Academic credentials from Mercu (degree, institution, graduation year, field of study) migrate to custom fields on the Zoho Recruit Candidate record. Official credential documents (diplomas, transcripts) attach as files to the Candidate. This ensures that while Zoho Recruit's native qualification fields cover basic education, the full academic credential history from Mercu is preserved and accessible to hiring committees.

Professional certifications, faculty development training, and continuing education records from Mercu migrate as custom fields on the Candidate record, with supporting documentation attached via Zoho Recruit's file attachment feature. Expiration dates for time-bound certifications are stored in date-type custom fields to support future expiration alerts via Zoho Recruit workflow rules.

Mercu attendance summaries (days worked, absence count, late arrivals) migrate as read-only custom fields on the Candidate record. Individual punch-in/punch-out records do not migrate since Zoho Recruit does not have a native time-tracking module and the volume of daily attendance records would exceed practical limits for candidate profile storage. The customer's IT team decides whether attendance data is relevant for the hiring decision and whether to include it in scope.

Mercu user accounts for active staff members who will act as recruiters or hiring managers in Zoho Recruit map to Zoho Recruit User records. We resolve by email address match against the destination Zoho Recruit User table. Any Mercu user without a matching Zoho Recruit User record goes to a reconciliation queue for the customer's admin to provision before record import continues. Inactive Mercu accounts do not migrate as Users but the employee records do migrate as Candidates.

Mercu records that track hiring committee membership for a given requisition migrate as related records linked to the corresponding Job Opening in Zoho Recruit. We resolve committee members by email against Zoho Recruit Users and store the committee role (chair, member, observer) in a custom field. Interviewer assignments and evaluation rights in Zoho Recruit are configured as a separate step by the customer's admin post-migration.