HRMS migration
Field-level mapping, validation, and rollback between Applicant Starter and Zoho Recruit. We move data and schema; workflows are rebuilt natively in Zoho Recruit.
Applicant Starter
Source
Zoho Recruit
Destination
Compatibility
11 of 12
objects map 1:1 between Applicant Starter and Zoho Recruit.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from Applicant Starter to Zoho Recruit is a structural migration that goes beyond a simple record copy. Applicant Starter stores candidates, jobs, and activities with account-specific pipeline stage names and no public API documentation, while Zoho Recruit enforces a typed schema with mandatory Last Name fields, a per-edition credit-based API, and a CSV-driven migration tool that requires precise field mapping. We reverse-engineer Applicant Starter's export endpoints during scoping, extract the full custom field and stage schema, and build a per-account mapping that handles the stage name differences and custom field gaps before loading into Zoho. Workflows, automations, and scorecards do not migrate; we deliver a written inventory of these for the customer's admin to rebuild in Zoho's Workflow Rules and Blueprint tools.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Applicant Starter object lands in Zoho Recruit, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Applicant Starter
Candidate
Zoho Recruit
Candidate
1:1Applicant Starter Candidate records map directly to Zoho Recruit Candidate. The full profile (name, email, phone, resume, current stage) migrates. Last Name is mandatory in Zoho Recruit; we pre-process candidates without a Last Name and substitute 'Not provided' or the first name as a placeholder before import. Resume files download as binary blobs, are renamed consistently (CandidateID_resume.pdf), and are attached to the corresponding Zoho Candidate record via the Attachments module.
Applicant Starter
Job Requisition
Zoho Recruit
Job Opening
1:1Applicant Starter job postings map to Zoho Recruit Job Opening records. We preserve the original job ID as a reference field in Zoho, map job title, department, hiring manager, job description, and status (Open/Closed). The original posting date and close date transfer as custom date fields if the customer requires historical job timing preserved. Active and closed positions migrate on a best-effort basis depending on Applicant Starter plan tier.
Applicant Starter
Pipeline Stage
Zoho Recruit
Pipeline Stage
lossyApplicant Starter's account-specific stage names (Applied/Screening/Interview or Open/Qualified/Closed, or any custom set) are extracted during scoping. We create matching Pipeline Stages in Zoho Recruit before candidate import so that the stage assignment resolves correctly at insert time. Stages with no Zoho equivalent are flagged for the customer to confirm before migration proceeds.
Applicant Starter
Custom Field (Candidate-level)
Zoho Recruit
Custom Field (Candidate module)
1:1Applicant Starter custom fields on candidates require explicit mapping. We extract the full field schema during discovery, identify Zoho equivalents, and create new custom fields in Zoho Recruit under the Candidate module up to the plan limit (50 on Standard, 300 on Professional/Enterprise). Fields with no Zoho match are flagged as unmapped and documented for manual post-migration entry.
Applicant Starter
Custom Field (Job-level)
Zoho Recruit
Custom Field (Job Opening module)
1:1Applicant Starter custom fields on job requisitions map to Zoho Recruit custom fields on the Job Opening module. Same schema extraction and creation process applies. The job-level custom field mapping is completed before job opening import so that field references resolve at insert.
Applicant Starter
Activity: Email
Zoho Recruit
Task
1:1Applicant Starter email activity logs migrate to Zoho Recruit Task records linked to the corresponding Candidate. We set Task Subject from the email subject line, Task Status to Completed, and attach the email body as the Task description. Activity timestamps are preserved as ActivityDate where available; older activities with missing timestamps are flagged and imported with a default timestamp pending customer review.
Applicant Starter
Activity: Call
Zoho Recruit
Task (Call subtype)
1:1Applicant Starter call logs migrate to Zoho Recruit Task records with Call type designation. Call duration, disposition, and any notes transfer to custom Task fields. We resolve the parent Candidate record by Applicant Starter candidate ID stored in a reference field during import.
Applicant Starter
Activity: Meeting/Interview
Zoho Recruit
Event
1:1Applicant Starter meeting and interview activity logs migrate to Zoho Recruit Event records. Start time, end time, location, and attendee information transfer. We link Event records to the corresponding Candidate via the Candidates module lookup. Interview feedback forms in Zoho Recruit (Professional/Enterprise) are created separately post-migration as no equivalent form structure exists in Applicant Starter.
Applicant Starter
Activity: Note
Zoho Recruit
Notes
1:1Applicant Starter notes attached to candidates migrate to Zoho Recruit Notes attached to the corresponding Candidate record. Note body and creation timestamp transfer. We flag any notes exceeding Zoho's character limit and split them across multiple Note records with sequence numbering.
Applicant Starter
Activity: Task
Zoho Recruit
Task
1:1Applicant Starter task records migrate to Zoho Recruit Task records. Task subject, description, due date, and completion status transfer. We resolve the assigned recruiter reference by matching Applicant Starter owner email to the corresponding Zoho Recruit user email.
Applicant Starter
Source/Tag (Candidate)
Zoho Recruit
Tag
1:1Applicant Starter candidate source tracking and tags migrate to Zoho Recruit Tags. Tags used for candidate classification are mapped directly where a matching Zoho Tag exists; new tags are created in Zoho before import to avoid tag-less records. Tags with no clear Zoho equivalent are documented for the customer's admin to assign post-migration.
Applicant Starter
Job Distribution Log
Zoho Recruit
Job Opening Source
1:1Applicant Starter tracks where each job was distributed (LinkedIn, Indeed, etc.). This data migrates to Zoho Recruit as source information on the Job Opening record. Distribution records that are inconsistently recorded in Applicant Starter are flagged; we migrate available distribution data and note gaps in the delivery report.
| Applicant Starter | Zoho Recruit | Compatibility | |
|---|---|---|---|
| Candidate | Candidate1:1 | Fully supported | |
| Job Requisition | Job Opening1:1 | Fully supported | |
| Pipeline Stage | Pipeline Stagelossy | Fully supported | |
| Custom Field (Candidate-level) | Custom Field (Candidate module)1:1 | Fully supported | |
| Custom Field (Job-level) | Custom Field (Job Opening module)1:1 | Fully supported | |
| Activity: Email | Task1:1 | Fully supported | |
| Activity: Call | Task (Call subtype)1:1 | Fully supported | |
| Activity: Meeting/Interview | Event1:1 | Fully supported | |
| Activity: Note | Notes1:1 | Fully supported | |
| Activity: Task | Task1:1 | Fully supported | |
| Source/Tag (Candidate) | Tag1:1 | Fully supported | |
| Job Distribution Log | Job Opening Source1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Applicant Starter gotchas
No public API documentation or developer portal
Export requires a paid plan
No native bulk export endpoint
Stage and tag schema varies per account
Zoho Recruit gotchas
Daily API rate limits are tier-gated and per-user capped
User import hard cap of 2,000 records
Attachment folder hierarchy must be preserved exactly
Resume parsing quota varies by plan and resets daily
Custom fields unavailable in Free and Standard editions
Pair-specific challenges
Migration approach
Discovery and API access verification
We audit the source Applicant Starter account across plan tier, custom field schema, stage definitions, candidate volume, job requisition count, and activity log volume. We verify API access by testing a read call against the Candidates endpoint. If API access is unavailable (free or trial plan), we flag the account as export-ineligible and discuss manual CSV extraction. We also assess the destination Zoho Recruit edition for API credit limits, custom field quota (50 or 300 per module), and any pre-existing data that could conflict with the import. The discovery output is a written migration scope with object inventory, field map draft, and a Zoho Recruit edition recommendation.
Schema buildout in Zoho Recruit
We create the destination schema in Zoho Recruit before any data moves. This includes creating custom fields in the Candidate and Job Opening modules (up to plan limits), configuring pipeline stages to match the Applicant Starter stage schema, creating tags that map to Applicant Starter source tags, and setting up any required picklist values. We work in a Zoho Recruit sandbox or the production account with a dedicated migration user if sandbox is unavailable. The schema build is validated by running a single-record import test for both a Candidate and a Job Opening before the full migration batch.
Pre-processing and mandatory field handling
We pre-process the Applicant Starter export data to handle mismatches before import. This includes substituting 'Not provided' for any candidate records missing Last Name, mapping per-account stage names to the newly created Zoho stage values, resolving Applicant Starter owner email references to Zoho Recruit user email addresses, and splitting long note bodies across multiple Zoho Note records. Pre-processing generates a data quality report identifying records with missing critical fields, duplicate candidates by email, and any records requiring manual review before import.
Export from Applicant Starter
We export candidate records, job requisitions, and activity history from Applicant Starter using the API with iterative pagination. Resume and attachment files download as binary blobs and are processed in a separate batch after the main record export. We throttle export requests to avoid rate-limit triggers and resume from the last successful page if a request fails. For accounts without API access, we guide the customer through the manual CSV export from the UI and validate the file structure before proceeding to import.
Bulk import into Zoho Recruit
We import records into Zoho Recruit in dependency order: Job Openings first (no dependencies), then Candidates (with stage and tag assignments resolved), then Activity history (Tasks, Events, Notes) linked to the corresponding Candidates by ID. We use the Zoho Recruit CSV import wizard for standard modules and the REST API for records requiring real-time lookup resolution. Each import phase emits a row-count reconciliation report comparing records in to records created, and we investigate any gap before proceeding to the next phase. Resume and attachment files are uploaded and linked to the corresponding Candidate record after the main candidate batch completes.
Cutover, validation, and handoff
We run a final delta migration of any records created or modified during the migration window after initial import. We validate a random sample of 25-50 candidate records against the Applicant Starter source, checking name, email, stage, and attachment presence. We deliver the migration reconciliation report showing record counts per object, any unmapped fields, and any records skipped due to missing mandatory data. We provide a written inventory of Applicant Starter workflows and automations for the customer's admin to rebuild using Zoho Recruit Workflow Rules and Blueprint tools. We do not provide post-migration admin support, training, or workflow rebuild as standard scope; these are separate engagements.
Platform deep dives
Applicant Starter
Source
Strengths
Weaknesses
Zoho Recruit
Destination
Strengths
Weaknesses
Complexity grading
Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Applicant Starter and Zoho Recruit.
Object compatibility
1 of 7 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
Applicant Starter: Not publicly documented.
Data volume sensitivity
Applicant Starter doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Applicant Starter to Zoho Recruit migration scoping. Not seeing yours? Book a call.
Walk through your Applicant Starter to Zoho Recruit migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Applicant Starter
Other ways to arrive at Zoho Recruit
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.