Migrate from LogicMelon to Zoho Recruit

LogicMelon Job records map directly to Zoho Recruit Job Openings. The job description, requirements, salary fields, and location migrate to their equivalent Zoho Recruit Job Opening fields. Each LogicMelon job carries its own list of targeted job boards; we preserve this list as a tag on the Zoho Recruit Job Opening (using Zoho's Tag feature) so the team can see which boards originally received each advert. The multi-post action itself is not replicated in Zoho Recruit because it uses direct board integrations rather than a relay aggregator model.

LogicMelon Application records combine candidate profile data with job-specific status and submission context. We split each Application into a Zoho Recruit Candidate record (contact details, work history, skills from LogicMelon's structured fields) and a submission association linking that Candidate to the migrated Job Opening. The original LogicMelon application date and status transitions are preserved as a history log on the Zoho Recruit Candidate record. If a LogicMelon candidate has applied to multiple jobs, each application generates a separate submission in Zoho Recruit against the corresponding Job Opening.

LogicMelon Candidate profiles map to Zoho Recruit Candidate records. We migrate structured profile fields (name, email, phone, current employer, skills, experience) directly. Status history and skills list migrate as custom fields or picklist values in Zoho Recruit depending on field availability. Candidates with no last name in LogicMelon are populated with 'not provided' per Zoho Recruit's mandatory field requirement to prevent records from being skipped during import.

LogicMelon stores CV documents as binary file attachments (typically PDF or Word format) linked to Candidate records. We extract the raw file from LogicMelon's file store and attach it to the corresponding Candidate record in Zoho Recruit. Any structured candidate data already captured in LogicMelon's profile fields migrates directly; the CV file serves as the source-of-truth backup where structured fields are incomplete. Zoho Recruit's resume parsing populates structured fields automatically for records where the CV is attached, providing a secondary data-enrichment step after migration.

Recruiter screening notes and evaluation scores attached to LogicMelon Applications migrate as Comments on the Zoho Recruit Candidate record, preserving the note content and the authoring recruiter reference. Where LogicMelon stores structured scoring (screening grades, rating values), these map to custom fields on the Candidate module. We identify all active screening note fields during discovery and configure the equivalent custom fields in Zoho Recruit before migration.

LogicMelon's configurable pipeline stages (for example: Applied, Screened, Interviewed, Shortlisted, Offered) are mapped to Zoho Recruit's Candidate Status values. During scoping we capture the customer's exact stage names and sequence from LogicMelon and configure Zoho Recruit's status picklist to match. Stage probability percentages where they exist in LogicMelon migrate as custom fields. If Zoho Recruit's default status values differ from LogicMelon's vocabulary, we update the picklist before migration.

LogicMelon Users (recruiters and administrators) are tied to the organisation hierarchy via API credentials and referenced on Jobs and Applications as owners. We extract every distinct user assignment and attempt to match by email address against Zoho Recruit User records. Any User without a matching Zoho Recruit account is flagged in a reconciliation queue; Zoho Recruit requires that existing users close any separate Zoho Recruit account before being imported into the company's Recruit account. Recruiter assignments on Jobs and Applications migrate as the Owner field once User reconciliation is complete.

LogicMelon's multi-tenant organisation hierarchy (agency-level versus client-level sub-units) maps to Zoho Recruit's Clients module or the Department structure depending on the customer's Zoho Recruit edition. Agency-level organisations in LogicMelon map to Zoho Recruit Clients; sub-unit structures within the agency map to Zoho Recruit Departments. We extract the full organisation hierarchy during discovery and present a mapping recommendation based on the customer's intended Zoho Recruit data model.

The list of job boards targeted per LogicMelon job advert is stored as a board-association object per job rather than globally. We preserve the complete board list as Zoho Recruit Tags on the Job Opening (one tag per board name). This gives the team visibility into the original posting distribution without attempting to replicate the multi-post action itself. Tags are accessible from Zoho Recruit's Tag management interface and can be used for filtering and reporting.

LogicMelon allows custom fields on Job records. We identify all active custom fields during discovery, determine their data types (text, picklist, date, number), and recreate equivalent custom fields in Zoho Recruit's Job Opening module. Custom field limits apply per Zoho Recruit plan: 50 per module on Standard, 300 per module on Professional and Enterprise. We flag any customer whose LogicMelon custom field count exceeds the target plan limit during scoping so the plan upgrade decision is made before migration.

LogicMelon Application-level custom fields migrate to Zoho Recruit Candidate custom fields, preserving the field type mapping (text to text, picklist to picklist, date to date). The same plan-tier custom field limits apply. Custom fields with complex data types or multi-select behaviour require additional mapping configuration during the transform phase.

File attachments beyond CVs — such as supporting documents attached to LogicMelon Jobs or Applications (offer letters, client briefs, test results) — are extracted from LogicMelon's file store and reattached to the corresponding record in Zoho Recruit. Attachment type determines destination: a document attached to a Job becomes a Zoho Recruit Job Opening Attachment; a document attached to an Application becomes a Candidate Attachment. File size limits per Zoho Recruit's storage policy are verified during scoping.

Active placements or offer records in LogicMelon migrate as Comments on the Candidate record with the offer details captured in structured custom fields (offer amount, start date, offer status). If the customer uses Zoho Recruit's Offer Letter module, placements map to Offer records linked to the Candidate. We identify offer-related data in LogicMelon during discovery and configure the appropriate target schema before migration.

LogicMelon talent pools and candidate shortlists (groupings of candidates not tied to a specific active job) migrate as Zoho Recruit Tags on the Candidate records. We extract pool names and membership during discovery, create matching Tags in Zoho Recruit, and associate each Candidate to the appropriate tags. An alternative approach using Zoho Recruit Custom Views for pool representation is presented during scoping based on the customer's reporting needs.

Activity notes, call summaries, and internal communications logged against LogicMelon Applications and Candidates migrate as Comments on the corresponding Zoho Recruit Candidate record. The comment author and timestamp are preserved where available from LogicMelon's structured activity data. Notes that include evaluation scores or screening outcomes are mapped to the screening custom fields identified in discovery.

Interview records from LogicMelon migrate to Zoho Recruit Interview records linked to the Candidate and the relevant Job Opening. Interview details (scheduled date, interviewer, location or meeting link, outcome, feedback) map to their equivalent Zoho Recruit Interview fields. Interview feedback forms in LogicMelon migrate as Comments or as custom fields on the Interview record depending on complexity.