CRM migration
Field-level mapping, validation, and rollback between Assembly Neos and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Assembly Neos
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Assembly Neos and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
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.
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 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)
Nutshell
Person
1:1Neos 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
Nutshell
Account
1:1Neos 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
Nutshell
Custom field on Person / Deal
1:1Neos 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
Nutshell
Note (on Person record)
1:1Neos 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
Nutshell
Task
1:1Neos 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)
Nutshell
Custom Field on Person / Account / Deal
1:1Neos 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)
Nutshell
Attachment on Person / Account
1:1Neos 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
Nutshell
Nutshell User (assigned to Person)
1:1Neos 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
Nutshell
Custom field on Person / Note
1:1Neos 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
Nutshell
Not migratable
1:1Neos 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
Nutshell
Not migratable
1:1Neos 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
Nutshell
Not migratable
1:1Neos 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.
| Assembly Neos | Nutshell | Compatibility | |
|---|---|---|---|
| Contact / Client (Person) | Person1:1 | Fully supported | |
| Company / Firm | Account1:1 | Fully supported | |
| Case / Matter | Custom field on Person / Deal1:1 | Fully supported | |
| Case Notes / Attorney Notes | Note (on Person record)1:1 | Fully supported | |
| Calendar / Deadline | Task1:1 | Fully supported | |
| Custom Field (Matter-level) | Custom Field on Person / Account / Deal1:1 | Fully supported | |
| Document (File) | Attachment on Person / Account1:1 | Fully supported | |
| Contact Owner / Assigned Attorney | Nutshell User (assigned to Person)1:1 | Fully supported | |
| Medical Provider / Treatment Record | Custom field on Person / Note1:1 | Fully supported | |
| Trust Accounting Ledger | Not migratable1:1 | Fully supported | |
| Document Assembly Template | Not migratable1:1 | Fully supported | |
| Workflow / Automation Rule | Not migratable1: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.
Assembly Neos gotchas
Built-in accounting removed requires QuickBooks Online
Per-user pricing model affects migration scope
Document export requires Premium or Pro tier for full OCR
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 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.
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.
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.
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.
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
Assembly Neos
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 Assembly Neos 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
Assembly Neos: Not publicly documented.
Data volume sensitivity
Assembly Neos 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 Assembly Neos to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Assembly Neos
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.