CRM migration

Migrate from Assembly Neos to Nutshell

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

Assembly Neos logo

Assembly Neos

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between Assembly Neos and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Assembly Neos stores data around matters, clients, medical records, and legal-specific properties that have no native equivalent in Nutshell's contact-and-deal model. FlitStack AI extracts Neos contacts, companies, notes, and custom field data via the Neos API and maps them to Nutshell People, Accounts, and custom fields. Legal-specific properties such as case type, lien status, provider tracking, and trust accounting flags are surfaced as Nutshell custom fields so your team can query them in reports. Workflows, document assembly templates, and case-type-specific automation logic cannot migrate — they must be rebuilt in Nutshell or replaced with Nutshell's sales sequences and automation rules. The migration runs against a scoped read grant on Neos while your team continues working, with a 24–48 hour delta pickup capturing changes during cutover. All original timestamps, author identities, and source IDs are preserved in custom fields to support audit trails and future reconciliation, including record creation dates and last-modified timestamps for complete historical visibility.

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

Assembly Neos logo

Assembly Neos

What's pushing teams away

  • Frequent software bugs and slow performance frustrate users, with multiple G2 reviews citing random freezing and document upload failures impacting daily workflows. Performance degrades noticeably with heavy workloads, especially when handling large case volumes or many concurrent users. The built-in accounting module is removed when migrating to Neos, forcing firms to adopt QuickBooks Online for all billing and disbursement tasks, which creates friction for firms expecting an all-in-one solution. A learning curve exists for advanced features like templates, custom workflows, and case type configurations. Some firms cite integration limitations or the desire for more modern AI features available in competing platforms.

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

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

Assembly Neos

Contact / Client (Person)

maps to

Nutshell

Person

1:1
Fully supported

Neos stores client/person records as contacts. FlitStack AI maps these directly to Nutshell People. The person's name, email, phone, and address fields transfer as direct field-level mappings. Neos contact IDs are preserved as a custom field for traceability, and cross-referencing during reconciliation.

Assembly Neos

Company / Firm

maps to

Nutshell

Account

1:1
Fully supported

Neos companies (law firms, opposing counsel, insurance carriers) map to Nutshell Accounts. Company name, domain, industry, and employee count fields map directly. Parent-child company hierarchies in Neos map to Nutshell's parent Account relationship, and any secondary addresses are carried over as address records in Nutshell.

Assembly Neos

Case / Matter

maps to

Nutshell

Custom field on Person / Deal

1:1
Fully supported

Neos matters have no native Nutshell equivalent. We extract matter name, case number, case type, and status, then store them as custom fields on the linked Person record and on Nutshell Deals that represent active client engagements. Case type becomes a custom pick-list field in Nutshell.

Assembly Neos

Case Notes / Attorney Notes

maps to

Nutshell

Note (on Person record)

1:1
Fully supported

Neos notes attached to a contact or case transfer as Nutshell Notes linked to the corresponding Person record. Original timestamps and author information are preserved. Rich-text formatting is converted to Nutshell's note format. Any embedded links or attachments are preserved as file links in the note.

Assembly Neos

Calendar / Deadline

maps to

Nutshell

Task

1:1
Fully supported

Neos calendared deadlines map to Nutshell Tasks with due dates. Statute of limitations and court deadlines that are critical in legal settings become high-priority tasks in Nutshell. Recurring deadlines map to Nutshell task recurrence where supported. Each task also records the original Neos deadline type for reference.

Assembly Neos

Custom Field (Matter-level)

maps to

Nutshell

Custom Field on Person / Account / Deal

1:1
Fully supported

Neos custom fields on matters (lien status, provider name, settlement stage) require new custom fields in Nutshell. FlitStack AI creates these fields during the migration plan phase and maps values field-by-field. Multi-select pick-lists require value-by-value mapping, and validates that each pick-list value appears in the Nutshell pick-list definition.

Assembly Neos

Document (File)

maps to

Nutshell

Attachment on Person / Account

1:1
Fully supported

Neos file attachments (contracts, correspondence, medical records) re-upload to Nutshell as file attachments on the Person record. Original filenames and upload timestamps are preserved. Large files are chunked per Nutshell's upload limits. The system also records the file's original storage location for audit purposes.

Assembly Neos

Contact Owner / Assigned Attorney

maps to

Nutshell

Nutshell User (assigned to Person)

1:1
Fully supported

Neos attorney and staff assignments resolve to Nutshell users by email match. Unmatched owners are flagged before migration so you can assign them to Nutshell accounts or reassign records before the full run. This ensures every record has a responsible owner in the new CRM.

Assembly Neos

Medical Provider / Treatment Record

maps to

Nutshell

Custom field on Person / Note

1:1
Fully supported

Neos treatment tracking and provider information has no native Nutshell equivalent. We preserve this as structured notes on the Person record with a custom field indicating provider name, treatment type, and status. You may also create a custom Nutshell object for provider records.

Assembly Neos

Trust Accounting Ledger

maps to

Nutshell

Not migratable

1:1
Fully supported

Neos trust account balances and transaction history cannot migrate to Nutshell. Nutshell does not support financial ledger or escrow accounting. Trust accounting must remain in dedicated legal accounting software such as CosmoLex or Clio Billing. We export the ledger as a CSV for your records.

Assembly Neos

Document Assembly Template

maps to

Nutshell

Not migratable

1:1
Fully supported

Neos document templates with merge fields and conditional logic cannot transfer. Nutshell has no document assembly feature. Templates must be rebuilt outside Nutshell using a dedicated document generation tool or migrated separately to a replacement platform. FlitStack AI exports a JSON schema of each template for reference during reconstruction.

Assembly Neos

Workflow / Automation Rule

maps to

Nutshell

Not migratable

1:1
Fully supported

Neos case intake workflows, medical records triggers, and milestone automations have no Nutshell equivalent. Sales sequences in Nutshell can replace basic follow-up automation, but legal-specific workflow logic must be documented and rebuilt manually or with Nutshell's automation builder. All workflow steps, conditions, and time triggers are exported as a reference map.

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.

Assembly Neos logo

Assembly Neos gotchas

High

Built-in accounting removed requires QuickBooks Online

Medium

Per-user pricing model affects migration scope

Medium

Document export requires Premium or Pro tier for full OCR

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

  • Legal-specific data has no native Nutshell equivalent

    Neos stores legal-specific data (case type, lien status, medical provider, settlement stage) that maps only to Nutshell custom fields. Nutshell does not have a Matter or Case object. All case-level properties must be defined as custom fields in Nutshell before migration. Custom field creation in Nutshell is limited by plan tier (Foundation plans support fewer custom fields than Pro). FlitStack AI audits your Neos custom field count during discovery and recommends plan upgrades if needed. Failure to pre-create custom fields results in those properties landing as unparsed text notes instead of structured data.

  • Document assembly templates and merge fields do not migrate

    Neos document templates with conditional logic, merge fields, and case-type-specific formatting have no equivalent in Nutshell. Nutshell's attachment model handles static file storage only. Law firms that rely on Neos document assembly for correspondence, demands, and settlement documents must rebuild these templates outside Nutshell using a dedicated document generation platform. FlitStack AI exports your Neos template definitions as a reference document your team can use during the rebuild phase, but the templates themselves cannot be imported into Nutshell.

  • Trust accounting ledger records have no destination

    Neos trust account transactions, escrow balances, and trust ledger entries cannot migrate to Nutshell. Nutshell has no accounting, ledger, or escrow object. Firms using Neos for trust accounting must retain that data in a dedicated legal accounting platform (CosmoLex, Clio Billing, LawPay). FlitStack AI exports trust ledger data as a CSV file for import into your chosen legal accounting software. The CSV preserves transaction date, amount, type, and matter reference so trust records remain auditable.

  • Workflows and case automations cannot transfer

    Neos case intake workflows, milestone automations, medical records triggers, and checklist logic are platform-specific automation constructs. Nutshell's automation engine (sequences, task triggers, stage-based rules) covers sales follow-ups but not legal process automation. You must document your Neos workflow logic during the discovery phase so your team can rebuild the automation in Nutshell or a separate workflow tool. FlitStack AI exports workflow definitions as a reference for your rebuild effort. The exported definitions include condition trees, assigned users, timing intervals, and trigger events, giving your team a detailed blueprint for reconstruction.

  • Neos API rate limits on large find queries affect extraction speed

    Neos's API rate limits large find requests, particularly when exporting full case histories or records with attachments. Nutshell's API also rate-limits find queries with non-stub responses. FlitStack AI sequences the migration in batches to respect both APIs' rate limit windows, which extends extraction time for large datasets. We coordinate with your Neos API key settings to maximize throughput within rate limit constraints. If necessary, we request temporary elevated limits from Neos support and schedule migration runs during off-peak hours to reduce wait times.

Migration approach

Six steps for a successful Assembly Neos to Nutshell data migration

  1. Audit Neos data model and capture custom field inventory

    FlitStack AI connects to Neos via scoped read access and exports a full inventory of contacts, companies, cases, notes, and custom field definitions. We identify all legal-specific properties (case type, lien status, provider fields) that need to become Nutshell custom fields. We also capture workflow definitions and document template metadata for your rebuild reference. The audit output includes record counts per object, custom field count, and a preliminary value-mapping plan for pick-list fields.

  2. Design Nutshell schema and pre-create custom fields

    Before data moves, FlitStack AI generates a Nutshell schema setup plan specifying which custom fields to create on Person, Account, and Deal objects, along with field types (text, pick-list, date, number) and any value-mapping rules for pick-list fields. Your Nutshell admin creates these fields (or our team assists via Nutshell API). We also configure the Nutshell pipeline and stage structure to mirror your Neos case pipeline. Schema readiness is a prerequisite for the field-level diff in step 4.

  3. Resolve Neos users to Nutshell users by email

    Neos attorney and staff assignments are resolved against Nutshell users by email address. Any Neos user without a corresponding Nutshell account is flagged before migration. You either invite the user to Nutshell or reassign their Neos records to an existing Nutshell owner before the full migration runs. No record lands in Nutshell without a valid owner reference. This ensures accurate responsibility tracking and reporting throughout the CRM.

  4. Run sample migration with field-level diff

    A representative slice of 100–500 records migrates first, covering contacts, companies, cases, notes, and custom fields. FlitStack AI generates a field-level diff comparing source values in Neos against destination values in Nutshell. You verify case-type mapping, lien status preservation, custom field population, and owner resolution before the full run commits. Sample migration reveals value-mapping gaps and pick-list mismatches before they affect the full dataset.

  5. Execute full migration with delta-pickup and audit log

    The full migration runs against Nutshell using bulk-compatible API operations. A delta-pickup window (24–48 hours) captures any records created or modified in Neos during the cutover window. Every operation is recorded in an audit log. One-click rollback is available if reconciliation detects missing records or field-level discrepancies. Trust accounting ledger and document template definitions are exported as CSV and JSON reference files during this phase.

Platform deep dives

Context on both ends of the pair

Assembly Neos logo

Assembly Neos

Source

Strengths

  • Cloud-based access from any device with no VPN required for remote teams
  • Microsoft 365, QuickBooks, DocuSign, and RingCentral integrations built natively into the platform
  • AI document summarization and data extraction reduce manual data entry overhead
  • Configurable case types and customizable layouts adapt to firm-specific workflows
  • Per-user pricing with annual discount options suitable for small to mid-size law firms

Weaknesses

  • Frequent software bugs and slow performance cited across multiple G2 reviews with 18 mentions of document upload issues
  • Performance degrades under heavy workloads with large case volumes or many concurrent users
  • Built-in accounting is absent, requiring third-party QuickBooks integration for all billing and disbursement tasks
  • Learning curve for advanced features including templates, custom workflows, and case type configurations
  • No free version or free trial available, limiting pre-purchase evaluation
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 Assembly Neos 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

    Assembly Neos: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Assembly Neos to Nutshell migrations complete in 48–72 hours of clock time for under 25,000 records. Larger setups with 100,000+ records, complex custom field mapping, or multi-stage case pipelines extend to 5–10 days. The longest planning step is designing the Nutshell custom field schema and value-mapping plan for legal-specific pick-lists before data moves, including the setup of custom fields on Person, Account, and Deal objects.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Assembly Neos.
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