CRM migration

Migrate from Assembly Trialworks to Nutshell

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

Assembly Trialworks logo

Assembly Trialworks

Source

Nutshell

Destination

Nutshell logo

Compatibility

92%

11 of 12

objects map 1:1 between Assembly Trialworks and Nutshell.

Complexity

BStandard

Timeline

2–4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Assembly Trialworks organizes work around cases, parties, attorneys, documents, and court dates for litigation practices. Nutshell models data around accounts, people, leads, and deals for sales teams. These platforms serve different industries and different data shapes, so migration requires deliberate object translation rather than direct field carry-over. We extract cases, parties, attorneys, documents, calendar events, and custom fields from Assembly Trialworks, then map them to Nutshell's People, Accounts, Leads, and Deals objects — creating custom fields on each for case-number, court, responsible-attorney, and statute-of-limitations data that Nutshell does not store natively. We re-upload document attachments to Nutshell Files, preserving original filenames and association to the correct deal or person record. We surface workflows, automations, and reporting templates as rebuild references since those constructs do not exist in Nutshell's schema. Our migration engine runs against Assembly Trialworks via its data export interface and loads into Nutshell via the Nutshell REST API, with a 24–48 hour delta window capturing any records modified during the cutover window. Before committing a full run, we execute a sample migration against a representative slice of your data and generate a field-level diff so you can verify case-to-deal mapping, party contact linking, and document re-association before go-live.

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 Trialworks logo

Assembly Trialworks

What's pushing teams away

  • Assembly Software is actively steering Trialworks customers toward Neos, its cloud-only successor, and has stopped creating or modifying custom dashboards, making the platform feel like it is entering long-term maintenance mode.
  • Neos is cloud-only with no on-premise option, which forces firms that require local server deployment to either switch platforms entirely or accept a deployment model they never chose.
  • Users report that Neos lacks features Trialworks had, and G2 satisfaction scores for Neos exceed Trialworks, creating pressure without clear functional parity at launch.
  • The forced transition conversation is creating churn anxiety among firms that do not want to migrate to a cloud product but face uncertainty about Trialworks' long-term roadmap despite Assembly's official no-EOL statement.
  • Windows-only workstation requirement and lack of native Mac or mobile support increasingly conflicts with modern law firm BYOD expectations and hybrid work arrangements.

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

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

Case

maps to

Nutshell

Deal

1:1
Fully supported

Cases map to Nutshell Deals as the primary record. Case number, court name, statute of limitations, and responsible attorney fields are created as custom fields on the Deal. Each Case generates one Deal; the Deal name defaults to the case number or case short name.

Assembly Trialworks

Party (Plaintiff/Defendant/Attorney)

maps to

Nutshell

Person + custom fields

1:1
Fully supported

Parties map to Nutshell Person records. We preserve the party role (Plaintiff, Defendant, Opposing Counsel, etc.) as a custom field on the Person so the litigation role is visible without a separate object. Multiple parties on one case link to the same Deal via Nutshell's deal association.

Assembly Trialworks

Opposing Counsel / Co-Counsel

maps to

Nutshell

Person

1:1
Fully supported

Attorney contacts with bar number, firm name, and contact details map directly to Nutshell Person records. The attorney role is stored as a custom Person field. Links to the opposing or co-counsel are preserved as Person-to-Person relationships where the CRM allows.

Assembly Trialworks

Document (Pleadings, Discovery, Exhibits)

maps to

Nutshell

File attached to Deal or Person

1:1
Fully supported

Assembly documents are exported from the hosted file system, downloaded with their folder and tab categorization preserved. We re-upload them as Nutshell Files linked to the corresponding Deal (or Person for attorney documents). Assembly's document category (tab) is stored as a custom tag field in Nutshell.

Assembly Trialworks

Calendar / Court Date / Deadline

maps to

Nutshell

Activity (Task or Event)

1:1
Fully supported

Assembly docketing entries (Fast Track court dates, deadlines, statute dates) map to Nutshell Activities. A Task is created for each docket entry with the due date as the activity date, the matter/case as the related Deal, and the court or deadline type as the task name. We cannot replicate docketing-only views in Nutshell — these are surfaced as rebuild reference exports.

Assembly Trialworks

Case Custom Fields

maps to

Nutshell

Deal Custom Fields

1:1
Fully supported

Assembly custom fields on cases (e.g., insurance carrier, case type, venue, jurisdictional tags) are created as matching custom fields on Nutshell Deals. Field types are translated: pick-lists become Nutshell choice fields, dates become date fields, free text becomes text fields. We flag any Assembly field that cannot be represented in Nutshell's supported types.

Assembly Trialworks

Insurance Carrier / Adjuster

maps to

Nutshell

Account + Person

many:1
Fully supported

Insurance carriers and adjusters on a case are modeled as two records in Nutshell: the carrier organization as an Account and the adjuster contact as a Person linked to that Account. This captures the organizational relationship while keeping the adjuster's contact details accessible on the Deal.

Assembly Trialworks

User / Staff Assignment

maps to

Nutshell

Person Owner field

1:1
Fully supported

Assembly user assignments (paralegal, associate, partner) map to the responsible attorney Person record on the Deal. We match by email to Nutshell users; any Assembly user without a matching Nutshell account is flagged for admin review before migration. Role assignments are stored as custom Person fields to preserve the original staff designation on each case.

Assembly Trialworks

Intake / Lead (prospective client)

maps to

Nutshell

Lead

1:1
Fully supported

Prospective client records in Assembly that have not yet opened a case map to Nutshell Leads. Basic contact information (name, phone, email, referral source) transfers directly. Once a case is opened in Assembly, the corresponding Lead in Nutshell is converted to a Person and linked to the Deal.

Assembly Trialworks

Document Template / Form

maps to

Nutshell

No equivalent

1:1
Fully supported

Assembly document templates (Word, PDF forms generated within TrialWorks) have no direct equivalent in Nutshell. We provide a full export of template filenames and storage locations as a rebuild reference for your team to set up in Word, PDF form tools, or Nutshell integrations post-migration.

Assembly Trialworks

Workflow / Automation / Fast Track Rule

maps to

Nutshell

No equivalent

1:1
Fully supported

Assembly Fast Track rules and docketing automations have no Nutshell equivalent. We export the workflow definitions (rule names, triggers, actions) as a structured reference document so your team can implement equivalent automation in Nutshell or a connected tool like Zapier after migration.

Assembly Trialworks

Reporting / Dashboard

maps to

Nutshell

No equivalent (data underlying migrates)

1:1
Fully supported

Assembly SQL-built dashboards and reporting templates cannot be migrated. The underlying data (cases, parties, documents, activities) migrates in full. We provide a dashboard export showing each report's dimensions, filters, and chart types as a specification for rebuilding in Nutshell's built-in reporting or an external BI tool.

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 Trialworks logo

Assembly Trialworks gotchas

High

No public API means migration requires direct SQL database access

High

Assembly has discontinued custom dashboard creation and modification

Medium

FileIT document import requires a parallel folder-to-case mapping step

Medium

Custom fields are firm-specific and must be discovered before mapping

Medium

Firms being pushed toward cloud-only Neos despite needing on-premise

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

  • No native Cases object in Nutshell — cases must become Deals with custom fields

    Nutshell has no case-management entity. Every Assembly Trialworks case migrates as a Nutshell Deal with custom fields appended for case_number, court_name, statute_of_limitations, and responsible_attorney. Any reports built in Assembly around case-specific metrics (days-to-filing, discovery cutoffs, trial date) must be rebuilt in Nutshell's reporting module or in a connected BI tool after migration. FlitStack exports the full schema of each Assembly custom dashboard as a rebuild specification so your team can replicate the logic.

  • Party-role pick-lists require value-by-value mapping to Nutshell custom choice fields

    Assembly Trialworks stores party roles as a configured pick-list (Plaintiff, Defendant, Counterclaimant, Co-Party, Expert Witness, etc.). Nutshell custom choice fields must be created with the exact same values manually in Settings before migration runs, or records with unmatched values will default to blank. We deliver a party-role value list export from Assembly as a pre-migration setup checklist so Nutshell admins can create the choice field values before the data lands.

  • Large document attachments hit Nutshell's 25MB per-file limit

    Assembly Trialworks document libraries can contain large files — deposition transcripts, medical records, or court filings can exceed 25MB. Nutshell Files default to a 25MB per-file ceiling. Files over this threshold are flagged during the pre-migration audit and can be either split into smaller documents (by page range or section) or stored in a connected cloud storage integration (Google Drive, Dropbox) with the Nutshell File record pointing to the external URL. We identify every oversized file before migration so no record lands with a broken attachment.

  • Docketing calendar entries have no equivalent scheduling construct in Nutshell

    Assembly Fast Track docketing tracks court dates, filing deadlines, and statute-of-limitations windows with automatic reminders tied to case-stage rules. Nutshell Activities are standard CRM tasks and events with no docketing-specific logic. Each Assembly docket entry migrates as an individual Nutshell Activity — but you lose the docketing view, the court-calendar overview, and the automatic deadline escalation that Assembly provides. We export all docketing rules as a structured automation spec so your team can implement reminder logic in Nutshell Workflows or Zapier post-migration.

Migration approach

Six steps for a successful Assembly Trialworks to Nutshell data migration

  1. Extract and profile Assembly Trialworks data

    We pull a full export of cases, parties, attorneys, documents, calendar entries, custom fields, and user accounts from Assembly Trialworks. This includes metadata for each document (filename, size, tab category, author, date). We run a data-quality profile identifying missing required fields, duplicate party records, and oversized documents that will hit Nutshell's 25MB file limit. We deliver a data-quality report before writing a single record to Nutshell.

  2. Create Nutshell custom fields and choice values

    Before any data lands, we create all required custom fields on Nutshell Deals, People, Accounts, Leads, and Files — matching the field types, choice values, and labels from Assembly's schema. This includes case_number, court_name, statute_of_limitations, responsible_attorney, party_role, document_category, and any other legal-specific properties. We provide a pre-migration setup checklist so your Nutshell admin can create fields in the correct order.

  3. Run a sample migration with field-level diff

    A representative slice — typically 50–100 cases spanning the range of case types, party counts, and document sizes — migrates first. We generate a field-level diff comparing source values against destination fields so you can verify case-to-deal naming, party-role mapping, document re-association, and user resolution. We surface any unmapped fields or value mismatches at this stage before the full run commits.

  4. Execute full migration with dependency sequencing

    Accounts migrate first (insurance carriers and law firms), then People (parties and attorneys), then Leads, then Deals (cases) with party associations and document attachments linked in order. The Nutshell REST API is used for all writes, ensuring each entity's dependencies are resolved before child records are created. Any documents exceeding 25MB are flagged for splitting or external storage linking before the migration run completes.

  5. Cutover with delta pickup and reconciliation

    During the cutover window, Assembly Trialworks operates in read-only mode — your team continues working but no new records are created that would be missed. We capture a final delta export for any cases, parties, or calendar entries modified in the last 24–48 hours. An audit log records every operation. We run a reconciliation count against source totals for contacts, accounts, deals, and documents. One-click rollback is available if the reconciliation reveals gaps.

Platform deep dives

Context on both ends of the pair

Assembly Trialworks logo

Assembly Trialworks

Source

Strengths

  • Windows-native platform with deep Microsoft Office and WordPerfect document generation integration that litigation attorneys know well.
  • SQL Server backend gives IT staff full access to the database for custom reporting, backup, and integration work.
  • Customizable dashboards let individual users surface case metrics and pipeline views tailored to their practice area.
  • Supports on-premise, hosted, and virtual desktop deployment, giving firms flexibility in how they run the software.
  • Structured Claims and Parties data model aligns closely with how PI and liability litigation firms actually organize case information.

Weaknesses

  • No public REST API documented, making programmatic export and import a custom SQL-level operation rather than a standard integration.
  • Assembly has stopped creating or modifying custom dashboards, signaling reduced investment in the platform's feature set.
  • Strictly Windows-only workstations; no native Mac or Linux client, limiting deployment flexibility for modern hybrid work environments.
  • Cloud-only successor (Neos) has no on-premise option, forcing firms with local server requirements to migrate to a different platform entirely if they want to stay current.
  • Support for NeosAI and newer AI-powered features is concentrated in Neos, leaving Trialworks users without access to Assembly's most recent product investments.
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 Trialworks 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 Trialworks: Not applicable—no public API.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Assembly-to-Nutshell migrations complete in 2–4 weeks of project time for under 10,000 case records and standard custom field sets. The longest phase is data profiling and custom field creation in Nutshell (5–7 days), followed by the migration run itself (1–3 days) and reconciliation (1 day). Large document libraries exceeding 10GB or migrations with 50+ custom fields per entity extend the timeline to 5–8 weeks. We include a sample migration in every project so the full run has a verified mapping before your team commits to cutover.

Adjacent paths

Related migrations to explore

Ready when you are

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