Migrate from Longlist to Zoho Recruit

Longlist candidate records map directly to Zoho Recruit Candidates. The candidate's full name, email address, phone number, LinkedIn profile URL, and location fields transfer to their Zoho Recruit equivalents. Longlist's Last Name may be absent for records sourced with only a first name or company name; we populate the Zoho Recruit Last Name with a placeholder value ('Not Provided' or equivalent) per Zoho's import requirement and flag the record in a custom field original_name__c to preserve the original enrichment string.

Longlist's structured contact fields (email address, phone number, LinkedIn URL) map to Zoho Recruit's standard Candidate email and phone fields. LinkedIn URL does not have a native Zoho Recruit field at Standard tier; we create a custom field LinkedIn_URL__c of type URL and populate it during import. At Enterprise tier, customers can create a lookup field to a custom Social Profiles module.

Longlist lists (recruiter-applied groupings of candidates) map to Zoho Recruit Candidate Groups. Candidate Groups are a Zoho Recruit standard feature accessible from the Candidates module. We map each distinct Longlist list name to a Zoho Group, then assign candidate records to their respective group during import via the CandidateGroupCandidate related table.

Longlist tags applied during the enrichment phase map to a Zoho Recruit custom multi-select picklist field on the Candidate object (for example, sourcing_channel__c). We pre-create this field during migration setup with the tag values imported from Longlist. Tags that represent enrichment confidence or data source (for example, 'verified email', 'phone found') can be mapped to separate single-select or multi-select custom fields for filtering and reporting in Zoho Recruit.

Longlist records often carry source attribution indicating where the contact data was found (for example, LinkedIn Recruiter, company website, Boolean search). We preserve this attribution in Zoho Recruit's standard Source field and add a custom field sourcing_tool__c with Longlist recorded as the value so that reporting distinguishes enriched candidates from directly applied ones.

Longlist enrichment metadata such as data confidence scores, last enriched timestamp, and verification status do not have native Zoho Recruit equivalents. We create custom fields enrichment_confidence__c (number), last_enriched__c (date/time), and data_verified__c (checkbox) on the Candidate object and populate them during import. This preserves the enrichment provenance for teams that want to filter by data freshness in Zoho Recruit.

Longlist does not expose a formal user roster via its export, but tag and list assignments carry implicit owner attribution. We extract the email address associated with the Longlist session where tags were applied and match against Zoho Recruit User records by email. Users without a matching Zoho Recruit account are flagged in a reconciliation queue for the admin to provision before the candidate import phase begins.

Longlist does not have a job opening or requisition module. If the customer has a separate document (spreadsheet or job board export) that associates Longlist candidates with specific job reqs, we can create corresponding Zoho Recruit Job Opening records and link the migrated Candidates via the Job Openings lookup field. If no job association data exists, we import candidates into Zoho Recruit without a job opening link and rely on Candidate Groups and Tags for initial organization.

If Longlist exports include any free-text notes attached to candidate records, these map to Zoho Recruit Notes on the Candidate. Notes attach via the Zoho Recruit Notes sub-panel of the Candidate record. We preserve the note body, creation timestamp, and author if the author email is resolvable to a Zoho Recruit User.

Longlist does not natively store resume files, but if the customer exported resume attachments alongside candidate records, we attach these to the Zoho Recruit Candidate record via the Attachments sub-panel. Zoho Recruit Standard plan supports resume parsing at 250 resumes per day; Enterprise supports unlimited parsing. We map parsed resume fields to Candidate standard fields and raw attachments to the candidate record.

For customers with large-scale enrichment exports from Longlist (for example, CSV exports of thousands of sourced candidates), we can create a custom Zoho Recruit module (for example, Sourced_Candidates__c) to hold enrichment-specific fields that do not map to the standard Candidate object. This is available in Zoho Recruit Enterprise. Custom modules are configured before import and use the Zoho Recruit API for record insertion.

Longlist does not expose automation or sourcing workflow definitions as exportable objects. Any tagging logic, enrichment triggers, or list assignment rules configured in Longlist do not migrate as code. We deliver a written inventory of any identified enrichment logic (for example, auto-tagging rules based on data source) and recommend equivalent Zoho Recruit Blueprint or assignment rule configurations for the customer's admin to implement post-migration.