CRM migration

Migrate from Oncourse CRM to Nutshell

Field-level mapping, validation, and rollback between Oncourse CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Oncourse CRM logo

Oncourse CRM

Source

Nutshell

Destination

Nutshell logo

Compatibility

63%

5 of 8

objects map 1:1 between Oncourse CRM and Nutshell.

Complexity

BStandard

Timeline

2-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Oncourse CRM to Nutshell is a schema-normalization migration. Oncourse CRM stores organization names as a Contact property rather than a distinct Account object, so we extract every organization value, deduplicate it, and create Nutshell Company records before importing any Contact. This ensures the People-to-Company lookup relationship is satisfied at import time rather than patched afterward. Oncourse CRM also records activity history as freeform Notes rather than structured activity records, which means we cannot reconstruct a native Nutshell activity timeline from the source data; we preserve the note content as Note records attached to the appropriate Contact or Deal. Deals, Pipeline Stages, and Tasks migrate 1:1, with stage names mapped directly. Custom fields on Contacts, Leads, and Deals are exposed via Oncourse DSL export and map to equivalent Nutshell custom properties with type preservation. Workflows, automations, and attachment files do not migrate; we deliver a written inventory of any active workflows requiring manual rebuild in Nutshell.

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

Oncourse CRM logo

Oncourse CRM

What's pushing teams away

  • Public API documentation is limited — custom integrations are described as 'requires more technical know-how' and there is no self-service developer portal.
  • Activity history is stored as notes rather than structured Activity records, limiting reporting depth and making clean migration off the platform harder.
  • Attachment export is not supported by the standard tooling — files in the document store have to be manually backed up before migration.
  • Small market footprint and limited public review volume make peer benchmarking against established competitors (HubSpot, Pipedrive, Close) harder.
  • Voice/SMS allowances are capped (400 minutes / 400 SMS on Standard) — high-volume outbound teams hit overage or per-line surcharges quickly.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Oncourse CRM objects map to Nutshell

Each row shows how a Oncourse CRM object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.

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

Oncourse CRM

Lead

maps to

Nutshell

Lead

1:1
Fully supported

Oncourse CRM Lead records (distinct from Contacts, with source and status properties) map directly to Nutshell Lead. We preserve lead source, lead status, and any custom field values during import. The Nutshell Lead object serves as the top-level unqualified prospect record, distinct from People which represent known contacts.

Oncourse CRM

Contact

maps to

Nutshell

People

1:1
Fully supported

Oncourse CRM Contact records map to Nutshell People. Standard fields (name, email, phone, address) map without transformation. Organization values stored in Oncourse CRM's organization Contact property are held during import and used to create Nutshell Company records before People insertion.

Oncourse CRM

Company (extracted from Contact)

maps to

Nutshell

Company

1:many
Fully supported

Oncourse CRM does not have a distinct Account object; organization names live as a property on Contact. We extract every unique organization value, deduplicate (normalizing for case and whitespace), and create Nutshell Company records. Each People record is then linked to its Company via the People-Company lookup at insert time. This resolves the flat-to-normalized schema gap that would otherwise leave Nutshell People unassociated with any Company.

Oncourse CRM

Deal

maps to

Nutshell

Deal

1:1
Fully supported

Oncourse CRM Deal records map directly to Nutshell Deal. We preserve deal name, monetary value, stage, and owner assignment. Closed-Lost and Closed-Won statuses migrate as the applicable Nutshell pipeline stage. Owner assignment maps from Oncourse CRM owner to Nutshell user by email match.

Oncourse CRM

Pipeline Stage

maps to

Nutshell

Pipeline Stage

lossy
Fully supported

Oncourse CRM pipeline stages are per-account and customizable. We extract the customer's active stage names during scoping and create matching Nutshell pipeline stages before Deal import. Stage probability percentages are mapped if present in Oncourse CRM. If Nutshell does not have an equivalent stage name, we create it in the destination before migration begins.

Oncourse CRM

Task

maps to

Nutshell

Task

1:1
Fully supported

Oncourse CRM tasks associated with Deals map to Nutshell Tasks linked to the corresponding Deal. Task subject, status (open/closed), due date, and owner assignment migrate directly. We resolve the parent Deal reference at migration time using deal name as the dedupe key.

Oncourse CRM

Note (activity history)

maps to

Nutshell

Note

1:1
Fully supported

Oncourse CRM records activity history as freeform Notes rather than structured Call/Email/Meeting records. These migrate as Nutshell Note records attached to the relevant People or Deal. This is a data-shape limitation: Nutshell will display the note content, but the native activity timeline (Calls, Emails, Meetings) cannot be reconstructed from Oncourse CRM source data. We flag this gap in the scoping document and recommend manual activity logging post-migration if a structured timeline is required.

Oncourse CRM

Custom Fields

maps to

Nutshell

Custom Fields

lossy
Mapping required

Oncourse CRM custom fields on Contacts, Leads, and Deals are exposed via DSL export. We map each to a Nutshell custom property of equivalent data type (text, number, date, dropdown). Custom field names and API identifiers are preserved where possible. Nutshell's custom field UI handles field creation before data import begins.

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.

Oncourse CRM logo

Oncourse CRM gotchas

High

Attachments are not exportable via the standard import/export tooling

Medium

Activity history lives in notes, not structured records

Medium

Pipeline stages are tenant-defined free text

Low

Voice and SMS allowances cap at 400 each on Standard

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Activity history migrates as Notes, not native activities

    Oncourse CRM stores activity history (call notes, email content, meeting summaries) as freeform Notes rather than structured activity records with typed categories. When migrating to Nutshell, we preserve the note content as Note records attached to People or Deals, but Nutshell's native activity timeline (Calls, Emails, Meetings, Tasks) cannot be populated from the source data shape. Teams that rely on the activity timeline for rep coaching or compliance logging should be aware that post-migration manual activity logging or a third-party integration (phone system, email sync) is required to restore structured activity tracking.

  • Organization deduplication required before Company creation

    Oncourse CRM does not have a Company or Account object; organization names are stored as a flat property on Contact. This means identical organizations may appear under variant names (e.g., Acme Corp, Acme Corporation, acme corp) across multiple Contact records. We deduplicate organization values before creating Nutshell Companies, but the customer should review the deduplication logic during scoping. Incorrect deduplication results in split Company records or orphaned People records with no Company association.

  • No public attachment export from Oncourse CRM

    Oncourse CRM does not expose a public file attachment export via its standard import/export tooling. Files stored within the platform (document attachments, images, signed documents) cannot be retrieved through automated extraction. We recommend a manual backup of the document repository before migration. In Nutshell, files can be re-uploaded manually or through a bulk upload process after records are in place.

  • Oncourse CRM owner assignment is optional; Nutshell requires Deal ownership

    Oncourse CRM allows Deals without an assigned owner. Nutshell requires a person (user) to be assigned as the Deal owner. During migration, Deals without an Oncourse CRM owner are held in a reconciliation queue. The customer's admin assigns an active Nutshell user before those Deals are inserted. Skipping this step results in import failures for ownerless Deals.

Migration approach

Six steps for a successful Oncourse CRM to Nutshell data migration

  1. Source data extraction and scoping

    We audit the Oncourse CRM account for record counts (Leads, Contacts, Deals, Tasks, Notes), custom field definitions, pipeline stage names, and owner assignments. We use the Oncourse DSL export or CSV export tooling to extract records and validate schema coverage. The scoping output is a written migration scope document with record counts, field mapping, and any data shape limitations (noted above) requiring customer decisions before migration begins.

  2. Organization deduplication and Company pre-creation

    We extract every unique organization value from the Oncourse CRM Contact organization field, normalize (trim whitespace, normalize case, collapse punctuation variants), deduplicate, and create Nutshell Company records before any People import. This step resolves the flat-to-normalized schema gap. The customer reviews the deduplication output and approves merge decisions before Company records are created.

  3. Nutshell schema setup

    We configure Nutshell pipeline stages to match the Oncourse CRM stage names, create any missing stages, and set probability percentages. We create custom fields in Nutshell matching the Oncourse CRM custom field definitions (with type mapping for text, number, date, and dropdown). If the customer requires specific Nutshell page layouts or field visibility settings, we configure these before record import.

  4. Record import in dependency order

    We import in dependency order: Nutshell Companies (created in step 2), then Leads (1:1), then People with Company lookup resolved, then Deals with OwnerId and CompanyId resolved, then Tasks linked to Deals, then Notes attached to People or Deals. Each phase emits a row-count reconciliation report. Owner mapping uses email match; any unmatched owner goes to a reconciliation queue for admin resolution before the Deals phase.

  5. Cutover, validation, and workflow handoff

    We freeze Oncourse CRM writes during cutover, run a delta migration for any records modified during the migration window, then mark Nutshell as the system of record. We deliver a written inventory of any active Oncourse CRM workflows or configurations requiring rebuild in Nutshell. We do not rebuild workflows as Nutshell automations inside the migration scope; that is a separate admin task. A one-week hypercare window covers reconciliation issues raised by the sales team post-go-live.

Platform deep dives

Context on both ends of the pair

Oncourse CRM logo

Oncourse CRM

Source

Strengths

  • Unified phone dialer, SMS, email sequencing and CRM in one product
  • Low entry price (Basic $14.99/user/month; Standard $49.95/user/month on annual)
  • Drag-and-drop pipeline with customisable stages tuned for small-team sales motions
  • Outlook, Gmail and Google Calendar integrations supported natively
  • Card-view pipeline and mobile CRM access for on-the-go sales teams

Weaknesses

  • Public API documentation is sparse; custom integrations require Zibtek dev work
  • Activity history stored as notes rather than structured Activity records
  • Standard attachment export is not supported — files must be backed up manually
  • Voice (400 min) and SMS (400) caps on Standard limit high-volume outbound teams
  • Small ecosystem and limited public reviews relative to HubSpot, Pipedrive, Close
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 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 Oncourse CRM and Nutshell.

  • Object compatibility

    B

    2 of 8 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

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

  • API constraints

    B

    Oncourse CRM: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Oncourse CRM to Nutshell 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 Oncourse CRM to Nutshell data migrations

Answers to the questions buyers ask most during Oncourse CRM to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Oncourse CRM to Nutshell 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 under 5,000 Contacts and 1,500 Deals with clean organization data and straightforward pipeline stages. Migrations with high organization deduplication complexity, large custom field sets, or multi-stage pipeline structures move to four to six weeks because of the pre-creation and reconciliation work required for the Company lookup resolution.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Oncourse CRM.
Land in Nutshell, 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