HRMS migration

Migrate from Loxo to Zoho Recruit

Field-level mapping, validation, and rollback between Loxo and Zoho Recruit. We move data and schema; workflows are rebuilt natively in Zoho Recruit.

Loxo logo

Loxo

Source

Zoho Recruit

Destination

Zoho Recruit logo

Compatibility

67%

8 of 12

objects map 1:1 between Loxo and Zoho Recruit.

Complexity

BStandard

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Loxo to Zoho Recruit is a cost-driven migration for agencies and in-house teams that have outgrown Loxo's per-seat pricing without needing its AI sourcing layer. Loxo's Basic tier runs $169 per user per month, while Zoho Recruit Standard starts at $12 per recruiter per month — a difference of roughly $157 per user monthly that compounds at scale. We handle the structural differences: Loxo's unified candidate-person model splits into Zoho Recruit's separate Candidate and Client objects depending on record type; Loxo's customizable Deal pipeline maps to Zoho Recruit's Opportunity pipeline with configurable stage names; and Loxo's duplicate candidate profiles (created when the same person applies to multiple jobs) are flagged and deduplicated before loading into Zoho Recruit so the destination database is clean from day one. Outreach sequences, campaign automation, and portal settings do not migrate via API; we preserve sequence enrollment status as Candidate custom properties and deliver a written inventory of automation logic requiring rebuild in Zoho Recruit Workflow Rules.

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

Loxo logo

Loxo

What's pushing teams away

  • Email and SMS automation failures cause recruiters to fall back to manual outreach, defeating the purpose of the platform and creating extra work during active searches.
  • The AI matching quality is inconsistent — users with niche skillset requirements report that Loxo Source produces outdated results that do not replace LinkedIn Recruiter.
  • Users on Capterra report being misled on sales calls about sourcing capabilities, with promised integrations absent after purchase, leading to non-renewal and billing disputes.
  • Multiple users report duplicate candidate profiles when the same person applies to different jobs, creating messy databases that require manual cleanup.
  • The deal pipeline board is difficult to use for managing business development workflows, pushing some users toward platforms purpose-built for CRM-style pipeline management.

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 Loxo objects map to Zoho Recruit

Each row shows how a Loxo 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.

Loxo

Candidate

maps to

Zoho Recruit

Candidate

1:1
Fully supported

Loxo Candidates map directly to Zoho Recruit Candidates. The primary record fields — name, email, phone, address, skills, experience, and source — transfer to the Zoho Recruit Candidate module. Multi-job duplicate profiles (same person applied to multiple Loxo Jobs) are flagged during extraction and resolved before load: we match by email address and present the deduplication choice (merge into one Zoho Candidate, or keep as separate records) to the customer during scoping. The most recent Loxo outreach sequence enrollment status and step number are stored as custom fields on the Zoho Candidate for the admin to reference during rebuild.

Loxo

Contact

maps to

Zoho Recruit

Candidate or Client

1:many
Fully supported

Loxo Contacts are split into Zoho Recruit Candidates (for talent-facing contacts) and Zoho Recruit Clients (for employer-facing contacts). We determine the split from the Loxo Contact's associated record type — if the Contact is linked to a Client Company in Loxo, it maps to a Zoho Client record; if linked to a Job or Placement, it maps to a Candidate. Any Loxo Contact without a clear association is held in a review queue during scoping for the customer to classify.

Loxo

Job

maps to

Zoho Recruit

Job Opening

1:1
Fully supported

Loxo Jobs (requisitions) map to Zoho Recruit Job Openings. The job title, description, requirements, status, assigned recruiter, and hiring manager transfer. Custom fields on the Loxo Job migrate as Zoho Recruit custom fields on the Job Opening module. Zoho Recruit's active job limits vary by tier (Free 1, Standard 100, Professional 250, Enterprise 750 per recruiter); we validate the count against the destination tier during scoping and flag any overage before migration.

Loxo

Client Company

maps to

Zoho Recruit

Client

1:1
Fully supported

Loxo Client Companies map to Zoho Recruit Client records, preserving the company name, address, billing contacts, and associated client-specific notes. Client Company hierarchy (parent and subsidiary relationships) maps to Zoho Recruit Client hierarchy if enabled on the destination tier. If Loxo client records contain no billing or account information (client-company records used primarily as address books), they migrate as Zoho Clients with minimal fields populated.

Loxo

Deal

maps to

Zoho Recruit

Opportunity

1:1
Fully supported

Loxo Deals map to Zoho Recruit Opportunities. The deal name, amount, currency, stage, expected close date, probability (derived from Loxo stage percentage), and assigned owner transfer. Loxo's customizable pipeline stages (unique per organization) map to Zoho Recruit Opportunity stages, and we validate stage count against Zoho Recruit's stage limit during scoping. Deals without an associated Client in Loxo are attached to the most recently associated Job Opening as the WhatId in Zoho.

Loxo

Placement

maps to

Zoho Recruit

Candidate (placement status field)

lossy
Fully supported

Loxo Placements record a placed candidate against a Job and Deal, including start date, compensation, and placement status. Zoho Recruit does not have a standalone Placement object; we represent Placements as Candidate records with a custom field set to placement status (Active, On Hold, Completed) and custom fields for start date, compensation, and the linked Opportunity. We preserve the placement-to-job and placement-to-deal relationships via lookup fields in Zoho Recruit custom fields.

Loxo

Custom Field

maps to

Zoho Recruit

Custom Field

lossy
Fully supported

Loxo custom fields on Candidates, Contacts, Jobs, and Deals map to Zoho Recruit custom fields on the corresponding modules. Zoho Recruit caps custom fields per module by tier (Standard 50/module, Professional and Enterprise 300/module). We audit the Loxo custom field schema during scoping, count fields per module, and flag any overage against the destination tier before schema deployment. Picklist options in Loxo map to Zoho Recruit picklist or multi-select picklist fields; free-text fields map to multi-line text fields.

Loxo

Activity: Email, Call, SMS, Note

maps to

Zoho Recruit

Tasks, Events, Calls

1:1
Fully supported

Loxo engagement history — emails, calls, SMS, and notes — maps to Zoho Recruit Tasks (generic activities), Events (calendar entries), and Calls (call log records). The most recent 12-24 months of activity is the recommended scope to reduce risk of misaligned email threads from Loxo Connect's inbox-sync behavior. Call duration, disposition, and recording URL transfer to Zoho Call record custom fields. Zoho Recruit Standard and above support Tasks, Events, and Call logging; the Free tier does not support Tasks or Events.

Loxo

Tag

maps to

Zoho Recruit

Tag

1:1
Fully supported

Loxo tags on Candidates, Contacts, Jobs, and Deals transfer to Zoho Recruit Tags. We extract every distinct tag value, create the corresponding tag in Zoho Recruit during migration, and apply tag associations to the migrated records. Tags used for candidate segmentation in Loxo map directly to Zoho Recruit Tags; tags used for workflow classification are preserved as tags and noted as candidates for Zoho Workflow Rule triggers post-migration.

Loxo

Attachment (Resume, Document)

maps to

Zoho Recruit

Document Library

1:1
Fully supported

Binary attachments — resumes, cover letters, client agreements — stored on Loxo Candidate, Contact, and Job records are extracted via the Loxo API file URL, downloaded, and re-uploaded to Zoho Recruit's Document Library with associations back to the parent record. Large attachment counts may require chunked download and upload with hash-verified integrity checks to confirm each file arrived intact.

Loxo

Owner

maps to

Zoho Recruit

User

1:1
Fully supported

Loxo Owner assignments on Candidates, Contacts, Jobs, Deals, and Placements map by email to Zoho Recruit User records. We extract every distinct owner email referenced across all record types, match against the Zoho Recruit User table, and flag any Loxo owner without a Zoho User match for the customer to provision before production migration. Active and inactive owner status is preserved in the migration mapping.

Loxo

Pipeline Stage

maps to

Zoho Recruit

Opportunity Stage

lossy
Fully supported

Loxo Pipeline Stages are organization-specific and stored per Deal record. We extract the complete stage list from the Loxo API, map each Loxo stage name to a Zoho Recruit Opportunity stage with a customer-confirmed probability percentage, and validate stage count against Zoho Recruit's pipeline stage limits. Stage order and probability mapping are applied during Deal-to-Opportunity migration.

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.

Loxo logo

Loxo gotchas

High

API returns 403 on trailing spaces in URL parameters

High

Outreach campaign automation not available via API

Medium

Duplicate candidate profiles for multi-job candidates

Medium

Loxo Connect email boundary risk

Low

Pricing discrepancy between published tiers and actual invoices

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

  • Duplicate candidate profiles do not auto-merge on migration

    Loxo creates a new Candidate profile every time the same person applies to a different Job, meaning one physical candidate can have three to ten Candidate IDs across the database. Zoho Recruit deduplicates Candidates by email address by default. We flag all multi-profile candidates during extraction, run a deduplication pass that groups records by email, present the options to the customer (merge into one Zoho Candidate record or preserve as separate), and apply the chosen strategy before any Candidate records are inserted. Skipping this step produces a Zoho Recruit database where one candidate appears as five separate records, requiring the same cleanup work post-migration that the source system required.

  • Loxo Outreach sequences have no API endpoint

    Loxo Outreach campaign configuration — email cadence steps, SMS triggers, auto follow-up timing, and sequence enrollment status — is not exposed through the public API. Active automation cannot be migrated directly as code. We capture the most recent outreach enrollment status (which sequence, which step, last contact date) as Candidate custom fields during extraction so the destination admin knows where each candidate sits in an outreach flow without needing to rebuild from memory. The campaign logic itself requires rebuild in Zoho Recruit Workflow Rules, and we deliver a written inventory of every active Loxo Outreach sequence with its cadence structure for that rebuild.

  • Loxo Connect email sync can misalign threads during extraction

    Loxo Connect syncs emails between a recruiter's personal inbox and candidate records. Emails sent from a personal address to a candidate's work email can end up in the wrong candidate record or unlinked in Loxo. We recommend scoping candidate communication history to the most recent 12-24 months to reduce the volume of fragmented threads, and we validate email-address ownership before mapping any Loxo Connect thread to a Zoho Recruit Contact or Candidate activity record. Older email threads are preserved as notes with a warning flag if they lack a verified email address match.

  • Zoho Recruit tier caps on active jobs and custom fields constrain migration scope

    Zoho Recruit's active job limits vary by tier (Standard 100 per recruiter, Professional 250, Enterprise 750) and custom field limits are 50 per module on Standard versus 300 on Professional and Enterprise. If the Loxo database contains more active Jobs than the destination tier allows, we flag the overage during scoping and recommend either a Professional tier upgrade or a job-archival strategy (closing completed Jobs before migration to bring active job count within the limit). Custom field count per module is similarly validated against the destination tier schema.

  • Zoho Recruit API does not expose client portal settings or assignment rules

    Zoho Recruit's client-facing portal configuration — branding, shared job visibility, candidate submission forms, and client report templates — is tied to instance-level portal settings not accessible via API. Assignment Rules (automatically assigning Candidates or Job Openings to recruiters) are configurable in Zoho Recruit but their import/export is not fully API-documented. We capture the current portal and assignment configuration as a written snapshot for the customer's admin to reconfigure in Zoho Recruit settings post-migration. This is a manual step, not a migration gap.

Migration approach

Six steps for a successful Loxo to Zoho Recruit data migration

  1. Discovery and tier mapping

    We audit the source Loxo account across tier (Free/Basic/Professional/Enterprise), custom field schemas per object, active Job count, Deal pipeline count and stage names, outreach sequence count, activity history date range, and attachment file count. We pair this with a Zoho Recruit tier assessment: Standard ($12/user/month) covers most migrations with up to 100 active jobs and 50 custom fields per module; Professional (approximately $20/user/month) is recommended if the migration requires more active job slots or higher custom field density; Enterprise handles large agencies with 750+ active job limits and unlimited resume parsing. The discovery output is a written migration scope with source record counts, destination tier recommendation, and deduplication strategy.

  2. Schema design and custom field provisioning

    We design the Zoho Recruit destination schema before any data moves. This includes creating custom fields on Candidate, Client, Job Opening, and Opportunity modules to match the Loxo custom field schema (type-mapped: picklist to picklist, text to multi-line text, number to number). We validate custom field count against the destination tier limit (50 on Standard, 300 on Professional/Enterprise), configure Zoho Recruit Opportunity stages to match Loxo pipeline stages with customer-confirmed probability mapping, and set up Candidate and Client modules with the custom fields required to carry Loxo outreach enrollment status. Schema is deployed into the destination Zoho Recruit account for validation before migration begins.

  3. Deduplication strategy and sample migration

    We run a deduplication pass across Loxo Candidate records grouped by email address. Each group of duplicate profiles is presented to the customer with the record set and metadata (most recent application date, last activity, associated Jobs and Deals). The customer chooses the merge strategy per group or applies a global rule (merge all duplicates by email). We then run a sample migration of 50-100 records — covering at least one candidate from each deduplication group, one Job, one Deal, one Client Company, and activity records — into the live Zoho Recruit account. The customer's admin spot-checks mapping accuracy, validates custom field population, and confirms deduplication results before the full migration is approved.

  4. Production migration in dependency order

    We run production migration in record-dependency order: Client Companies first (to satisfy any Account or Client lookup in Zoho), Job Openings next (to satisfy Job lookups on Candidates), then Candidates with deduplication applied and outreach status as custom fields, then Clients, then Opportunities (with stage and probability mapping resolved), then Activities (Tasks, Events, Calls via Zoho Recruit API with batch chunking), then Attachments via Document Library upload, then Tags applied last to preserve associations. Each phase emits a row-count reconciliation report showing source count, migrated count, and skipped count with reason codes before the next phase begins.

  5. Cutover and delta sync

    We freeze writes to the Loxo account during cutover — either a planned maintenance window or a weekend migration to minimize disruption. Any records modified in Loxo during the migration window are captured as a delta pass and inserted into Zoho Recruit before go-live. Tags are applied in a final pass after all record inserts are confirmed. We validate record counts against the Loxo source totals and flag any residual gaps for customer review.

  6. Validation, outreach inventory handoff, and portal rebuild support

    We validate migrated data against the Loxo source across a random sample of 50 records per object type, checking field-level accuracy, owner assignment, and activity completeness. We deliver the Outreach Sequence Inventory document listing every active Loxo Outreach sequence with its cadence structure, step count, and recommended Zoho Recruit Workflow Rule equivalent. We do not rebuild Loxo Outreach sequences as Zoho Workflow Rules inside the migration scope; that is a separate engagement or an internal admin task. Client portal settings are documented separately as a manual reconfiguration checklist. We support a one-week post-cutover window for reconciliation issues raised by the recruiting team.

Platform deep dives

Context on both ends of the pair

Loxo logo

Loxo

Source

Strengths

  • Bundles ATS and CRM into one platform, replacing multiple separate tools for candidate tracking and client management.
  • Loxo Source provides a searchable database of over 800 million professionals with verified contact information built into the candidate record.
  • AI-powered candidate matching and ranking learn from recruiter behavior over time, surfacing suggestions on subsequent searches.
  • Omni-channel outreach (email, SMS, LinkedIn) with automation and auto follow-ups consolidates engagement into a single workflow.
  • Free tier provides a full ATS and Recruiting CRM indefinitely, allowing teams to try the platform before committing.

Weaknesses

  • AI capabilities are layered on top of legacy architecture, limiting how deeply automation can handle high-volume workflows compared to newer AI-native platforms.
  • The API lacks publicly documented rate limits, making it difficult to plan bulk extraction without risking 403 responses during large migrations.
  • Campaign automation and outreach configuration are not fully exposed via the public API, preventing migration of active sequences.
  • The client portal is a secondary focus; client-side users report limited visibility into pipeline progress and prefer email updates from recruiters.
  • Duplicate candidate profiles are created when the same person applies to multiple jobs, requiring manual deduplication after migration.
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 Loxo 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

    Loxo: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Loxo 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 Loxo to Zoho Recruit data migrations

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

Can't find your answer?

Walk through your Loxo to Zoho Recruit migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Straightforward migrations under 10,000 Candidates, 2,000 Deals, and 1,000 active Jobs with clean deduplication land between two and four weeks. Migrations with significant duplicate candidate profiles (multi-job applications requiring deduplication pass), large engagement histories (over 200,000 activity records), or custom schemas approaching Zoho Recruit's per-tier field limits move to five to ten weeks. Timeline also depends on customer approval speed for the deduplication strategy and sample migration sign-off.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Loxo.
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