Migrate your Assembly Trialworks data
On-premise Windows case management built for litigation and PI firms, now in a products-in-transition moment as Assembly steers customers toward its cloud platform.
In its favor
Why people choose Assembly Trialworks
The signal that keeps Assembly Trialworks on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Firms choose Trialworks for its deep integration with Microsoft Office and Corel WordPerfect for document generation, a workflow that many litigation attorneys have used for decades and do not want to rebuild.
The platform is Windows-native with no per-seat cloud subscription model, appealing to firms that want perpetual licensing and local server control rather than recurring SaaS costs.
Personal injury firms value the structured Claims and Parties data model that Trialworks enforces, which mirrors how PI workflows actually operate—high-volume medical records, liability parties, insurance carriers.
G2 reviewers specifically mention customizable dashboards as a strength, allowing each attorney or paralegal to surface the metrics most relevant to their caseload.
The on-premise deployment model satisfies data residency and confidentiality requirements that some litigation firms maintain due to client privilege concerns.
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.
Reasons to switch
Why people leave Assembly Trialworks
The recurring reasons buyers give for replacing Assembly Trialworks. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Assembly Trialworks fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Assembly Trialworks pricing overview
Trialworks historically sold as a perpetual on-premise license with an annual maintenance contract. Current pricing is confirmed directly with Assembly sales. The successor platform Neos uses a per-seat monthly subscription model starting around $39/month for the Starter tier.
TrialWorks Perpetual License
Tier 1 of 3
~$495 one-time (historical; current availability confirmed per vendor)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Assembly Trialworks's schedule — see our quote-based pricing →
What gets migrated
Assembly Trialworks object support
Object-by-object support for Assembly Trialworks migrations. Per-pair details surface during scoping.
Matters
Fully supportedMatters is the primary case container in Trialworks. We export the full Matter record including case number, status, type, responsible attorney, paralegal, and opened/closed dates. Standard fields map 1:1 to destination Matter or Case objects.
Clients
Fully supportedClient records contain name, contact information, address, date of birth, and client type. We preserve all standard fields. Custom client properties require field-level mapping to the destination schema.
Parties
Mapping requiredTrialworks supports multiple Party types (defendant, co-defendant, insurer, etc.) per Matter. Party-to-Matter associations are stored as relational records. We export all Party links and reconstruct them in the destination, mapping Party type values to the destination's equivalent taxonomy.
Claims
Mapping requiredClaims are a structured sub-record attached to a Matter capturing claim type, amount, status, and description. Destination platforms often flatten Claims into custom Matter fields or a separate Claims object. We map the claim structure and flag any loss of relational fidelity.
Documents
Mapping requiredTrialworks stores documents in a Casefiles folder structure with a proprietary index database. The FileIT utility imports local files into the case structure. We extract documents from the Casefiles directory and re-associate them to the correct Matter in the destination using the index as our mapping key.
Bills and Time Entries
Mapping requiredBill records include time entries, expense items, retainer tracking, and payment history. Trialworks bills are often tightly coupled to the SQL schema. We export bill headers and line items and map them to the destination's invoice or billing object, noting any fee structure differences.
Calendar Events
Mapping requiredCalendar entries are stored in Trialworks with date, time, matter association, attendee, and reminder fields. We export events and import them as calendar records in the destination, applying the correct timezone and noting any all-day versus timed event discrepancies.
Tasks
Mapping requiredTask records include due date, assignee, priority, status, and matter association. Task ordering and subtask hierarchies vary by firm. We export flat task lists and reconstruct them, flagging any subtask chains that do not map directly to the destination's task model.
Custom Fields
Mapping requiredTrialworks allows firms to define custom fields on Matters, Clients, Parties, and other objects. These are stored in the SQL schema as additional columns. We export all custom field values and map them to destination custom fields, requiring a discovery pass to identify which custom fields exist in each firm's database before migration.
Contacts
Fully supportedContact records include name, company, role, phone, email, and address. We export all contacts including attorney contacts, expert witnesses, and vendor contacts. Standard fields map cleanly to most destination CRM contact objects.
Document Tabs
Mapping requiredTrialworks organizes documents into named tabs (Medical Records, Pleadings, Correspondence, etc.) within each case. These are configured per firm. We export tab assignments and recreate the same structure in the destination, applying the firm's tab taxonomy.
Trust Accounts
Mapping requiredTrust account balances and transaction histories are stored in Trialworks. We export the trust ledger entries and map them to the destination's trust or escrow accounting module, noting any currency or multi-currency handling differences.
| Object | Support | Notes |
|---|---|---|
| Matters | Fully supported | Matters is the primary case container in Trialworks. We export the full Matter record including case number, status, type, responsible attorney, paralegal, and opened/closed dates. Standard fields map 1:1 to destination Matter or Case objects. |
| Clients | Fully supported | Client records contain name, contact information, address, date of birth, and client type. We preserve all standard fields. Custom client properties require field-level mapping to the destination schema. |
| Parties | Mapping required | Trialworks supports multiple Party types (defendant, co-defendant, insurer, etc.) per Matter. Party-to-Matter associations are stored as relational records. We export all Party links and reconstruct them in the destination, mapping Party type values to the destination's equivalent taxonomy. |
| Claims | Mapping required | Claims are a structured sub-record attached to a Matter capturing claim type, amount, status, and description. Destination platforms often flatten Claims into custom Matter fields or a separate Claims object. We map the claim structure and flag any loss of relational fidelity. |
| Documents | Mapping required | Trialworks stores documents in a Casefiles folder structure with a proprietary index database. The FileIT utility imports local files into the case structure. We extract documents from the Casefiles directory and re-associate them to the correct Matter in the destination using the index as our mapping key. |
| Bills and Time Entries | Mapping required | Bill records include time entries, expense items, retainer tracking, and payment history. Trialworks bills are often tightly coupled to the SQL schema. We export bill headers and line items and map them to the destination's invoice or billing object, noting any fee structure differences. |
| Calendar Events | Mapping required | Calendar entries are stored in Trialworks with date, time, matter association, attendee, and reminder fields. We export events and import them as calendar records in the destination, applying the correct timezone and noting any all-day versus timed event discrepancies. |
| Tasks | Mapping required | Task records include due date, assignee, priority, status, and matter association. Task ordering and subtask hierarchies vary by firm. We export flat task lists and reconstruct them, flagging any subtask chains that do not map directly to the destination's task model. |
| Custom Fields | Mapping required | Trialworks allows firms to define custom fields on Matters, Clients, Parties, and other objects. These are stored in the SQL schema as additional columns. We export all custom field values and map them to destination custom fields, requiring a discovery pass to identify which custom fields exist in each firm's database before migration. |
| Contacts | Fully supported | Contact records include name, company, role, phone, email, and address. We export all contacts including attorney contacts, expert witnesses, and vendor contacts. Standard fields map cleanly to most destination CRM contact objects. |
| Document Tabs | Mapping required | Trialworks organizes documents into named tabs (Medical Records, Pleadings, Correspondence, etc.) within each case. These are configured per firm. We export tab assignments and recreate the same structure in the destination, applying the firm's tab taxonomy. |
| Trust Accounts | Mapping required | Trust account balances and transaction histories are stored in Trialworks. We export the trust ledger entries and map them to the destination's trust or escrow accounting module, noting any currency or multi-currency handling differences. |
Gotchas
What to watch for in Assembly Trialworks migrations
Issues we've hit on past Assembly Trialworks migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
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
| Severity | Issue |
|---|---|
| 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 |
Leaving Assembly Trialworks?
Where Assembly Trialworks customers move next
12 destinations Assembly Trialworks can migrate to.
How a Assembly Trialworks migration works
Four steps, Assembly Trialworks-specific
Connect
None documented into Assembly Trialworks. Scopes limited to read-only on the data we move.
Map
We translate Assembly Trialworks-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Assembly Trialworks quirks before production.
Migrate
Full migration with Assembly Trialworks rate-limit handling. Rollback available throughout.
FAQ
Assembly Trialworks migration FAQ
Answers to the questions buyers ask most during Assembly Trialworks migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Assembly Trialworks migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Assembly Trialworks.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Assembly Trialworks setup and destination — written quote back within a business day.