CRM migration
Field-level mapping, validation, and rollback between Assembly Trialworks and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Assembly Trialworks
Source
Nutshell
Destination
Compatibility
11 of 12
objects map 1:1 between Assembly Trialworks and Nutshell.
Complexity
BStandard
Timeline
2–4 weeks
Overview
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.
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 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
Nutshell
Deal
1:1Cases 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)
Nutshell
Person + custom fields
1:1Parties 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
Nutshell
Person
1:1Attorney 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)
Nutshell
File attached to Deal or Person
1:1Assembly 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
Nutshell
Activity (Task or Event)
1:1Assembly 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
Nutshell
Deal Custom Fields
1:1Assembly 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
Nutshell
Account + Person
many:1Insurance 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
Nutshell
Person Owner field
1:1Assembly 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)
Nutshell
Lead
1:1Prospective 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
Nutshell
No equivalent
1:1Assembly 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
Nutshell
No equivalent
1:1Assembly 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
Nutshell
No equivalent (data underlying migrates)
1:1Assembly 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.
| Assembly Trialworks | Nutshell | Compatibility | |
|---|---|---|---|
| Case | Deal1:1 | Fully supported | |
| Party (Plaintiff/Defendant/Attorney) | Person + custom fields1:1 | Fully supported | |
| Opposing Counsel / Co-Counsel | Person1:1 | Fully supported | |
| Document (Pleadings, Discovery, Exhibits) | File attached to Deal or Person1:1 | Fully supported | |
| Calendar / Court Date / Deadline | Activity (Task or Event)1:1 | Fully supported | |
| Case Custom Fields | Deal Custom Fields1:1 | Fully supported | |
| Insurance Carrier / Adjuster | Account + Personmany:1 | Fully supported | |
| User / Staff Assignment | Person Owner field1:1 | Fully supported | |
| Intake / Lead (prospective client) | Lead1:1 | Fully supported | |
| Document Template / Form | No equivalent1:1 | Fully supported | |
| Workflow / Automation / Fast Track Rule | No equivalent1:1 | Fully supported | |
| Reporting / Dashboard | No equivalent (data underlying migrates)1: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 Trialworks gotchas
No public API means migration requires direct SQL database access
Assembly has discontinued custom dashboard creation and modification
FileIT document import requires a parallel folder-to-case mapping step
Custom fields are firm-specific and must be discovered before mapping
Firms being pushed toward cloud-only Neos despite needing on-premise
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
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.
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.
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.
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.
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
Assembly Trialworks
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 Trialworks 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 Trialworks: Not applicable—no public API.
Data volume sensitivity
Assembly Trialworks 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 Trialworks to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Assembly Trialworks
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.