Migrate from unstop to Zoho Recruit

Unstop User records for candidates map to Zoho Recruit Candidate. We extract first name, last name, email, phone, education history, skills, and work history from the CSV export. Zoho Recruit requires Last Name as a mandatory field; unstop records with no last name (a common self-registration artifact) receive a Last Name value of 'Not Provided' per Zoho's own migration documentation, which we apply before import. Email address becomes the primary dedupe key across all modules.

Unstop Organization records for recruiter companies map to Zoho Recruit Client. Organization name, description, logo URL, and contact details migrate to the Client module. Client records are created first so that any candidate records referencing an Organization can resolve the ClientId lookup at import time.

Unstop Job Posting records (title, description, location, salary range, employment type, application deadline) migrate 1:1 to Zoho Recruit Job Opening. The application status history (Applied, Shortlisted, Rejected, Offered) migrates to Candidate sub-records linked to the Job Opening with a custom field for original_status preserved for audit.

Unstop Internship records share the same schema as Job Postings with additional internship-specific fields: duration, stipend amount, stipend currency, and internship type (remote, in-office, hybrid). We carry these as custom fields on the Zoho Recruit Job Opening record and set the job type discriminator to Internship so that the Zoho Recruit job board filter correctly categorizes them.

Unstop application records linking a User to a Job Posting with application status and timestamp migrate as Zoho Recruit candidate records linked to the corresponding Job Opening via the Candidates sub tab. The application date, source channel, and original status flags carry forward in custom fields. If the candidate already exists in Zoho Recruit from a prior sourcing event, we merge rather than duplicate using email as the match key.

Internship applications follow the same mapping as job applications but link to the internship-type Job Opening. We also carry forward the candidate's stated internship preferences (start date, duration willingness, location preference) as custom fields on the candidate record. Applications without a matching candidate record in the destination go to a reconciliation queue for resolution before final import.

Unstop Quiz Session records (quiz ID, attempt timestamp, score, passing status, time taken, device/platform) migrate as custom fields on the Zoho Recruit Candidate record: unstop_quiz_score__c, unstop_quiz_passed__c, unstop_quiz_date__c, unstop_quiz_duration__c, and unstop_quiz_platform__c. Quiz configuration (question bank, time limit, rubric) from the Unstop Assessment object migrates as a structured JSON payload in a long-text field unstop_quiz_config__c on the Candidate record. Records with missing end_timestamp are flagged for manual review before import as these indicate crash-affected sessions.

Unstop Hackathon records (name, organizer, dates, rules, team structures, submission URLs, judging scores, leaderboard position) require a custom Hackathon Engagement module in Zoho Recruit. We create the module via Zoho Recruit's Custom Module builder before migration, defining fields for hackathon_name, organizer, start_date, end_date, team_size, submission_url, judging_score, and leaderboard_rank. Individual participation records link to the Hackathon Engagement parent record via a lookup.

Unstop hackathon team memberships are flattened into individual participation records within the Hackathon Engagement custom module. Each team member receives a separate record linked to the parent Hackathon Engagement, capturing their role on the team (member, team lead), their individual contribution URL, and their judging sub-score if scored individually. This avoids the team-as-a-single-record problem where one person's participation would be lost if the team record were treated as atomic.

Unstop Competition records (name, format type, organizer, dates, rules, participant list, scores) migrate to a Competition Engagement custom module. Because Unstop supports multiple competition formats (coding challenges, quizzes, design contests, case studies) each with different metadata, we use a format_type discriminator field and store format-specific fields as structured JSON in a long-text field competition_config__c. Participant enrollment lists link individual participation records to the Competition Engagement parent.

Unstop Scholarship records (name, eligibility criteria, amount, deadline, application list) migrate to a custom Program module in Zoho Recruit. The module captures scholarship_name, eligibility_summary, grant_amount, application_deadline, and application_status. Applicant records link to the Program via a lookup, preserving the candidate's scholarship application date and status (Applied, Under Review, Awarded, Rejected). Custom lookup fields are created before migration to ensure referential integrity.

Unstop Assessment objects storing quiz configurations, question bank references, time limits, and scoring rubrics do not map to a native Zoho Recruit object. We export the configuration as a structured JSON payload and attach it as a long-text custom field unstop_quiz_config__c on the Candidate record. This preserves the full assessment metadata for audit purposes without requiring a separate custom object. Format-specific configuration for hackathons and competitions follows the same JSON payload pattern in their respective custom module records.