Migrate from Assembly Trialworks to Mailchimp

TrialWorks party records (plaintiffs, defendants, witnesses, medical providers, insurers) map as direct to Mailchimp audience members. One person who appears under multiple party roles across one or more matters is deduplicated into a single Mailchimp contact and tagged by role.

TrialWorks stores the role type (Plaintiff, Defendant, Witness, Medical Provider, Insurer, etc.) as a party-role label on each contact. We preserve this as a Mailchimp tag — one tag per distinct role the contact held across all TrialWorks matters. Contacts with multiple roles receive multiple tags.

TrialWorks case numbers have no native Mailchimp equivalent. We offer two options: appending case numbers as tags (e.g., TW-CASE-2024-0142) for reference filtering, or storing the primary case number as a custom merge field (PRIMARY_CASE__c) for segmentation. Your team chooses the approach during planning.

TrialWorks custom properties on parties — such as referral_source, lead_origin, or attorney_assigned — require Mailchimp merge fields to be created before migration. FlitStack delivers a merge-field setup plan for your Mailchimp admin to execute, then maps the values during migration. This is the primary source of added scope in TrialWorks-to-Mailchimp migrations.

Phone numbers on TrialWorks party records map directly to the Mailchimp PHONE merge field. TrialWorks does not enforce a consistent phone format — we normalize to E.164 during migration where possible, and flag records with missing or malformed phone numbers for your review.

Email addresses on TrialWorks party contacts map directly to the Mailchimp EMAIL field. FlitStack validates email format and flags bounces, role-based addresses (info@, admin@), and duplicates before migration so your Mailchimp audience lands with a clean address base. This pre-migration validation prevents deliverability issues and protects your sender reputation from the start.

TrialWorks party mailing addresses map to Mailchimp's standard address merge fields. Multi-line addresses in TrialWorks are split across ADDR1 and ADDR2. Incomplete addresses (missing city, state, or ZIP code) are flagged in the migration report — Mailchimp's built-in address validation can be run post-migration to verify and correct any incomplete records for postal deliverability.

TrialWorks notes on party records contain case-specific context that has no direct Mailchimp equivalent. We preserve the most recent note text as a Mailchimp contact note for reference. Full note history is not migrated — case-specific notes are inherently tied to the matter context that Mailchimp cannot represent.

TrialWorks document management (pleadings, medical records, correspondence files) has no Mailchimp equivalent. Documents are not migrated. If you need to associate case documents with Mailchimp contacts for compliance or client communication purposes, that requires a separate document management integration — FlitStack does not handle file transfers to Mailchimp.

TrialWorks docketing and court date tracking has no Mailchimp equivalent. Calendaring data is not migrated. Court dates, filing deadlines, and appearance schedules remain stored in your legal case management system (Neos, Clio, or another platform) after migration — these legal workflow dates are not relevant to email marketing and fall outside Mailchimp's audience model.

TrialWorks medical records management is a legal-workflow feature with no Mailchimp equivalent. PHI-adjacent data is not migrated. If your firm uses medical record data for marketing segmentation (e.g., injury type tags), that data must be transferred manually as Mailchimp tags or merge fields after migration.

TrialWorks Fast Tracks and process control settings (docketing rules, discovery deadlines, workflow stages) are legal operations logic with no Mailchimp equivalent. These settings do not migrate and must be reconfigured in your destination legal platform if you are also moving case management systems.

Attorney contacts stored as parties in TrialWorks (opposing counsel, co-counsel, insurance adjusters) are migrated as Mailchimp audience members. These contacts receive the Attorney tag. Note that the ABA rules and privilege implications of communicating via Mailchimp with opposing counsel differ from legal case management channels — your firm is responsible for compliance decisions.

Insurer party records on TrialWorks matters (insurance carrier name, adjuster name, policy number, claim number) can be migrated as contacts. Policy and claim numbers are stored as custom merge fields in Mailchimp. Carrier adjuster email addresses are mapped as EMAIL, and the carrier company name is stored as a merge field for segmentation.

Witness party records migrate as Mailchimp audience members tagged with WITNESS. Witness contact information (name, phone, address) maps directly to standard merge fields. Deposition dates or witness statement notes are not migrated — those belong in your case management system.