Migrate from Martian Logic to Zoho Recruit

Martian Logic ATS candidates map directly to Zoho Recruit Candidate records. We extract full candidate pipeline data including status history, application dates, resume files, and interview scores. The Martian Logic candidate_id becomes a custom field ml_candidate_id__c for audit traceability. Zoho Recruit requires a Last Name value on every Candidate import — where Martian Logic does not provide a separated last name field, we parse the name string and split on the first space, flagging any record that cannot be cleanly split for manual review before import.

Martian Logic Positions used in the recruitment workflow (open reqs with linked candidates) map to Zoho Recruit Job Opening records. Position title becomes Job Title, employment type from the Position configuration maps to Zoho Recruit's Job Type picklist, and the requesting manager from the Position's linked user maps to the Zoho Recruit Hiring Manager field. Closed or archived Positions in Martian Logic are imported as inactive Job Openings so the historical requisition record is preserved.

Martian Logic Users linked to recruitment activities (recruiters, hiring managers, approvers) map to Zoho Recruit Users. We resolve by email address. Any Martian Logic User without a matching Zoho Recruit User email is held in the reconciliation queue for the customer's admin to provision the account before candidate import begins. Zoho Recruit requires at least two Users to be present before the import wizard runs; we flag this during scoping if it is not met.

E-forms in Martian Logic are stored as a JSON payload within each employee's record, with field names and structure varying per onboarding pack configuration. There is no fixed schema. We parse each payload individually during the extraction phase, extract field-value pairs, and map them to Zoho Recruit Custom Fields on the Candidate object or a custom Onboarding Data module. The customer's admin approves the field mapping per pack. Fields that cannot map to typed Zoho Recruit fields (dates, picklists, numbers) are converted to Text or stored as JSON in a Long Text Area field.

Martian Logic Request-to-Recruit Workflows track the approval chain from manager submission through HR and executive sign-off. Zoho Recruit has no native equivalent to this HR-layer approval workflow. We document every active Requisition Workflow (trigger fields, approval stages, conditions) in a written handoff document. Job Opening status transitions in Zoho Recruit serve as the lightweight replacement for open-pending-approved requisition tracking, but the multi-stage approval chain must be rebuilt in Zoho Flow or handled manually.

Martian Logic's org chart is a derived view of the Position-to-Position reporting chain, not a standalone API object. We walk the position hierarchy during extraction and reconstruct it as a custom module in Zoho Recruit with a self-lookup Parent_Position__c field, or as a structured custom field chain (Level 1 Manager, Level 2 Manager) on the User object. Orphaned nodes (Positions with archived parents) are flagged for the customer's admin to resolve before import.

For migrations that include employees who were hired through Martian Logic's ATS (converted candidates), we map the Martian Logic Employee record to Zoho Recruit Candidate using the ml_candidate_id cross-reference. Personal details (name, email, phone, address) map to standard Zoho Recruit Candidate fields. Employee-specific fields without a Candidate equivalent (ESS access level, role permissions) are stored as custom fields or noted as requiring Zoho People for full HRMS coverage.

Martian Logic interview records (scheduled, completed, with scores and interviewer feedback) map to Zoho Recruit Interview records linked to the Candidate and Job Opening. Interviewer name resolves to a Zoho Recruit User by email lookup. Score cards and feedback notes migrate as Interview custom fields or notes attached to the Interview record.

Martian Logic Change of Staff Conditions records are effective-dated transactions recording old value, new value, change type, and reason per employee. We flatten these into a per-candidate change log stored as a custom Notes section or a multi-line custom text field on the Candidate record. Zoho Recruit has no native employment change log object. For customers who need full employment history tracking, we recommend Zoho People as a complementary HRMS and document the Employment Changes as a structured data table for import into Zoho People Employee records post-migration.

Martian Logic stores compensation in the Role and Remuneration Library linked to Positions. Pay structure data (base salary, allowances, pay frequency) has no native Zoho Recruit field. We map compensation to custom currency fields on the Job Opening (for position-level compensation ranges) or to Candidate custom fields (for candidate-specific compensation requirements or offers). Compliance with pay transparency requirements depends on the customer's use of these fields post-migration.

Martian Logic Compliance modules track regulatory attestations and expiry dates per employee. Zoho Recruit has no native compliance tracking. We export compliance status, certificate names, and expiry dates as custom fields on the Candidate or a separate Compliance module. Compliance enforcement and active monitoring remain outside Zoho Recruit's scope and should be handled in Zoho People or the customer's compliance management tool.

Martian Logic Integration Connectors push employee data to third-party payroll systems with field-to-field mappings stored as platform configuration. These connector field mappings do not export from Martian Logic. We document every active connector's source and destination fields during discovery, but the equivalent configuration must be rebuilt manually in the target payroll system post-migration. We do not migrate or re-create payroll integration configurations.