CRM migration

Migrate from Smokeball to Nutshell

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

Smokeball logo

Smokeball

Source

Nutshell

Destination

Nutshell logo

Compatibility

92%

11 of 12

objects map 1:1 between Smokeball and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Smokeball and Nutshell serve fundamentally different workflows — Smokeball organizes around matters, billing, and legal document automation, while Nutshell organizes around accounts, deals, and sales pipelines. This migration carries contacts, companies, activities, and any deal-like records from Smokeball into Nutshell's account-person-lead-deal model. Custom fields migrate as Nutshell custom fields on the corresponding record type. Workflows, document templates, billing data, and trust accounting records do not have equivalents in Nutshell and must be rebuilt or left behind. FlitStack AI uses Nutshell's JSON-RPC API with Basic auth (API token) to write records in dependency order — accounts first, then people, then leads and deals, then activities — preserving original create dates and owner assignments via email matching. A delta-pickup window captures any records modified during the cutover window to ensure Nutshell reflects the final state of Smokeball at go-live. The migration process requires careful sequencing because Nutshell enforces referential integrity — accounts must exist before people can link to them, and activities require parent records to exist first. Custom fields must be created via Nutshell's custom fields API before migration data can populate them, adding a preparation step for any non-standard fields.

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

Smokeball logo

Smokeball

What's pushing teams away

  • Billing issues appear in 22+ G2 reviews, with users reporting disorganization in invoicing, problems with payment routing, and hard/soft cost misalignments between Smokeball and integrated accounting software like Xero or MYOB.
  • Missing features frustrate users, particularly poor search functionality across documents and the absence of auto-save, which leads to lost work and wasted time re-entering data.
  • Software bugs cause real operational pain—duplicate documents appearing in containers, slow performance under load, and files failing to load after upload, each cited 14+ times on review platforms.
  • Collaboration limitations and cumbersome document import processes are cited as missing features, making it difficult for multi-attorney firms to share and organize files efficiently.
  • Integration issues with third-party software, particularly after major updates, cause connectivity failures with Outlook, LawPay, and accounting tools that disrupt billing workflows.

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

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

Smokeball

Contact

maps to

Nutshell

Person

1:1
Fully supported

Smokeball contacts map directly to Nutshell people. Each person record carries name, email, phone, address, and salutation fields. Primary company association maps to the Nutshell account lookup on the person record. Contacts without a linked company receive a default 'Unassigned' account in Nutshell.

Smokeball

Contact (staff member)

maps to

Nutshell

User

1:1
Fully supported

Smokeball staff records include name, email, status, and salutation. FlitStack resolves each staff email against Nutshell users to assign OwnerId on migrated records. Inactive Smokeball staff become inactive Nutshell users or are omitted from the user list — this is a configuration decision made before migration runs.

Smokeball

Company

maps to

Nutshell

Account

1:1
Fully supported

Smokeball companies map 1:1 to Nutshell accounts. Company name, domain/website, industry, phone, and address fields migrate directly. Smokeball parent-company hierarchies map to Nutshell's parent-account field. Multi-contact companies in Smokeball (N:N relationships) land as a single Nutshell account with all linked people associated.

Smokeball

Matter

maps to

Nutshell

Custom Field + Account

1:1
Fully supported

Smokeball matters have no direct Nutshell equivalent — Nutshell has no concept of legal cases or matter types. We preserve matter description, matter number, matter type, and key dates as custom fields on the linked Nutshell account for reference. Matter-specific data like parties, opposing counsel, and court details are preserved in a long-text custom field.

Smokeball

Matter Party / Client

maps to

Nutshell

Person (linked to Account)

many:1
Fully supported

Smokeball matter parties (Initiating Party, Responding Party, Client, Other Side) are merged into the Nutshell person record as a custom field (Party_Role__c) attached to the account representing the matter. Each party role is stored as a delimited value so firms can reconstruct party structure from the custom field after migration.

Smokeball

Activity (Task / Email / Note)

maps to

Nutshell

Activity

1:1
Fully supported

Smokeball activity records — tasks, document work, memos, emails — migrate as Nutshell activities with original timestamps and owners preserved. Activity type maps to Nutshell's activity kind field. Each activity links to its parent person or account record. Bulk activity imports run after persons and accounts are established.

Smokeball

Time Entry

maps to

Nutshell

Note (on Account or Person)

1:1
Fully supported

Smokeball time entries map to Nutshell notes because Nutshell has no time-tracking module. Each time entry is written as a note with type='Time Entry', the duration in the note body, and a reference to the linked matter/account. Billable/non-billable flag is preserved as a custom field on the note. Time-entry data must be reconciled against separate billing software.

Smokeball

Document / File

maps to

Nutshell

File (via attachment to Person/Account)

1:1
Fully supported

Smokeball documents attach to matters and contacts. FlitStack re-uploads document files to Nutshell, attaching each to the corresponding person or account record. File names and original upload dates are preserved in the Nutshell file metadata. Large document volumes increase migration time due to file-reupload overhead.

Smokeball

Custom Field (on Contact/Company/Matter)

maps to

Nutshell

Custom Field (on Person/Account/Lead)

1:1
Fully supported

Smokeball custom fields on contacts, companies, and matters become Nutshell custom fields on the corresponding record type (Person, Account, or Lead). Nutshell supports custom field types including text, number, date, dropdown, and checkbox. FlitStack creates the custom fields in Nutshell via its custom fields API before writing the data. Field types are mapped intelligently — a Smokeball dropdown becomes a Nutshell dropdown with the same options.

Smokeball

Workflow

maps to

Nutshell

Automation (Nutshell built-in + rebuild required)

1:1
Fully supported

Smokeball workflows — automated task series applied to matters — have no Nutshell equivalent. Nutshell offers personal email sequences and lead assignment rules, but not multi-step matter-based workflow automation. FlitStack exports Smokeball workflow definitions as a JSON reference file that your team can use to rebuild logic in Nutshell's automation tools or a third-party integration platform.

Smokeball

Billing / Trust Accounting

maps to

Nutshell

No equivalent

1:1
Fully supported

Smokeball billing records, trust accounting entries, invoices, and disbursement data do not map to Nutshell because Nutshell has no billing or accounting module. Financial records must be exported from Smokeball and migrated to dedicated accounting software (QuickBooks, Xero, LawPay). FlitStack can export billing data as CSV for import into your accounting platform of choice.

Smokeball

Tag

maps to

Nutshell

Tag

1:1
Fully supported

Smokeball contact and company tags migrate directly to Nutshell tags on the corresponding person and account records. Tags are preserved as-is — no transformation required. Tags used for segmentation in Smokeball can continue to be used for filtering in Nutshell's list view.

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.

Smokeball logo

Smokeball gotchas

High

Document upload may not finish before Go Live

High

Data entry must halt during final LIVE migration cutover

Medium

Duplicate contacts are not detected during import

Medium

Closed and archived matters migrate after Go Live

Medium

Lower pricing tiers strip PDF functionality and auto time

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

  • Matter-centric data has no Nutshell equivalent and must be preserved as custom fields

    Smokeball organizes all firm data around Matters — legal cases that link clients, opposing parties, documents, time entries, and billing. Nutshell has no matter or case concept; its data model is Account → Person → Deal. FlitStack maps matter metadata (matter number, type, description, responsible attorney) to custom fields on the linked Nutshell account, but the structural relationship between parties and matter documents cannot replicate Smokeball's matter graph. Firms should audit which Smokeball reports and processes rely on matter-centric filtering and plan for those to be rebuilt in Nutshell or via exported CSV.

  • Smokeball billing and trust accounting data cannot migrate to Nutshell

    Smokeball's trust accounting, disbursements, hard costs, soft costs, and LawPay integration are core to its value for law firms. Nutshell has no accounting module whatsoever — invoices, payments, trust balances, and financial records must remain in Smokeball or be exported to separate accounting software. FlitStack can export billing data as CSV, but Nutshell cannot receive financial records in any native object. Firms relying on Smokeball billing should treat the migration as a data-export project for billing history and a separate migration to accounting software.

  • Smokeball API requires partner enrollment — migration tooling access is gated

    The Smokeball API is not self-serve — integrating partners must complete formal enrollment via the Smokeball marketplace application form and receive a client_id and client_secret. Without partner enrollment, API access is not available, and data extraction must rely on Smokeball's Jumpstart CSV export tool. Firms that do not have partner access should coordinate with Smokeball support or use the CSV export pathway, which limits what data types can be extracted. Nutshell's API, by contrast, is accessible with a standard account API token from the integrations settings page.

  • Document files re-upload to Nutshell's storage — large volumes extend migration time

    Smokeball documents attached to matters and contacts must be downloaded and re-uploaded to Nutshell's file storage. Nutshell attaches files to person or account records, with file metadata (name, size, upload date) preserved. Document volumes exceeding 10,000 files significantly extend migration clock time because each file requires a separate upload operation via Nutshell's API. Firms with large document repositories should expect the delta-pickup window to extend accordingly, and should verify that Nutshell's file size limits (default 25MB per file) accommodate the largest documents before migration runs.

Migration approach

Six steps for a successful Smokeball to Nutshell data migration

  1. Enumerate Smokeball data scope and verify API or CSV export access

    FlitStack reviews your Smokeball account to count contacts, companies, matters, activities, documents, and custom fields. If Smokeball partner enrollment is complete, we extract data via the REST API using OAuth 2.0 with the token bucket algorithm (5 req/sec, 5 concurrent burst). If API access is unavailable, we use the Jumpstart CSV export tool as the extraction pathway, which limits document export to manual re-upload. The scope document identifies which Smokeball objects have Nutshell equivalents and which require custom field or no-equivalent handling.

  2. Create Nutshell custom fields before writing data

    Nutshell custom fields must exist before records can populate them. FlitStack creates custom fields on Person, Account, and Lead record types via Nutshell's custom fields API — text, number, date, dropdown, and checkbox types are mapped from Smokeball field types. Matter-metadata fields (Matter_Number__c, Matter_Type__c, Matter_Status__c) are created on the Account object. Staff-to-user resolution is prepared: each Smokeball staff email is matched against Nutshell users by email, with unmatched staff flagged for fallback owner assignment.

  3. Migrate in dependency order: Accounts → People → Leads → Activities

    Nutshell requires accounts to exist before people can link to them (via the account_id field), and activities require people or accounts to exist first. FlitStack sequences the migration accordingly: (1) Companies → Accounts, (2) Contacts → People (with account_id resolved), (3) Lead records split from contacts where applicable, (4) Activities attached to the correct person or account. Owner assignment is resolved by email match at this stage. Custom field values are written alongside standard fields in the same API call.

  4. Re-upload documents and attach to linked Nutshell records

    Smokeball documents are downloaded, organized by their linked contact or matter, and re-uploaded to Nutshell's file storage. Each file is attached to the corresponding Nutshell person or account record. For matters, documents attach to the account record representing the matter's primary client. File metadata (original filename, upload date, file size) is preserved in Nutshell's file record. Large document sets run in parallel batches with retry logic to handle transient upload failures.

  5. Run sample migration with field-level diff, then cut over with delta pickup

    A representative slice (typically 100–500 records spanning contacts, companies, matters, and activities) migrates first. FlitStack generates a field-level diff comparing source values against Nutshell field values so you can verify custom field mapping, owner resolution, and activity attachment. After sample sign-off, the full migration runs. A delta-pickup window (typically 24–48 hours) captures any records modified in Smokeball during the cutover. Audit log records every operation; one-click rollback is available if reconciliation fails.

Platform deep dives

Context on both ends of the pair

Smokeball logo

Smokeball

Source

Strengths

  • Automatic time tracking via AutoTime captures billable activity without manual entry, directly improving firm collection rates.
  • Comprehensive document automation with Smokeball Toolbar in Microsoft Word enables rapid generation of standardized legal precedents and letters.
  • Built-in trust accounting and reporting satisfy law firm regulatory requirements out of the box.
  • Exceptional customer support with dedicated Client Success Managers and UK-based telephone support keeps small firms operational.
  • AI assistant Archie and Outlook integration reduce context switching for attorneys managing client communications.

Weaknesses

  • Billing issues appear frequently in reviews, with payment routing and cost allocation problems requiring manual intervention.
  • Search functionality across documents and matters is a known pain point, making it difficult to locate historical files efficiently.
  • Auto-save is not available, risking data loss if attorneys forget to save manually during document work.
  • Collaboration features are limited, making Smokeball less suitable for large multi-office or multi-attorney firms requiring real-time co-authoring.
  • Price increases have been reported by existing customers, and lower tiers strip critical features like PDF functionality and automatic time tracking.
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. 3 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 Smokeball and Nutshell.

  • Object compatibility

    B

    3 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

    Smokeball: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Smokeball-to-Nutshell migrations complete in 48–72 hours of clock time for under 25,000 records. Larger setups with 100,000+ records, heavy custom-field usage, or large document volumes extend to 7–10 days. The longest single step is usually document re-upload — every file is a separate API operation — followed by the delta-pickup window at cutover. Matter-metadata field mapping and staff-to-user resolution are planning steps that run before any data moves.

Adjacent paths

Related migrations to explore

Ready when you are

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