CRM migration

Migrate from Jubilee to Nutshell

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

Jubilee logo

Jubilee

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between Jubilee and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Jubilee logo

Jubilee

What's pushing teams away

  • Firms that expand beyond bankruptcy into family law, civil litigation, or other practice areas find JubileePRO's feature set too narrow and migrate to general legal CRMs.
  • The desktop edition lacks real-time multi-user sync, causing collaboration friction for firms with remote or hybrid staff.
  • Reporting and analytics are limited compared to platforms with dedicated business intelligence tools, making firm health metrics harder to extract.

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

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)

maps to

Nutshell

Person

1:1
Fully supported

Jubilee 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)

maps to

Nutshell

Lead

1:1
Fully supported

Jubilee 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

maps to

Nutshell

Account

1:1
Fully supported

Jubilee 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

maps to

Nutshell

Deal

1:1
Fully supported

Jubilee 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

maps to

Nutshell

Pipeline

1:1
Fully supported

Jubilee'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)

maps to

Nutshell

Custom Field (Person)

1:1
Fully supported

Jubilee 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)

maps to

Nutshell

Custom Field (Account)

1:1
Fully supported

Jubilee 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)

maps to

Nutshell

Custom Field (Deal)

1:1
Fully supported

Jubilee 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)

maps to

Nutshell

Task

1:1
Fully supported

Jubilee 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

maps to

Nutshell

User

1:1
Fully supported

Jubilee 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

maps to

Nutshell

No equivalent

1:1
Fully supported

Jubilee 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

maps to

Nutshell

No equivalent

1:1
Fully supported

Jubilee 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.

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.

Jubilee logo

Jubilee gotchas

High

Desktop edition stores documents in local file paths

Medium

Trust account balance snapshot may not reflect pending transactions

Medium

Chapter-specific form versions are not auto-upgraded on import

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

  • Contact-lead split creates two record types in Nutshell that Jubilee stores as one

    Jubilee uses a single People object with a 'type' property to distinguish contacts from leads. Nutshell separates these into distinct object types — People and Leads — each with its own list view, fields, and workflow triggers. During migration, FlitStack routes Jubilee 'type=contact' records to Nutshell People and Jubilee 'type=lead' records to Nutshell Leads. The challenge is that any Jubilee person who later converts from lead to contact in Jubilee will exist as two separate records — the original lead (retained for history) and the new contact — after migration. Teams should review the Jubilee person type distribution during scoping so the split logic handles edge cases correctly.

  • Nutshell custom fields must be pre-created before data inserts

    Unlike some CRM platforms that auto-create custom fields during import, Nutshell requires custom fields to be explicitly created in Settings > Data > Custom Fields before any data is written to them. FlitStack delivers a custom-field creation plan as part of the migration package — it lists each Jubilee custom property, the recommended Nutshell field type, and the object it should be attached to. If your team creates fields differently than the plan (e.g., using a text field instead of the recommended pick-list), the migration mapping must be updated to match. This is the most common source of migration delays for custom-property-heavy Jubilee accounts.

  • Jubilee deal probability migrates as a reference field, not a calculated one

    Jubilee stores deal probability as an explicit numeric field on each deal record. Nutshell does not have a native probability field on deals — weighted pipeline value is calculated from the deal amount multiplied by the stage's probability weight, not stored per-deal. If your team uses Jubilee deal probability in custom reports or dashboards, that data exists only as a raw number in Jubilee and must be preserved manually. FlitStack migrates the probability value to a custom field (Legacy_Probability__c) on the Nutshell deal so existing reports can reference it, but Nutshell will not use it in its native weighted pipeline calculation.

  • Activity history linking depends on person migration completing first

    Jubilee activity records (calls, emails, meetings, notes) reference a person record by ID. Nutshell Tasks must reference a Nutshell record (Person, Lead, or Deal) after migration. Because person and lead records migrate before activities, FlitStack resolves the Jubilee person ID to the new Nutshell record ID during the activity migration phase. If a Jubilee person record was deleted before migration, its activities are linked to a 'Migrated Orphan' placeholder record in Nutshell so no activity data is silently dropped. This resolution step adds processing time for activity-heavy accounts.

  • Jubilee integrations to legal and court-filing tools have no Nutshell equivalent

    Jubilee's integration ecosystem is oriented toward bankruptcy practice management — court filing systems, document management platforms, and legal calendaring tools. Nutshell's native integrations cover sales and marketing tools (QuickBooks, Zoom, Google Workspace, Shopify, Calendly, Mailchimp). There is no equivalent for legal-specific integrations in Nutshell. Teams that rely on Jubilee's connected legal tools will need to replace those workflows with Nutshell-compatible alternatives or manual processes post-migration. FlitStack documents each active Jubilee integration during scoping so the impact is clear before migration begins.

Migration approach

Six steps for a successful Jubilee to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Jubilee logo

Jubilee

Source

Strengths

  • Pay-per-case pricing option lets occasional or part-time bankruptcy attorneys avoid monthly subscriptions for low case volume.
  • Covers all consumer/business chapters (7, 11, 12, 13) per LegalPRO Systems' vendor description.
  • Cloud-based platform reduces local infrastructure requirements for small firms per Capterra listing.
  • Strong review aggregations describe tech support as 'top notched' per multiple reviewer comments on Capterra and ITQlick.
  • Frequent updates to local court rules and form versions reduce manual compliance burden per existing whyPeopleChoose content.

Weaknesses

  • Narrow vertical focus on bankruptcy only — firms with mixed practice areas outgrow it quickly.
  • Desktop edition lacks real-time multi-user sync, complicating hybrid/remote staff workflows.
  • Reporting and analytics are basic relative to general legal practice management platforms.
  • Per-case fees on the pay-per-case plan add up for firms processing high case volume; subscription plan becomes more cost-effective above a break-even threshold.
  • No public API documentation found, complicating integrations beyond the bundled feature set.
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 Jubilee 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

    Jubilee: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your Jubilee to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Jubilee-to-Nutshell migrations complete in 48–72 hours of clock time for accounts with fewer than 25,000 total records. Larger datasets with 250,000+ records or extensive custom property configurations extend to 5–10 days. The longest planning step is custom-field creation in Nutshell — your team should complete that before the test migration runs. The delta-pickup window adds 24–48 hours after the full migration run but does not block your team from working in Jubilee during that time.

Adjacent paths

Related migrations to explore

Ready when you are

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