HRMS migration

Migrate from Applicant Starter to Zoho Recruit

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 logo

Applicant Starter

Source

Zoho Recruit

Destination

Zoho Recruit logo

Compatibility

92%

11 of 12

objects map 1:1 between Applicant Starter and Zoho Recruit.

Complexity

BStandard

Timeline

2-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Applicant Starter logo

Applicant Starter

What's pushing teams away

  • Teams outgrow the platform when hiring volume increases beyond what the UI can manage efficiently, citing lack of advanced analytics and reporting.
  • Customers report limited customization options for pipeline stages and candidate evaluation workflows, pushing them toward platforms like Workday or Greenhouse.
  • Integration options beyond job boards are sparse, and teams needing HRIS sync or advanced CRM features find the ecosystem insufficient.

Choosing

Zoho Recruit logo

Zoho Recruit

What's pulling them in

  • Lowest cost entry point of any major ATS — a free tier with Candidates, Clients, Contacts, Interviews, and a career site lets small teams validate before committing to a paid plan.
  • Deep Zoho ecosystem integration — if the team already uses Zoho CRM, Sheets, or Analytics, candidate data flows between modules without re-keying or third-party middleware.
  • Customizable pipelines and stages — both agency and corporate editions let users define custom pipeline stages and assign candidates through drag-and-drop visual boards.
  • AI-assisted features via Zia — resume parsing, candidate summarization, and job-candidate matching are built in on paid tiers, reducing manual screening time.
  • Job board aggregation at no extra cost — paid tiers include postings to major job boards, extending reach without purchasing separate job ad bundles.

Object mapping

How Applicant Starter objects map to Zoho Recruit

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

maps to

Zoho Recruit

Candidate

1:1
Fully supported

Applicant 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

maps to

Zoho Recruit

Job Opening

1:1
Fully supported

Applicant 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

maps to

Zoho Recruit

Pipeline Stage

lossy
Fully supported

Applicant 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)

maps to

Zoho Recruit

Custom Field (Candidate module)

1:1
Fully supported

Applicant 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)

maps to

Zoho Recruit

Custom Field (Job Opening module)

1:1
Fully supported

Applicant 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

maps to

Zoho Recruit

Task

1:1
Fully supported

Applicant 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

maps to

Zoho Recruit

Task (Call subtype)

1:1
Fully supported

Applicant 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

maps to

Zoho Recruit

Event

1:1
Fully supported

Applicant 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

maps to

Zoho Recruit

Notes

1:1
Fully supported

Applicant 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

maps to

Zoho Recruit

Task

1:1
Fully supported

Applicant 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)

maps to

Zoho Recruit

Tag

1:1
Fully supported

Applicant 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

maps to

Zoho Recruit

Job Opening Source

1:1
Fully supported

Applicant 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.

Gotchas + challenges

What specifically takes care here

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 logo

Applicant Starter gotchas

High

No public API documentation or developer portal

Medium

Export requires a paid plan

Medium

No native bulk export endpoint

Low

Stage and tag schema varies per account

Zoho Recruit logo

Zoho Recruit gotchas

High

Daily API rate limits are tier-gated and per-user capped

High

User import hard cap of 2,000 records

Medium

Attachment folder hierarchy must be preserved exactly

Medium

Resume parsing quota varies by plan and resets daily

Low

Custom fields unavailable in Free and Standard editions

Pair-specific challenges

  • Applicant Starter export access requires a paid plan

    Applicant Starter gates API export behind paid tiers only. Free or trial accounts have read-only UI access with no programmatic export capability. During scoping we verify API access by testing a read call against the Candidates endpoint. If authentication fails or returns permission errors, we flag the account as export-ineligible and discuss alternatives such as manual CSV extraction from the UI. Migration timing depends on API availability and consistency; we maintain a monitoring hook that alerts us when export requests return unexpected responses.

  • Zoho Recruit credit limits cap bulk API throughput

    Zoho Recruit's API uses a credit-based system tied to edition: Free 500 credits/day, Standard 3,000-5,000/day, Professional 5,000-10,000/day, Enterprise 10,000-30,000/day. Insert and Update calls cost 1 credit per 10 records. During scoping we assess the destination account's credit allowance and migration volume to determine whether we use the Zoho API or fall back to the CSV import wizard. If credits are insufficient for the migration window, we spread the import across multiple days or use the CSV bulk import path to avoid throttling.

  • Last Name is mandatory in Zoho Recruit Candidate records

    Zoho Recruit enforces Last Name as a required field on Candidate records. Applicant Starter does not enforce this, so some candidate records may have no Last Name value. During pre-processing we identify all records missing Last Name and substitute 'Not provided' or the first name as a placeholder before import. The substitution is documented in the delivery report so the customer's admin can clean up display names post-migration. Records without any name data at all are flagged in the reconciliation report for manual handling.

  • Stage schema varies per Applicant Starter account

    Applicant Starter allows fully custom stage names and does not enforce a fixed taxonomy. One account may use Applied/Screening/Interview while another uses Open/Qualified/Closed. We extract the full stage schema during discovery, create matching stages in Zoho Recruit before candidate import, and flag any stages with no clear destination equivalent. Stage probability percentages are set to defaults pending the customer's Zoho stage probability configuration.

  • No bulk export endpoint in Applicant Starter requires iterative pagination

    Applicant Starter's API paginates results and requires iterating through pages to retrieve all records. Large candidate databases require sequential API calls that consume time and increase the risk of hitting rate-limit responses. We handle pagination automatically, throttle requests to avoid triggering limits, and resume from the last successful page if a rate-limit response interrupts the export. Customers with thousands of records should plan for a longer migration window. Resume and attachment downloads are processed as a separate batch after the main candidate record export completes.

Migration approach

Six steps for a successful Applicant Starter to Zoho Recruit data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Applicant Starter logo

Applicant Starter

Source

Strengths

  • Low-cost entry point for small teams starting to formalize their hiring process
  • Clean, straightforward UI that requires minimal training
  • Built-in job board integrations covering major platforms like Indeed and LinkedIn
  • Automated candidate communication features including email templates and status notifications

Weaknesses

  • Limited API documentation and no public developer portal
  • No bulk export endpoint requires iterative API pagination
  • Export access gated behind paid tiers only
  • Custom pipeline stage schema varies per account, requiring custom mapping work
Zoho Recruit logo

Zoho Recruit

Destination

Strengths

  • Free tier includes full candidate management with a hosted career site, making it viable for very small staffing operations.
  • Multi-edition architecture splits agency and corporate HR workflows, with tier-gated features that scale predictably with headcount.
  • Per-user API rate limits (500–1000/day) are generous for mid-size migrations compared to competitors that gate by total org quota.
  • Zoho's own data migration tool supports CSV import from Bullhorn, CATS, Jobdiva, and Workable, validating interoperability with common ATS formats.
  • 45-day money-back guarantee and 15-day full-feature trial reduce financial risk for teams evaluating the platform.

Weaknesses

  • Free edition excludes custom fields, lookup relationships, and formula fields, making data model extensibility unavailable until a paid tier is purchased.
  • Resume parsing quotas are capped: 250/day on Standard, 500/day on Professional, unlimited only on Enterprise — bulk imports of large candidate pools will hit these limits.
  • No bulk/batch API endpoint for inserts or updates — large migrations rely on looping single-record API calls within daily rate limit windows.
  • Custom modules cannot be imported from external ATS; only standard modules (Users, Candidates, Clients, etc.) are in the supported migration list.
  • Attachments require a rigid folder hierarchy to re-associate with records, and any deviation in folder structure during extraction causes silent disassociation.

Complexity grading

How hard is this migration?

Standard HRMS migration. 1 of 7 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Applicant Starter and Zoho Recruit.

  • Object compatibility

    B

    1 of 7 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    7-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Applicant Starter: Not publicly documented.

  • Data volume sensitivity

    B

    Applicant Starter doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Applicant Starter to Zoho Recruit migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Applicant Starter to Zoho Recruit data migrations

Answers to the questions buyers ask most during Applicant Starter to Zoho Recruit migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between two and three weeks for accounts with fewer than 2,000 candidates, 50 job requisitions, and no complex custom field dependencies. Migrations with larger candidate databases (over 10,000 records), extensive per-account stage schema differences, or pre-existing Zoho data that requires deduplication move to five to eight weeks. The Applicant Starter export phase duration depends on record volume and whether API access is available; iterative pagination for large databases adds time to the export window.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Applicant Starter.
Land in Zoho Recruit, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day