CRM

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.

Encrypted end-to-end with one-click rollback
Talk to a real migration engineer in minutes
Assembly Trialworks logo

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

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.

Where it works

Small to mid-sized personal injury firms with high-volume medical records, liability parties, and insurance carrier workflows, where the structured Claims and Parties data model mirrors how PI practice actually operates.Litigation firms with dedicated IT staff experienced in Microsoft SQL Server who need full database access for custom reporting, backup, and integration work without learning a new platform.Firms with strict data residency or client privilege requirements that demand on-premise or locally hosted deployment rather than cloud infrastructure, and have Windows server infrastructure already in place.Attorneys and paralegals who rely heavily on Microsoft Office and WordPerfect document generation workflows built over decades and do not want to rebuild those templates in a new system.Firms that prefer perpetual licensing with local server control over recurring SaaS subscriptions, particularly those already operating virtual desktop environments for hybrid work.

Where it struggles

Firms with Mac-only or mobile-first attorneys who cannot run the Windows-only workstation client and lack Remote Desktop infrastructure for virtual access.Organizations being steered toward Assembly Neos as their cloud successor, which has no on-premise option, forcing firms with local server requirements to either switch platforms or accept a deployment model they never chose.Law firms that require modern AI-powered features such as NeosAI document intelligence or automated intake workflows, since Assembly has concentrated these investments in Neos rather than Trialworks.Practices with hybrid or BYOD expectations where attorneys work from personal laptops or non-Windows devices and need native application access rather than Remote Desktop sessions.Firms seeking a platform with a documented public REST API for integrations, since Trialworks requires custom SQL-level extraction rather than standard API-based connectivity.

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

Perpetual on-premise license for Windows workstations and serverRequires SQL Server (not included)Annual maintenance and support contract billed separatelyDeployment handled by firm IT or a hosting provider

Need help selecting your CRM?

Book a free 30 minute consultation

Pricing 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 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.

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

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 consultation

Most Assembly Trialworks migrations under 1M records finish in 48–72 hours end-to-end. Larger orgs with custom objects or buyer-side security review typically take 5–7 days.

Ready 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.

Free scoping call Quote in 1 business day 1,784 platforms supported