CRM migration
Field-level mapping, validation, and rollback between Onpipeline and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Onpipeline
Source
Nutshell
Destination
Compatibility
6 of 8
objects map 1:1 between Onpipeline and Nutshell.
Complexity
BStandard
Timeline
3-5 weeks
Overview
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.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
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
Nutshell
Person or Lead
1:manyOnpipeline 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
Nutshell
Account
1:1Onpipeline 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
Nutshell
Opportunity
1:1Onpipeline 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
Nutshell
Stage
lossyEach 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
Nutshell
Activity
1:1Onpipeline 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
Nutshell
Product
1:1Onpipeline 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
Nutshell
Quote
1:1Onpipeline 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
Nutshell
User
1:1Onpipeline 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.
| Onpipeline | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person or Lead1:many | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Pipeline Stage | Stagelossy | Fully supported | |
| Activity / Events | Activity1:1 | Fully supported | |
| Product | Product1:1 | Fully supported | |
| Quote | Quote1:1 | Fully supported | |
| User / Owner | User1:1 | Fully supported |
Gotchas + challenges
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 gotchas
Trial account data deleted 7 days after expiry
Calendar is user-scoped, not team-wide by default
Recurring invoice automation gated to Advanced plan
Facebook Lead Ads import requires API or Zapier setup
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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.
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
Onpipeline
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Onpipeline and Nutshell.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Onpipeline: Not publicly documented in the available developer docs.
Data volume sensitivity
Onpipeline doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Onpipeline to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Onpipeline to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Onpipeline
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.