HRMS migration

Migrate from SumTotal to Zoho Recruit

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

SumTotal logo

SumTotal

Source

Zoho Recruit

Destination

Zoho Recruit logo

Compatibility

58%

7 of 12

objects map 1:1 between SumTotal and Zoho Recruit.

Complexity

BStandard

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from SumTotal to Zoho Recruit is a category-shift migration. SumTotal is an enterprise HRMS covering learning management, talent management, performance, and compliance training for organisations with 1,000+ employees. Zoho Recruit is an applicant tracking system designed for in-house HR teams and staffing agencies that need candidate sourcing, resume parsing, interview scheduling, and pipeline management. The two platforms share almost no overlapping object schemas: SumTotal's Learners, Courses, Curricula, Training Records, and Compliance Certifications have no direct Zoho Recruit equivalents. We scope the migration to the subset of SumTotal data that can be represented in Zoho Recruit — primarily Users (mapped to Candidates or Employees depending on use case), any open requisitions or job postings captured in SumTotal's talent acquisition module, and supporting documents and notes. We flag SumTotal's API rate ceiling (50,000 req/hour), the v1/v2 endpoint duality introduced by the Cornerstone OnDemand acquisition, and the enterprise-tier gating on talent management objects. We do not migrate SumTotal's Workflow automation rules, course content, curricula assignments, compliance certification expiry logic, or performance goals because these are either configuration objects not accessible via SumTotal's data API or belong to schema areas that Zoho Recruit does not support. We deliver a written inventory of these objects for the customer's admin to evaluate in Zoho Recruit's workflow builder or in a separate LMS/HRMS addition.

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

SumTotal logo

SumTotal

What's pushing teams away

  • The mobile app is consistently described as unreliable — login failures, connectivity issues, and learners not receiving credit for completed trainings drive frustration in environments where mobile access is expected.
  • Customer service scores are the weakest dimension of the product, with reviewers noting slow ticket resolution and unhelpful responses, compounding frustration when problems arise during migrations.
  • Pricing is repeatedly cited as prohibitively expensive for mid-market organisations; the per-user, enterprise-tier cost structure excludes organisations that cannot absorb large annual licensing commitments.
  • The Content Library's organisation and browsing experience is described as confusing — users struggle to find content without knowing exact course categories, which increases administrative overhead and learner drop-off.
  • Steep UI complexity and a steeper-than-expected learning curve are cited as barriers to adoption, especially when comparing SumTotal to modern alternatives like HiBob HRIS or 360Learning that score higher on usability.

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

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

SumTotal

Learners (Users)

maps to

Zoho Recruit

Candidate or Employee (via Custom Module)

1:1
Fully supported

SumTotal Learner records map to Zoho Recruit Candidates via the Candidate module. We extract first name, last name, email address, phone, hire date, and any custom profile fields. Last Name is mandatory in Zoho Recruit — any SumTotal learner record missing a last name is flagged and populated with 'not provided' before import per Zoho's import documentation. Users who already hold individual Zoho Recruit accounts must close those accounts before they can be imported into a company Zoho Recruit instance; we flag these conflicts during reconciliation. SumTotal user status (active, inactive, suspended) maps to Zoho Recruit Candidate status flags.

SumTotal

Courses / Curricula

maps to

Zoho Recruit

Custom Module (Courses) or Job Opening

1:many
Fully supported

SumTotal Courses and Curricula represent learning content rather than job requisitions and have no native Zoho Recruit equivalent. If SumTotal was used to track internal job requisitions or requisition-based training programs alongside its LMS functions, those requisitions map to Zoho Recruit Job Openings with associated Candidates. Standalone learning content (Courses, Curricula) is documented as a custom Zoho Creator or Zoho Recruit custom module for the customer's admin to configure post-migration, as it requires a separate content management strategy.

SumTotal

Training Records (Transcripts)

maps to

Zoho Recruit

Custom Module (Training History)

1:1
Fully supported

SumTotal Training Records (transcripts) capture what each learner completed, with completion dates, scores, and credit flags. We export the full transcript history and map it to a custom Training History module in Zoho Recruit, linked to the corresponding Candidate record via a Lookup relationship. Completion dates migrate as custom date fields; scores migrate as custom number fields. Note that Zoho Recruit's custom modules on Standard are limited to 50 fields per module, and Lookup fields are not available in Standard — the Professional or Enterprise tier is required for cross-module lookup relationships.

SumTotal

Compliance Certifications

maps to

Zoho Recruit

Custom Module (Certifications)

lossy
Mapping required

SumTotal Compliance Certification records include expiry dates, renewal rules, and audit-trail metadata. These map to a Zoho Recruit custom Certifications module with expiry date, renewal status, and issuing body as custom fields. Renewal automation logic (automated reminders, escalation triggers) does not migrate because SumTotal stores renewal rules as configuration objects not accessible via data API. We document the renewal rules for the customer's admin to rebuild as Zoho Recruit Workflow Rules post-migration.

SumTotal

ILT Sessions (Instructor-Led Training)

maps to

Zoho Recruit

Custom Module (Sessions)

lossy
Fully supported

SumTotal ILT Sessions include session metadata, registrations, attendance records, and venue/room associations. We export session-level metadata and registration records as a custom Sessions module linked to Candidates (attendees). Venue and room facility data is typically not fully exported from SumTotal and is documented as a Zoho Recruit custom field or note for manual completion post-migration.

SumTotal

Performance Goals / Performance Reviews

maps to

Zoho Recruit

Not migratable (talent management gated module)

1:1
Fully supported

SumTotal Goals and Performance Reviews are part of the talent management module, which is gated behind enterprise-tier licensing. Not all SumTotal tenants have this module active, and it has no equivalent in Zoho Recruit's ATS schema. We confirm module availability during scoping, exclude these objects from the migration contract, and document the performance data scope for the customer's HR leadership to evaluate whether Zoho People or a separate HRMS handles this post-migration.

SumTotal

Workflow Assignments and Automation Rules

maps to

Zoho Recruit

Not migratable (configuration objects)

lossy
Mapping required

SumTotal's automation engine drives learner assignment rules, deadline notifications, and escalation workflows stored as automation configuration rather than data records. The REST API does not export these rules. We document every active SumTotal workflow with its trigger, conditions, and actions in a written inventory delivered alongside the migration. The customer's admin rebuilds these as Zoho Recruit Workflow Rules (available on Standard and Enterprise at different limits: 5 per module on Standard, 50 on Enterprise) or as Blueprint processes on Enterprise.

SumTotal

Custom Fields and User-Defined Properties

maps to

Zoho Recruit

Custom Fields (Zoho Recruit)

lossy
Mapping required

SumTotal allows custom fields on standard objects. We capture every custom field definition (field name, type, validation rules, picklist values) alongside data exports. Zoho Recruit supports custom fields per module on paid tiers (50 per module on Standard, 300 on Professional, 300 on Enterprise). Custom field types including lookup, formula, multi-select picklist, and dependency fields are supported on Professional and Enterprise only. We pre-create all destination custom fields before import and map data types to their closest Zoho Recruit equivalents.

SumTotal

Job Openings / Requisitions (if active in SumTotal)

maps to

Zoho Recruit

Job Opening

1:1
Fully supported

If SumTotal was used to track internal job requisitions as part of its talent acquisition module, those requisitions map directly to Zoho Recruit Job Opening records. Job title, department, hiring manager, status, and description migrate as standard Zoho Recruit Job Opening fields. Zoho Recruit's Corporate plan comparison shows job opening limits per tier (1 on Free, 10 on Standard/recruiter, 20 on Enterprise/recruiter), which we confirm against the import scope during scoping.

SumTotal

Content Library Metadata

maps to

Zoho Recruit

Not migratable (content management gap)

1:1
Mapping required

SumTotal's Content Library holds course metadata including taxonomy, categories, and folder hierarchies used for content discoverability. The Content Library browsing and taxonomy navigation is not fully replicated via SumTotal's API export — we export the course records but the folder/category hierarchy requires manual reconstruction in Zoho Recruit's document management system (Zoho WorkDrive) or as a custom content module. We flag this as a manual post-migration step.

SumTotal

Users (SumTotal Admins and Instructors)

maps to

Zoho Recruit

Users (Zoho Recruit Staffing or Corporate)

1:1
Fully supported

SumTotal administrative users and instructors map to Zoho Recruit Users. We resolve SumTotal owner/instructor records by email against Zoho Recruit's User table. Zoho Recruit differentiates between staffing agency mode (Candidates, Clients, Job Openings) and corporate HR mode (Employees, Department, Candidates). The customer selects the deployment mode during Zoho Recruit onboarding; we align the migration object model to this selection during scoping.

SumTotal

Documents and Attachments

maps to

Zoho Recruit

Document Library or Candidate Attachments

1:1
Fully supported

SumTotal learner documents, course materials, and compliance certificates stored as attachments migrate to Zoho Recruit's Document Library (available on Standard and Enterprise). Candidate attachments (resumes, cover letters, credentials) migrate to Candidate attachment records linked via ContentDocumentLink. We export attachments in bulk and map them to the corresponding parent record in Zoho Recruit, preserving original file names and content types.

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.

SumTotal logo

SumTotal gotchas

High

50,000 req/hour API rate limit can throttle large exports

High

Enterprise-tier gating on talent management objects

Medium

Mobile app completion credits not reliably propagated to backend

Medium

Cornerstone OnDemand acquisition introduces v1/v2 API duality

Medium

Workflow automation rules are configuration objects not exported via data API

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

  • Schema mismatch between HRMS and ATS is fundamental

    SumTotal is an enterprise HRMS covering learning, talent, performance, and workforce management; Zoho Recruit is an ATS covering candidate sourcing, tracking, and hiring workflows. Most of SumTotal's core objects — Courses, Curricula, Training Records, Compliance Certifications, Performance Goals, and Workflow Automation Rules — have no direct equivalent in Zoho Recruit. We scope the migration to the subset of SumTotal data that can be represented in Zoho Recruit's schema and deliver a written inventory of unmappable objects for the customer's HR and IT leadership to evaluate for a separate LMS addition or manual process.

  • SumTotal 50,000 req/hour API ceiling can throttle large exports

    SumTotal's REST API caps RET API calls at 50,000 per hour per tenant, with some individual endpoints carrying tighter limits. When exporting large learner bases (thousands of learner records with associated training history) or full transcript archives, we pace requests below the ceiling and chunk large record sets across multiple export windows. We flag any 429 responses immediately and retry after the window resets. If the limit is hit during a live migration, we pause and resume rather than risk silent record omission. This is especially relevant for organisations that ran SumTotal as their primary LMS and have multi-year transcript histories to export.

  • Zoho Recruit requires Last Name and blocks pre-existing user accounts

    Zoho Recruit's data import requires a Last Name value for every Candidate record — records without a last name are ignored during import. SumTotal learner records occasionally lack a last name field, particularly for contractor or contingent worker profiles. We flag these records during data preparation and populate them with 'not provided' or 'none' per Zoho's import documentation. Separately, users who already hold a personal Zoho Recruit account cannot be imported into a company Zoho Recruit instance — they must close their individual account first. We run a pre-import reconciliation to identify and flag these conflicts before the import phase begins.

  • Custom fields and lookup fields gated by Zoho Recruit edition

    Zoho Recruit's custom field limits and lookup field availability are tier-dependent. Standard edition allows 50 custom fields per module but does not include Lookup or Formula fields — these require Professional or Enterprise. If the migration scope includes SumTotal custom fields that map to Zoho Recruit Lookup fields (for example, linking a Training History record to a Candidate), the customer must be on Professional or Enterprise at migration time. We confirm the destination edition during scoping and advise on any tier upgrade required before import begins.

  • SumTotal Cornerstone acquisition introduces v1/v2 API duality

    SumTotal was acquired by Cornerstone OnDemand in August 2022 and some tenants still reference legacy Skillsoft-era API endpoints. The current Swagger UI surfaces both v1 and v2 definitions with different object schemas. We disambiguate which API version applies to each tenant during discovery, normalise all paths to the v2 surface before migration begins, and prevent field-mismatch failures at import time. This is particularly relevant for tenants who were migrated from Skillsoft or who have legacy integration connections pointing to older endpoint paths.

Migration approach

Six steps for a successful SumTotal to Zoho Recruit data migration

  1. Discovery and module availability audit

    We audit the source SumTotal tenant across modules (LMS base, Professional/Advanced, or Enterprise full suite), API endpoint version (v1 vs v2), custom field definitions on standard objects, active learner counts, transcript volumes, compliance certification records, and any active talent management modules. We confirm which modules are licensed at the current tenant because talent management objects (Goals, Performance Reviews) are not available on base LMS tier and cannot be exported if the tenant does not hold that license. We also confirm SumTotal's current API credentials, rate limit utilisation, and any legacy Skillsoft-era endpoint references still active in the tenant. The discovery output is a written migration scope listing in-scope and out-of-scope objects with availability justifications.

  2. Zoho Recruit edition selection and schema preparation

    We confirm the destination Zoho Recruit edition (Standard at $25/user/month, Professional at $50/user/month, or Enterprise at $75/user/month) based on the migration scope. If the scope includes custom fields with lookup relationships or cross-module references, Professional or Enterprise is required. We create the destination schema in Zoho Recruit: custom modules (Training History, Certifications, Sessions if required), custom fields with field types mapped from SumTotal definitions, Workflow Rules framework, and page layout assignments. We also configure Zoho Recruit's deployment mode (Staffing Agency vs Corporate HR) to align with the customer's hiring model. Schema preparation happens in the customer's live Zoho Recruit account before any data import.

  3. Data extraction from SumTotal in dependency order

    We extract SumTotal data in dependency order: Users and Admins first (resolved by email for Zoho Recruit User matching), then Learners (mapped to Candidates), Job Openings (if present), Training Records (transcripts), Compliance Certifications, and ILT session registrations. We pace exports below the 50,000 req/hour ceiling and chunk large record sets across multiple windows. Each module export produces a CSV file with field names aligned to the SumTotal v2 API schema, with any legacy v1 field names normalised. We flag any 429 rate-limit responses and resume after the window resets. All exports include a record-count reconciliation report comparing source tenant record counts to exported file record counts.

  4. Data cleaning, field mapping, and mandatory field resolution

    We clean the exported data before import: populating missing Last Name fields with 'not provided' per Zoho Recruit's mandatory field requirement, de-duplicating records by email address, validating email formats, resolving custom field picklist values to match Zoho Recruit's picklist definitions, and mapping SumTotal custom fields to their Zoho Recruit equivalents. We build a field mapping document that pairs every SumTotal field in scope with its Zoho Recruit destination field, field type, and any transformation logic applied (date format normalisation, multi-select to comma-separated text, etc.). Records with unresolved Zoho Recruit User references (SumTotal owners without matching Zoho accounts) are held in a reconciliation queue.

  5. Import sequencing and reconciliation

    We import data into Zoho Recruit in dependency order: Users first (validated against the Zoho Recruit User table), then Candidates (linked to Users by email), Job Openings (linked to Candidates), custom module records (Training History, Certifications linked to Candidates via Lookup on Professional/Enterprise), and finally attachments. Each phase emits a row-count reconciliation report. We validate that record counts in Zoho Recruit match the exported file totals and flag any discrepancies for investigation before the next phase begins. We run a spot-check of 25-50 records per module comparing source SumTotal values to imported Zoho Recruit values to confirm mapping accuracy.

  6. Cutover, delta migration, and workflow rebuild handoff

    We freeze SumTotal writes during cutover, run a final delta export of any records modified during the migration window, and import the delta into Zoho Recruit. We then enable Zoho Recruit as the system of record. We deliver the written automation inventory — documenting every SumTotal workflow, assignment rule, deadline escalation, and notification trigger — with recommended Zoho Recruit Workflow Rule and Blueprint equivalents for the customer's admin to rebuild. We do not rebuild SumTotal automation as Zoho Recruit Workflow Rules inside the migration scope; that is a separate engagement or an internal admin task. We provide a one-week post-migration hypercare window for reconciliation issues raised during the first recruiting cycle in Zoho Recruit.

Platform deep dives

Context on both ends of the pair

SumTotal logo

SumTotal

Source

Strengths

  • Integrated suite covering learning, talent, and workforce management on one platform reduces tool sprawl for large enterprises.
  • Powerful reporting engine with flexible automated report scheduling for compliance tracking and audit trails.
  • Deep automation capabilities for learner assignment, deadline rules, and compliance certification enforcement.
  • Learning Administration feature is fully manageable internally post-implementation, reducing reliance on vendor support.
  • ServiceNow integration via the SumTotal spoke enables workflow continuity for IT-managed HR operations.

Weaknesses

  • Mobile app is unreliable with inconsistent login, connectivity, and course-completion credit issues.
  • Customer service scores are below category average, with slow ticket resolution times reported.
  • Per-user enterprise pricing structure is prohibitively expensive for mid-market organisations.
  • Content Library browsing is confusing without prior knowledge of exact course categories — navigation lacks intuitive discoverability.
  • Steep UI complexity creates a steeper-than-expected learning curve compared to modern HRMS alternatives.
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 SumTotal 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

    SumTotal: 50,000 requests per hour per tenant across all REST APIs, with some individual endpoints carrying lower per-endpoint limits documented in the Swagger.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your SumTotal 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 four weeks for organisations with up to 5,000 candidate records, fewer than 50 job openings, and a limited number of SumTotal modules in scope. Migrations with large learner bases (thousands of transcript records), multiple SumTotal modules (LMS, talent, workforce), complex custom field definitions, or compliance certification archives requiring custom module configuration move to six to ten weeks. The most significant timeline variable is whether SumTotal was used primarily as an LMS with learning content requiring custom module reconstruction in Zoho Recruit, versus an ATS-adjacent use case with cleaner data portability.

Adjacent paths

Related migrations to explore

Ready when you are

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