HRMS migration

Migrate from SumTotal to Recruit CRM & ATS

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

SumTotal logo

SumTotal

Source

Recruit CRM & ATS

Destination

Recruit CRM & ATS logo

Compatibility

17%

2 of 12

objects map 1:1 between SumTotal and Recruit CRM & ATS.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Migrating from SumTotal to Recruit CRM is a cross-category move: SumTotal is an enterprise HRMS covering learning, talent, performance, and workforce management, while Recruit CRM is a recruitment ATS and CRM built for staffing and executive search agencies. The primary migration path is SumTotal Learners to Recruit CRM Candidates, with SumTotal Companies (if the HRMS holds client or organizational data) mapping to Recruit CRM Clients. Courses, Curricula, Training Records, Compliance Certifications, Performance Goals, and ILT Sessions have no direct Recruit CRM equivalent because Recruit CRM does not function as an LMS. We export these objects and deliver them as a structured data package for the customer's records, but they cannot be imported as working records in Recruit CRM. SumTotal's API rate limit of 50,000 requests per hour affects export pacing for large learner bases, and enterprise-tier gating on talent management objects must be confirmed during scoping because some modules are not accessible at lower licensing tiers. Workflow automation rules, deadline escalation configurations, and assignment logic are configuration objects that do not export via the SumTotal data API; we document them and hand off a rebuild guide for Recruit CRM's automation tooling.

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

Recruit CRM & ATS logo

Recruit CRM & ATS

What's pulling them in

  • Agencies choose Recruit CRM for its full customizability — pipelines, stages, and fields can be tailored to any recruitment workflow without developer involvement.
  • Small teams value the built-in CRM and ATS combined in one subscription, eliminating the need to purchase and sync separate systems.
  • The Chrome extension for one-click LinkedIn profile collection streamlines candidate sourcing and reduces manual data entry for recruiters.
  • Responsive customer support with fast issue resolution is consistently cited as a reason teams stick with the platform long-term.
  • Automation options including email sequences and workflow triggers allow recruitment agencies to reduce repetitive manual outreach tasks.

Object mapping

How SumTotal objects map to Recruit CRM & ATS

Each row shows how a SumTotal object lands in Recruit CRM & ATS, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

SumTotal

Learner (User)

maps to

Recruit CRM & ATS

Candidate

1:1
Fully supported

SumTotal Learner records are the primary migration object into Recruit CRM Candidate records. The mapping uses email as the dedupe key. First name, last name, and email map directly. Custom fields on the Learner profile (such as department, location, manager, or custom hire-date fields) map to Recruit CRM custom fields on Candidate where the field type is compatible. SumTotal user status (active, inactive, suspended) maps to Candidate active/inactive flags, with suspended users flagged separately for customer review before activation. This is a 1:1 field-level mapping with custom field extension support.

SumTotal

Company

maps to

Recruit CRM & ATS

Client

1:1
Fully supported

SumTotal Companies (organisational units or client structures stored within the HRMS) map to Recruit CRM Client records if present in the source tenant. Not all SumTotal deployments use the Company object. We confirm Company object presence during scoping. Company name, domain, and primary contact fields map to Client name, website, and primary contact respectively. If SumTotal Companies reference the Learner object via manager relationships, those references cannot map to Recruit CRM's candidate model and are flagged as non-migratable relationships.

SumTotal

Course

maps to

Recruit CRM & ATS

Not migratable to Recruit CRM

lossy
Fully supported

SumTotal Courses are LMS objects with no equivalent in Recruit CRM's ATS and recruitment CRM model. Recruit CRM does not maintain a course catalog, training catalog, or learning content repository. We export Course records as a structured CSV and JSON package for the customer's records but do not import them into Recruit CRM. This is disclosed upfront during scoping and reflected in the migration contract scope.

SumTotal

Curriculum

maps to

Recruit CRM & ATS

Not migratable to Recruit CRM

lossy
Fully supported

SumTotal Curricula bundle courses into structured learning paths with ordering and deadline configurations. Recruit CRM has no learning path or curriculum object. We export Curriculum-to-Course associations as a relationship table in the deliverables package. If the customer needs to preserve which learners were assigned which curricula, we can export that assignment history as a Candidate note or custom field attachment in Recruit CRM as a workaround.

SumTotal

Training Record (Transcript)

maps to

Recruit CRM & ATS

Candidate custom field or note attachment

lossy
Fully supported

SumTotal Training Records (transcripts) carry completion dates, scores, and credit flags tied to Learner and Course IDs. Since Recruit CRM has no course object, training completion records cannot be stored as structured records. We export the full transcript history and attach it as a structured document (CSV) to the Candidate record, or we extract the last completion date and key certification fields into Candidate custom fields if the customer wants at-a-glance visibility without opening an attachment.

SumTotal

Compliance Certification

maps to

Recruit CRM & ATS

Not migratable to Recruit CRM

lossy
Fully supported

Compliance Certifications in SumTotal carry expiry dates, renewal rules, and audit-trail metadata tied to regulatory contexts (OSHA, GDPR, FINRA, industry-specific mandates). Recruit CRM does not have a compliance certification object or expiry tracking for candidate credentials. We export certification records as a structured data package. If the customer's recruiting workflow requires visibility into candidate certifications, we can store certification name, expiry date, and status as custom fields on the Candidate record as a partial workaround.

SumTotal

Performance Goal

maps to

Recruit CRM & ATS

Not migratable to Recruit CRM

lossy
Fully supported

Performance Goals are part of SumTotal's talent management module and are gated behind enterprise-tier licensing. Recruit CRM is a recruitment ATS and does not include goal management or performance review functionality. We confirm module availability during scoping (tenants on base LMS tier cannot export Goals). Goals that exist are exported as a structured data package for the customer's HR or operations team to retain outside of Recruit CRM.

SumTotal

Performance Review

maps to

Recruit CRM & ATS

Not migratable to Recruit CRM

lossy
Fully supported

Performance Review records include 360-degree feedback, ratings, and reviewer assignments stored as complex nested structures varying by organisation-specific templates. Recruit CRM has no performance review object. We extract raw review data and deliver it as a structured export. Review metadata (reviewer name, review period, overall rating) can be attached as a note to the Candidate record if the customer wants historical performance context preserved within the ATS.

SumTotal

ILT Session (Instructor-Led Training)

maps to

Recruit CRM & ATS

Not migratable to Recruit CRM

lossy
Fully supported

ILT Sessions in SumTotal include session metadata, registrations, attendance records, and venue associations. Recruit CRM does not have a training session or scheduling object beyond its candidate interview and meeting scheduling features. Attendance records and room/venue data do not migrate. We export session and registration data as a structured package for the customer's records.

SumTotal

Custom Field Definitions

maps to

Recruit CRM & ATS

Custom Fields

lossy
Mapping required

SumTotal allows custom fields on standard objects (Learner, Course, Curriculum). We capture custom field definitions alongside data exports, including field types, validation rules, and picklist values. These definitions map to Recruit CRM custom fields on Candidate where the destination field type supports equivalent data. Custom field types that have no Recruit CRM equivalent (such as SumTotal-specific complex validation) are documented in the deliverables with a non-migratable flag.

SumTotal

Workflow Assignments and Automation Rules

maps to

Recruit CRM & ATS

Not migratable to Recruit CRM

lossy
Mapping required

SumTotal's automation engine drives learner assignment rules, deadline escalation, and notification triggers stored as configuration rather than data records. The REST API exports learner data but does not export automation rules. We document which workflows exist with a written inventory describing trigger conditions, actions, and destinations. Recruit CRM's workflow automation must be rebuilt manually by the customer's admin using Recruit CRM's workflow builder. We provide the documented inventory and recommended mapping as part of the deliverables package.

SumTotal

Content Library Metadata

maps to

Recruit CRM & ATS

Not migratable to Recruit CRM

lossy
Mapping required

SumTotal's Content Library holds course metadata with folder and category taxonomy. Recruit CRM does not have a content library or taxonomy navigation feature. Folder and category hierarchy cannot be replicated. We export course-level metadata records only; the browsing and categorisation structure is not portable to Recruit CRM's flat candidate and job record model.

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

Recruit CRM & ATS logo

Recruit CRM & ATS gotchas

High

API rate limits are license-scaled and can throttle bulk migration

Medium

Custom field schemas vary per organization and require field-level mapping

Medium

Files and email attachments require separate extraction and re-upload

Low

Email sequences and automation logic do not transfer between platforms

Pair-specific challenges

  • Most SumTotal modules have no Recruit CRM equivalent

    SumTotal is an enterprise HRMS and LMS; Recruit CRM is a recruitment ATS and CRM. Courses, Curricula, Training Records, Compliance Certifications, Performance Goals, Performance Reviews, and ILT Sessions are core SumTotal objects that have no equivalent data model in Recruit CRM. We export these objects as structured data packages and document what cannot be imported, but customers must understand before signing the migration contract that these records will not become working records in Recruit CRM. Treating the migration as a full data transfer when most of the schema is not compatible is the most common source of post-migration disputes in cross-category migrations.

  • SumTotal API rate limit throttles large learner exports

    SumTotal's REST API caps RET API calls at 50,000 per hour per tenant. Large learner bases (10,000+ records) with extensive training histories can exceed this ceiling during export. We pace requests below the ceiling, chunk large record sets across multiple export windows, and pause immediately on any 429 response rather than risking silent record omission. If the limit is hit during a live migration window, we pause and resume after the window resets rather than retrying blindly.

  • Enterprise-tier gating on talent management objects

    SumTotal's talent management module (Goals, Performance Reviews, Compensation) is not available on all licensing tiers. Customers running only the base LMS tier cannot export these objects even if records theoretically exist. We confirm module availability during scoping and exclude unavailable objects from the migration contract rather than leaving customers expecting a complete export that is technically impossible at their licensing level. This is especially relevant because some customers believe they have access to these modules based on historical data they can see in the UI but cannot actually export.

  • SumTotal v1 and v2 API duality requires normalisation

    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 and normalise all paths to the v2 surface before migration begins. Skipping this step produces field-mismatch failures at import time when v1 field names do not correspond to the correct Recruit CRM import field definitions.

  • Recruit CRM migration cost scales on total record count in source

    Recruit CRM's documented migration pricing is calculated on the total number of records in the database, not the number of records being imported. If the SumTotal tenant holds 50,000 learner records but the customer wants only 10,000 active ones migrated, the cost is still scoped on the full 50,000 unless the customer applies data filtering during scoping. We confirm the migration scope filter early (active vs inactive, date ranges, organisational units) to avoid cost surprises at invoice time. Filtering at scoping can reduce migration cost substantially.

Migration approach

Six steps for a successful SumTotal to Recruit CRM & ATS data migration

  1. Discovery and scope confirmation

    We audit the SumTotal tenant across licensing tier, active modules, learner record count, custom field definitions, and any historical training or certification data the customer wants preserved. We confirm which SumTotal modules are accessible at the current tier (talent management gating is a common blocker). We pair this with a Recruit CRM account audit to confirm custom field availability and any existing Client, Job, or Candidate structures. The discovery output is a written migration scope that explicitly lists which objects migrate to Recruit CRM as working records, which migrate as export packages, and which have no migration path, signed by both parties before migration begins.

  2. Data filtering and migration scope lock

    SumTotal record counts determine migration cost at Recruit CRM. We work with the customer to define filters: active only or all records, date-range cutoffs, specific organisational units, and any records to be archived rather than migrated. We apply these filters to SumTotal API queries during export rather than exporting everything and filtering after, which avoids unnecessary API calls against the 50,000 req/hour ceiling. The filtered scope is locked before export begins to prevent scope creep mid-migration.

  3. Schema design and custom field provisioning

    We design the Recruit CRM destination schema before any data moves. This includes provisioning custom fields on the Candidate record to receive SumTotal custom fields (department, location, manager, hire date, etc.) and any custom fields created to hold training completion dates or certification status as a partial workaround for non-migratable objects. We also map the Candidate field schema so that Recruit CRM's import tool can receive the CSV structure we generate from SumTotal exports. If SumTotal Companies exist, we provision Client records and map the relationship to Candidate.

  4. Export with API rate-limit pacing

    We export SumTotal Learner records in batches paced below the 50,000 req/hour ceiling, with row-count reconciliation after each batch. Training Records and Compliance Certifications are exported separately and attached as structured packages. Custom field definitions are extracted alongside data records so that field types and validation rules are preserved in the mapping documentation. We normalise v1 endpoints to v2 during export so that field names match the current SumTotal API schema. Any records that return as inactive or suspended in SumTotal are flagged for customer review before being set as inactive in Recruit CRM.

  5. Test import and reconciliation

    We run a test import with a subset of exported records into a Recruit CRM staging environment. The customer reconciles record counts, spot-checks 25-50 candidate records against the SumTotal source for field accuracy, and validates that custom fields populated correctly. Mapping corrections (field name mismatches, data type issues, missing required fields in Recruit CRM) are resolved here before the full production import. Any objects flagged as non-migratable are confirmed as export-only in the deliverables package at this stage.

  6. Production migration and cutover

    We run the full production migration in record-dependency order: Recruit CRM custom fields and Client records first (if applicable), then Candidate records with the dedupe key resolved from SumTotal Learner email. Training and certification export packages are delivered as CSV and JSON attachments to the relevant Candidate records. We freeze SumTotal write access during the cutover window, run a final delta export of any records modified during migration, then enable Recruit CRM as the system of record. We deliver the automation inventory document to the customer's admin team for Recruit CRM workflow rebuild. We do not rebuild SumTotal automation rules as Recruit CRM workflows inside the migration scope; that is a separate engagement or an internal admin task.

  7. Non-migratable object deliverables and handoff

    We deliver a structured export package for all objects that cannot be imported into Recruit CRM (Courses, Curricula, Training Records, Compliance Certifications, Performance Goals, Reviews, ILT Sessions, Content Library metadata). This package includes raw data exports, relationship tables, and field definitions. We also deliver the workflow automation inventory with triggers, conditions, and recommended Recruit CRM equivalents documented. The customer's HR, LMS, or operations team retains these packages outside of Recruit CRM. We do not provide ongoing access to these records post-migration unless a separate data-retention engagement is contracted.

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.
Recruit CRM & ATS logo

Recruit CRM & ATS

Destination

Strengths

  • Fully customizable pipelines, stages, and fields without requiring developer involvement
  • Combines recruitment CRM and ATS in one subscription for staffing agencies and small teams
  • Built-in email sequences and automation reduce manual outreach work
  • Chrome extension enables one-click LinkedIn profile collection directly into the CRM
  • Responsive customer support cited across multiple reviews with fast resolution times

Weaknesses

  • Several features are gated as paid add-ons rather than included in the base subscription
  • Email functionality has been reported as unreliable by multiple users
  • Interface occasionally lags during high-activity periods in large pipelines
  • Pricing is considered higher than comparable recruitment CRMs by some customers
  • Limited native reporting — users request pre-made report exports rather than manual data pulls

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 Recruit CRM & ATS.

  • 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 Recruit CRM & ATS 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 Recruit CRM & ATS data migrations

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

Can't find your answer?

Walk through your SumTotal to Recruit CRM & ATS migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most migrations land between three and five weeks for tenants with fewer than 10,000 active learner records and no complex custom field structures. Migrations with large historical training records, multiple SumTotal modules in scope, custom object configurations, or large-scale data filtering requirements move to eight to twelve weeks because of the cross-category schema gap analysis, the delta-export work for non-migratable objects, and the custom field provisioning time in Recruit CRM.

Adjacent paths

Related migrations to explore

Ready when you are

Move from SumTotal.
Land in Recruit CRM & ATS, 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