CRM migration

Migrate from Onpipeline to Nutshell

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

Onpipeline logo

Onpipeline

Source

Nutshell

Destination

Nutshell logo

Compatibility

75%

6 of 8

objects map 1:1 between Onpipeline and Nutshell.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Onpipeline to Nutshell is a mid-market sales CRM migration that consolidates the core CRM record types (People, Companies, Deals) while leaving Onpipeline-specific post-sale objects (Invoices, Products with inventory) to be assessed based on the customer's Nutshell plan tier. Onpipeline has no native export endpoint beyond its API, and Nutshell's Import2 integration list does not include Onpipeline, so we build the migration pipeline directly from the Onpipeline REST API into Nutshell's Contacts, Accounts, and Opportunities objects. We preserve Quote headers and line items, flag Invoices for manual settlement review at the destination, and map Onpipeline Pipeline Stages to Nutshell's stage configuration. Workflows, automations, and Onpipeline's integrated invoice generator do not migrate; we deliver a written inventory of these for the customer's admin to configure in Nutshell or through a separate billing integration.

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

Onpipeline logo

Onpipeline

What's pushing teams away

  • Limited advanced automation or workflow builder compared to HubSpot or Salesforce, leaving power users wanting more complex rule-based processes.
  • Reporting and analytics are described as functional but not as deep or customizable as larger CRM platforms.
  • Multi-currency or multi-entity support is minimal, making it less suitable for businesses with complex international structures.
  • Smaller ecosystem of third-party integrations compared to market leaders, requiring more custom API work for niche tools.

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 Onpipeline objects map to Nutshell

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

Onpipeline

Contact

maps to

Nutshell

Person or Lead

1:many
Fully supported

Onpipeline Contacts with a lifecycle stage of customer or evangelist map to Nutshell Person. Contacts without a deal association or in early funnel stages map to Nutshell Lead. We apply the split using Onpipeline's lifecycle_stage property at migration time and preserve the original stage in a custom field op_original_stage__c on both Person and Lead for audit and reporting continuity.

Onpipeline

Company

maps to

Nutshell

Account

1:1
Fully supported

Onpipeline Company records map directly to Nutshell Account. The company domain or website field becomes the Account's website for deduplication. Account is created before any Person import so that the Account-Person link is satisfied at the moment of Person insert. If Onpipeline Contacts are linked to a Company, we resolve the AccountId reference during Person import.

Onpipeline

Deal

maps to

Nutshell

Opportunity

1:1
Fully supported

Onpipeline Deals map to Nutshell Opportunity. The deal value, stage, probability, and expected close date migrate directly. Onpipeline Pipeline Stages map to Nutshell Stage values, and we configure the stage probabilities in Nutshell's pipeline settings before migration. Closed-Lost and Closed-Won custom fields become Nutshell Loss Reason and Won Reason text fields.

Onpipeline

Pipeline Stage

maps to

Nutshell

Stage

lossy
Fully supported

Each Onpipeline pipeline and its custom stages are mapped to Nutshell Stage values. We capture the full stage hierarchy (stage name, probability percentage, order) and configure Nutshell's pipeline stages to match before Deal import begins. If the customer has multiple Onpipeline pipelines, we map them to separate Nutshell pipelines on Pro tier or above.

Onpipeline

Activity / Events

maps to

Nutshell

Activity

1:1
Fully supported

Onpipeline Events (calendar appointments with datetime, duration, assigned user, and description) migrate as Nutshell Activity records linked to the parent Person, Account, or Opportunity. Notes attached to Deals or Contacts migrate as Activity notes within the same record. Onpipeline's user-scoped calendar means each user's events import under that user's Activity feed in Nutshell. We preserve the original event timestamp as the Activity date.

Onpipeline

Product

maps to

Nutshell

Product

1:1
Fully supported

Onpipeline Products (name, SKU, price, stock quantity) migrate to Nutshell Product. We preserve the product name, SKU, and unit price. Note that Nutshell's Sales Suite does not include native inventory management, so the stock quantity field is stored as a custom numeric field on the Product record rather than a live inventory count. If the customer relies on Onpipeline's inventory alerts, they should configure a separate inventory tracking solution post-migration.

Onpipeline

Quote

maps to

Nutshell

Quote

1:1
Fully supported

Onpipeline Quotes with headers, line items, pricing, and e-signature status migrate to Nutshell Quote. Quote line items reference the migrated Product records via the Nutshell Product ID. The Quote status (draft, sent, signed) migrates directly. If the Quote PDF or e-signature document is stored in Onpipeline, we attach it as a file to the Nutshell Quote record.

Onpipeline

User / Owner

maps to

Nutshell

User

1:1
Fully supported

Onpipeline Users are mapped to Nutshell Users by email address match. Any Onpipeline Owner referenced on a Deal without a matching Nutshell User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Onpipeline users map to inactive Nutshell users to preserve historical attribution.

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.

Onpipeline logo

Onpipeline gotchas

High

Trial account data deleted 7 days after expiry

Medium

Calendar is user-scoped, not team-wide by default

Low

Recurring invoice automation gated to Advanced plan

Low

Facebook Lead Ads import requires API or Zapier setup

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

  • Nutshell has no native Onpipeline import connector

    Nutshell's Import2 integration list does not include Onpipeline, so the migration cannot use Nutshell's self-service import wizard for this pair. We build the migration pipeline directly from the Onpipeline REST API, handling pagination, field selection, and rate-limit responses without relying on a CSV export-import path. Customers who have been waiting for a native connector should expect custom API work rather than a point-and-click import.

  • Onpipeline trial data is deleted 7 days after expiry

    Onpipeline suspends access immediately when a trial ends and deletes all data and settings after 7 days if the account is not subscribed. If a customer initiates migration scoping after the trial window, the source data may already be permanently gone. We ask for trial expiration dates during discovery and prioritize migrations for accounts approaching expiry to prevent data loss before scoping completes.

  • Onpipeline Invoices have no Nutshell equivalent on Sales Suite

    Onpipeline's integrated invoice generator produces invoices with payment status, line items, and settlement records. Nutshell's Sales Suite (Foundation through Enterprise) does not include native invoice generation; it offers Quotes with e-signature as the closest sales document. We migrate Invoice headers and line items as archived records in a custom Nutshell object or as Quote records flagged as invoiced, but the customer should plan to use a separate billing integration (such as QuickBooks, FreshBooks, or Xero) for post-migration invoicing.

  • Product inventory levels are informational only in Nutshell

    Onpipeline's Product catalog includes stock quantity tied directly to deals, with inventory alerts and deduction on sale. Nutshell Products store price and SKU but do not enforce live inventory counts or deduction on deal close. We preserve the Onpipeline stock quantity as a custom field on Nutshell Product for reference, but the customer must configure a separate inventory tracking workflow if they sell physical goods and rely on real-time stock visibility.

Migration approach

Six steps for a successful Onpipeline to Nutshell data migration

  1. Discovery and plan assessment

    We audit the Onpipeline account across all objects: People count, Company count, Deal count and pipeline structure, Quote volume, Invoice volume, Product catalog size, and Activity history volume. We pair this with a Nutshell plan assessment: Foundation ($13/user) covers basic CRM and single pipeline; Pro ($42/user) is required for multiple pipelines, automation, and email sequences; Enterprise ($79/user) unlocks API access if the customer needs custom integrations post-migration. The discovery output is a written scope and a Nutshell plan recommendation.

  2. Schema design and custom field provisioning

    We design the Nutshell schema to receive the Onpipeline data. This includes creating custom fields on People, Companies, and Opportunities (using Nutshell's native custom field UI or API for bulk creation), configuring pipeline stages and probabilities to match Onpipeline's pipeline setup, and defining any custom Quote fields needed to carry Onpipeline invoice metadata. Custom fields are provisioned in the Nutshell target account before any data import begins.

  3. Owner reconciliation and user provisioning

    We extract every distinct Onpipeline User referenced on Deals, Activities, and Quotes and match by email against the Nutshell destination account's User table. Owners without a matching Nutshell User go to a reconciliation queue. The customer's admin provisions any missing Users (active or inactive depending on whether the original Onpipeline user is still active) before record migration begins. This step is required because OwnerId references must be satisfied on Deals and Activities.

  4. Sandbox migration and reconciliation

    We run a full migration into a Nutshell test account or sandbox environment using a representative data sample. The customer's RevOps lead validates record counts (People in, Accounts in, Opportunities in, Activities in), spot-checks 20-30 random records against the Onpipeline source, and confirms Quote line item integrity before production migration begins. Any mapping corrections are made here.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (from Onpipeline Companies), People (with AccountId resolved), Opportunities (with OwnerId and stage resolved), Products (with inventory fields as custom numeric fields), Quotes (with line items referencing Product IDs), Activities (Events and Notes linked to parent records), and Invoices (as archived Quote records or a custom object). Each phase emits a row-count reconciliation report before the next phase begins.

  6. Cutover, validation, and automation inventory handoff

    We freeze Onpipeline write access during cutover, run a final delta migration of records modified during the migration window, then enable Nutshell as the system of record. We deliver a written inventory of Onpipeline Workflows, automations, and invoice templates that require manual rebuild in Nutshell. We do not rebuild Onpipeline automations as Nutshell automation rules inside the migration scope; that is a separate engagement or an internal admin task.

Platform deep dives

Context on both ends of the pair

Onpipeline logo

Onpipeline

Source

Strengths

  • Per-user flat-rate pricing with no per-contact or per-deal fees
  • Integrated quote, invoice, and e-signature workflow within the CRM
  • Product inventory management tied directly to the sales pipeline
  • API available on all plans with developer documentation and tools
  • Multilingual UI supporting Spanish, Portuguese, French, and Italian

Weaknesses

  • Limited advanced automation and workflow builder
  • Analytics and reporting less customizable than enterprise CRMs
  • Fewer native integrations than HubSpot or Salesforce
  • Multi-entity and multi-currency support is minimal
  • Calendar is user-scoped, limiting team-wide calendar visibility without team-leader roles
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 Onpipeline 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

    Onpipeline: Not publicly documented in the available developer docs.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your Onpipeline 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 three and five weeks for accounts under 10,000 People, 2,000 Deals, and a straightforward pipeline structure with no complex custom fields. Migrations with Quote line items, multi-pipeline Deal structures, large activity histories, or Products with inventory tracking move to six to ten weeks because of line-item resolution, inventory field mapping, and Onpipeline API pagination work.

Adjacent paths

Related migrations to explore

Ready when you are

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