CRM migration
Field-level mapping, validation, and rollback between PlanPlus Online and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
PlanPlus Online
Source
Nutshell
Destination
Compatibility
7 of 8
objects map 1:1 between PlanPlus Online and Nutshell.
Complexity
BStandard
Timeline
3-5 weeks
Overview
PlanPlus Online does not publish a REST API, so all migration data comes from manual CSV exports from the web interface and data dumps from its sync connectors. This shifts the migration timeline earlier—the CSV assembly phase alone runs two to three weeks before any records enter Nutshell. We map PlanPlus Online Contacts and Companies to Nutshell People and Accounts, Deals to Nutshell Deals, and preserve Franklin Covey priority quadrants as a custom property. Calendar events migrate as Nutshell Activities with full timestamp and attendee data where available. We do not migrate PlanPlus Online workflows, automations, or sync connection configurations as these do not have equivalents in Nutshell and are documented for the customer's admin to rebuild manually.
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 PlanPlus Online 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.
PlanPlus Online
Contact
Nutshell
Person
1:1PlanPlus Online Contacts map 1:1 to Nutshell Person records. All standard fields including name, email address, phone number, title, and mailing address transfer directly. We resolve the owner assignment from PlanPlus Online by matching the owner email against Nutshell Users and populate the Person's ownerId. If PlanPlus Online uses custom contact properties, we map them to Nutshell custom fields with the custom_ prefix convention. Links between PlanPlus Online Contacts and their associated Company records resolve to Nutshell Account lookups on Person during the Company import phase.
PlanPlus Online
Company
Nutshell
Account
1:1PlanPlus Online Company records map 1:1 to Nutshell Account records. We preserve the company name, industry classification, employee count, and website URL. The PlanPlus Online domain field becomes the Account's website. The dedupe key during Nutshell import is the company name and domain. Account records must import before Contact records so that AccountId resolves on Person insert. If no matching PlanPlus Online Company exists for a Contact, the Person is created as a standalone record without an Account link.
PlanPlus Online
Deal
Nutshell
Deal
1:1PlanPlus Online deal records from the External Opportunity Portal map to Nutshell Deal records. We preserve deal name, monetary value, close date, and stage assignment. PlanPlus Online stage names and probabilities map to Nutshell's configurable Deal stages during schema setup. If PlanPlus Online uses a stage structure incompatible with Nutshell's ten-stage limit, we collapse or merge stages and document the mapping in the reconciliation report. Closed-Lost and Closed-Won reasons from PlanPlus Online custom fields migrate to text fields on the Nutshell Deal.
PlanPlus Online
Task
Nutshell
Task
1:1PlanPlus Online Tasks map 1:1 to Nutshell Task records with title, due date, priority, and completion status preserved. Subtasks under a parent PlanPlus Online task migrate as child Task records under the parent Nutshell Task. Franklin Covey priority quadrants (urgent/important matrix) from PlanPlus Online export as a custom property on the Nutshell Task, stored as a text or custom picklist field depending on the customer's scoping decision. Task assignment resolves the owner from PlanPlus Online by email match against Nutshell Users.
PlanPlus Online
Calendar Event
Nutshell
Activity
1:1PlanPlus Online calendar events including appointments and all-day events map to Nutshell Activity records. We preserve the event title, start and end timestamps, location, and linked attendee list. Nutshell creates an Activity record for each calendar event; attendee information transfers to the Activity's participants field where the attendee email matches a Nutshell Person or User. If attendee matching is ambiguous, we attach the raw attendee list as a text note on the Activity record. All-day events from PlanPlus Online set the Nutshell Activity as an all-day entry.
PlanPlus Online
Project
Nutshell
Note
1:1PlanPlus Online Projects with milestones and task breakdowns export with status, milestone dates, and task breakdowns. Nutshell does not have a native Project object, so we create a Note on the primary associated Person or Account for each project, capturing the project name, status, and key dates in structured text. Project Summary Reports published as PlanPlus Online webpages export as static HTML and attach as a Note attachment for reference. Hierarchical project dependencies do not carry over structurally; we document them in the project note for the customer's admin to rebuild as linked Notes or Opportunities if needed.
PlanPlus Online
Custom Field
Nutshell
Custom Field
lossyCustom fields created in PlanPlus Online export as flat key-value pairs attached to the parent object. We map each to an equivalent Nutshell custom field during schema setup, using the custom_ field naming convention the Nutshell API requires. Fields with no direct Nutshell equivalent are flagged in the pre-migration review for the customer to decide whether to create a custom field, store the value as text, or drop the field. We validate field data types during the sandbox migration to catch format mismatches before production.
PlanPlus Online
Sync Connection
Nutshell
Sync Connection
1:1Sync connections to Google Calendar, Microsoft 365, and Outlook established within PlanPlus Online are authentication configurations that do not export or transfer to Nutshell. These connections are specific to the PlanPlus Online sync infrastructure and have no equivalent mechanism in Nutshell's API. We document which external systems were connected and provide a checklist for the customer to re-establish OAuth connections in Nutshell post-migration. This documentation is included in the handoff package.
| PlanPlus Online | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Calendar Event | Activity1:1 | Fully supported | |
| Project | Note1:1 | Fully supported | |
| Custom Field | Custom Fieldlossy | Fully supported | |
| Sync Connection | Sync Connection1: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.
PlanPlus Online gotchas
No public API means no automated migration pipeline
Data export blocked for delinquent accounts
Planner Edition lacks sync and export infrastructure
Auto-renewal with annual price adjustment
Time zone settings must be correct before sync 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, export planning, and account verification
We audit the source PlanPlus Online account for edition tier, record volumes by object type, custom field definitions, and sync connector configurations. We verify the account is in good standing with no overdue invoices—PlanPlus Online restricts data export for delinquent accounts. We confirm whether the account uses Business Edition with the External Opportunity Portal for deal tracking or Professional Edition without it, as this affects the deal migration scope. We map every PlanPlus Online field to a Nutshell field or custom field and present the mapping to the customer for sign-off before export begins.
CSV export assembly and pre-migration data validation
The customer performs the CSV export from PlanPlus Online's web interface under our written instructions, or we guide the export if the interface supports direct download. We assemble the export files into structured datasets per object type, validate field counts against the mapping, and flag any records with missing required fields before the migration window opens. This phase runs two to three weeks in parallel with Nutshell sandbox setup and typically requires the most manual effort from the customer's PlanPlus Online account administrator.
Nutshell sandbox testing and schema configuration
We configure the destination Nutshell account with the custom fields, deal stages, and any other schema elements defined in the mapping document. We run a sandbox migration using a subset of the exported data to verify field mapping accuracy, parent-child resolution for Account-Person and Person-Deal relationships, and that Nutshell API responses return the expected record structure. The customer reconciles sandbox results against the source PlanPlus Online data and signs off on the mapping before production migration begins.
Production migration in record dependency order
We run production migration in strict dependency order: Nutshell Users and Accounts (from PlanPlus Online Companies) first, then Person records with resolved AccountId links, then Deals with resolved PersonId and ownerId, then Tasks, then Calendar Activities. Each phase emits a row-count reconciliation report before the next phase begins. We handle Nutshell API rate-limit responses with exponential backoff and retry failed records up to three times before flagging them for manual review.
Cutover, final validation, and handoff
We perform a final delta export of any records modified in PlanPlus Online during the migration window, insert them into Nutshell, and enable Nutshell as the system of record. We deliver the migration summary report showing record counts by object, any records that could not migrate, and the workflow and automation inventory document. We support a three-day hypercare window to resolve any immediate post-cutover data issues. Post-migration admin support, Nutshell training, and automation rebuild are outside standard scope and can be scoped as separate engagements.
Platform deep dives
PlanPlus Online
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 PlanPlus Online 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
PlanPlus Online: Not publicly documented.
Data volume sensitivity
PlanPlus Online 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 PlanPlus Online to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your PlanPlus Online 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 PlanPlus Online
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.