Migrate from Assembly Trialworks to Pipedrive

Trialworks Case is the central record. It maps to Pipedrive Deal (the Opportunity-equivalent) where the case name becomes Deal title, case amount maps to Deal value, and case status maps to a pipeline stage value. Custom fields on the case (practice area, court, opposing counsel) migrate as Pipedrive custom fields on the Deal.

Trialworks Party records (clients, witnesses, opposing counsel, etc.) map directly to Pipedrive People. Party roles stored in a 'role' custom field on the Person record since Pipedrive has no native party-role concept. Multiple parties on one case are linked via Deal-Person association in Pipedrive.

Trialworks Party records whose role indicates a company or firm—such as opposing law firms, insurance carriers, or corporate entities—are merged into Pipedrive Organizations. The Party name becomes the Organization name, and any address or contact information stored on the Party record is transferred to the Organization fields. All related individual Party records (e.g., attorneys or adjusters) are linked to that Organization via Pipedrive's relationship model, preserving the hierarchical context while eliminating duplicate Organization entries.

Trialworks documents are stored within the Case record's file tab. Pipedrive stores files attached to People, Organizations, or Deals but has no native document-management tab. We export documents to your specified cloud storage (SharePoint, Google Drive, Dropbox) and re-associate them as file attachments on the corresponding Deal or Person in Pipedrive.

Trialworks bill records contain line items, totals, and payment status tied to a Case. Pipedrive has no accounts-receivable model. Bill totals and outstanding balance migrate as custom fields on the Deal for reference, but the billing logic must be handled outside Pipedrive (or via Pipedrive Products for time tracking).

Trialworks calendar entries and court dates map to Pipedrive Activities (meetings or tasks) with the original date and time preserved. The activity subject carries the event title; a custom field marks events originally labeled as court dates for filtering in Pipedrive.

Communication logs and notes attached to a Trialworks Case migrate as Pipedrive Notes on the corresponding Deal. Original creation timestamps and author IDs are preserved in the note metadata. Rich-text formatting is stripped to plain text because Pipedrive Notes does not support HTML. Attachments are not migrated; they are flagged in the migration report for manual re‑attachment. Notes remain searchable within Pipedrive's activity timeline.

Trialworks custom fields defined at the Case level are recreated as Pipedrive Deal custom fields via POST /dealFields. Field type is mapped: text → VARCHAR, number → NUMBER, date → DATE, picklist → DROP_DOWN. The custom field key (hash) is assigned by Pipedrive and stored for traceability.

Trialworks custom fields defined at the Party level are recreated as Pipedrive Person custom fields via POST /personFields. Field types are mapped: text to VARCHAR, numbers to NUMBER, dates to DATE, and pick‑lists to DROP_DOWN. Party‑specific data such as bar number, engagement status, or billing rate migrates to these fields. Pipedrive assigns a hash key to each field; FlitStack stores it for data writes, ensuring field population on Person record.

Trialworks practice areas or case-type categorizations that function as pipelines are mapped to Pipedrive Pipelines. Each distinct Trialworks case type becomes a separate Pipedrive pipeline, and the corresponding stage values (e.g., Intake, Discovery, Hearing, Closed) are translated to Pipedrive stage names via value‑mapping. The mapping preserves the original stage labels where possible, allowing your team to recognize the workflow in Pipedrive.

Trialworks user accounts are resolved by email match against Pipedrive users. Unmatched users are flagged before migration; the client either invites them to Pipedrive or assigns their records to a fallback owner. No record lands in Pipedrive without an owner.

Trialworks workflows and automation rules tied to case events have no equivalent in Pipedrive's automation model. We export workflow definitions as a structured JSON document that your Pipedrive admin can use as a rebuild reference in Pipedrive Automations and Sequences.