CRM migration
Field-level mapping, validation, and rollback between Jubilee and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Jubilee
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Jubilee and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Jubilee CRM and Nutshell CRM share a core object model — people, companies, and deals — but they diverge in how they structure lifecycle and pipeline data. Jubilee stores contacts and leads in a unified People object with a 'type' flag, while Nutshell separates People and Leads into distinct objects. Jubilee deal records carry a stage name and probability percentage; Nutshell deal records carry a stage name and weighted monetary amount tied to that stage. Custom properties in Jubilee migrate as Nutshell custom fields, but Nutshell custom fields must be pre-created in the Settings > Data > Custom Fields section before data lands. We sequence the migration so company records insert first (foreign key for person records), then people split by Jubilee type flag into Nutshell People or Leads, then deals attach to their respective company and person records. Activity history (calls, emails, meetings, notes) migrates as Tasks against the parent record with original timestamps preserved. Our migration uses scoped read access on Jubilee — your team keeps working throughout — with a 24–48 hour delta-pickup window at cutover to capture in-flight changes. Workflows, automations, integrations, and billing configurations do not migrate and must be rebuilt in Nutshell.
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 Jubilee 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.
Jubilee
Person (type = contact)
Nutshell
Person
1:1Jubilee contact records map 1:1 to Nutshell Person records. The person name, email, phone, job title, and address fields transfer directly. Jubilee company association (stored as a company_id on the person) resolves to a Nutshell AccountId lookup after accounts migrate.
Jubilee
Person (type = lead)
Nutshell
Lead
1:1Jubilee leads split into Nutshell Leads. Nutshell Lead records have a separate list view, status pipeline, and assignment workflow from Person records. Lead status values (new, contacted, qualified) are mapped from Jubilee's lead status field using a value-by-value mapping table provided during scoping.
Jubilee
Company
Nutshell
Account
1:1Jubilee Company records map to Nutshell Account records. Company name, domain/website, industry, employee count, and annual revenue migrate directly. Parent-company relationships in Jubilee map to the Nutshell Account parent field; circular references are flagged before migration commits. Address fields including street, city, state, postal code, and country transfer directly to maintain complete company profiles.
Jubilee
Deal
Nutshell
Deal
1:1Jubilee deal name, amount, stage, expected close date, and owner migrate to Nutshell Deal records. Jubilee stores deal probability as a field; Nutshell calculates weighted pipeline value from stage-level weighting. We preserve Jubilee's probability as a custom field (Legacy_Probability__c) for reporting continuity.
Jubilee
Pipeline
Nutshell
Pipeline
1:1Jubilee's pipeline configuration maps to Nutshell Pipelines — each Jubilee pipeline becomes one Nutshell pipeline. Stage names are mapped value-by-value from Jubilee stage names to Nutshell stage names. Nutshell allows multiple pipelines; Jubilee's pipeline assignments per deal are preserved as a custom field (Legacy_Pipeline__c) on the deal.
Jubilee
Custom Property (Person)
Nutshell
Custom Field (Person)
1:1Jubilee custom properties on Person records require pre-created Nutshell custom fields on the Person object. FlitStack delivers a custom-field creation plan before migration runs. Text, number, date, and pick-list property types map to equivalent Nutshell field types; multi-select pick-lists may require a custom approach.
Jubilee
Custom Property (Company)
Nutshell
Custom Field (Account)
1:1Jubilee company custom properties migrate to Nutshell Account custom fields. The same pre-creation requirement applies — fields must exist in Nutshell before data inserts. Complex Jubilee field types (e.g., formula fields) are evaluated individually; the result value migrates as a text or number field in Nutshell.
Jubilee
Custom Property (Deal)
Nutshell
Custom Field (Deal)
1:1Jubilee deal-level custom properties migrate to Nutshell Deal custom fields. Standard Nutshell Deal fields (name, amount, stage, responsible, expected close) are mapped first; remaining properties are added as custom fields per the creation plan. All deal custom fields must be pre-created in Nutshell before migration inserts begin to ensure proper data typing and field availability on the deal object.
Jubilee
Activity (call, email, meeting, note)
Nutshell
Task
1:1Jubilee activity records (calls, emails, meetings, notes) map to Nutshell Tasks. The task subject carries the activity type prefix (e.g., 'Call — Q4 follow-up'), original timestamps are preserved on the task, and the task is linked to the parent Person, Lead, or Deal record. Note bodies migrate as Task descriptions.
Jubilee
Owner / User
Nutshell
User
1:1Jubilee owner assignments resolve by email match against Nutshell users. Unmatched owners are flagged before migration — the team either creates Nutshell user accounts first or assigns records to a designated fallback user. No record migrates without a valid Nutshell owner.
Jubilee
Workflow / Automation
Nutshell
No equivalent
1:1Jubilee workflow rules, automation triggers, and task-assignment rules do not have a direct Nutshell equivalent. These must be rebuilt in Nutshell using Nutshell's built-in automation features (email sequences, stage-triggered tasks) after migration. FlitStack can export Jubilee workflow definitions as a reference document for your team.
Jubilee
Integration / Connected App
Nutshell
No equivalent
1:1Jubilee integrations with legal tools, document management systems, and court filing services have no direct Nutshell counterpart. Nutshell's native integrations (QuickBooks, Zoom, Google Workspace, Shopify) serve a different use case. Your team will need to rebuild or replace integrations post-migration.
| Jubilee | Nutshell | Compatibility | |
|---|---|---|---|
| Person (type = contact) | Person1:1 | Fully supported | |
| Person (type = lead) | Lead1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline | Pipeline1:1 | Fully supported | |
| Custom Property (Person) | Custom Field (Person)1:1 | Fully supported | |
| Custom Property (Company) | Custom Field (Account)1:1 | Fully supported | |
| Custom Property (Deal) | Custom Field (Deal)1:1 | Fully supported | |
| Activity (call, email, meeting, note) | Task1:1 | Fully supported | |
| Owner / User | User1:1 | Fully supported | |
| Workflow / Automation | No equivalent1:1 | Fully supported | |
| Integration / Connected App | No equivalent1: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.
Jubilee gotchas
Desktop edition stores documents in local file paths
Trust account balance snapshot may not reflect pending transactions
Chapter-specific form versions are not auto-upgraded on import
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
Audit Jubilee data and build the custom-field creation plan
FlitStack reads your Jubilee data via scoped API access to inventory all object types, record counts, custom properties, pipeline configurations, and activity volumes. We identify any data-quality issues (duplicate records, missing required fields, orphaned relationships) and surface them before migration planning begins. The custom-field creation plan is generated from this audit — it lists every Jubilee custom property that needs a corresponding Nutshell custom field, the recommended field type for each, and which Nutshell object (Person, Account, Deal) it belongs on. Your team creates these fields in Nutshell before the test migration runs.
Create a mapping specification and validate with a sample migration
With Nutshell custom fields in place, FlitStack applies the object and field mapping specification — the contact-lead split logic, company-account resolution, deal stage value mapping, owner email matching, and activity parent resolution. A representative sample (typically 100–300 records across people, companies, deals, and activities) migrates first. We generate a field-level diff comparing source Jubilee values to the resulting Nutshell records so your team can verify that probability values, stage names, and custom property data landed correctly before the full run.
Migrate accounts and contacts in dependency order
FlitStack sequences the migration to respect Nutshell's foreign-key requirements. Account records insert first (Jubilee companies). Person and Lead records insert second — split by the Jubilee type flag, each attached to the migrated Account record via the account_id lookup. Deal records insert third, each linked to their respective Account and primary Contact. Activity records (calls, emails, meetings, notes) insert last, linked to their parent Person, Lead, or Deal record. Owner resolution by email match runs throughout so every record has a Nutshell user assigned at insert time. Unresolved owners are logged and surfaced to your team for decision before the full migration commits.
Run delta-pickup and deliver the reconciliation audit
After the full migration completes, FlitStack runs a delta-pickup window — typically 24 hours, extendable to 48 — to capture any records modified or created in Jubilee during the cutover period. An audit log records every insert, update, and link operation. Your team receives a reconciliation report comparing Jubilee record counts and key field totals (total deal amount, total person count, total activity count) against what landed in Nutshell. If reconciliation fails — record counts diverge, required fields are blank, or duplicate records appear — one-click rollback reverts the Nutshell data so the migration can be re-run with corrected mapping.
Hand off workflow definitions and rebuild reference documentation
FlitStack exports your Jubilee workflow definitions as a structured reference document so your Nutshell admin can rebuild automation logic in Nutshell's built-in sequence and task-automation tools. We document which Jubilee automations had what trigger conditions, what actions they performed, and what objects they applied to — giving your admin a rebuild checklist rather than a blank slate. Email templates, integration credentials, and user-role configurations are outside FlitStack's migration scope and are noted explicitly in the handoff package.
Platform deep dives
Jubilee
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 Jubilee 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
Jubilee: Not publicly documented.
Data volume sensitivity
Jubilee 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 Jubilee to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Jubilee 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 Jubilee
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.