Migrate from MerusCase to Pipedrive

MerusCase case files map directly to Pipedrive Deals. The case number becomes a Pipedrive deal custom field (Case_Number__c) so staff can cross-reference records. Case status (Open/Closed) maps to Pipedrive's deal stage, with the final stage representing closed matters.

MerusCase parties with contact roles (Plaintiff, Defendant, Contact) map to Pipedrive People. The party role is preserved as a custom pick-list field (Party_Role__c) on the Person record. Multiple parties per case become separate Person records linked to the same Deal via Deal-Person association.

MerusCase parties that are law firms or corporate legal departments map to Pipedrive Organizations. The firm's name and contact information populate the Organization record; the party's address and phone migrate to the Organization's standard address and phone fields.

MerusCase activities with types (Call, Meeting, Filing, Statute, General Note) map to Pipedrive Activities using the same type labels where available. Original timestamps, assigned staff, and activity descriptions are preserved. Each activity is linked to the corresponding Deal.

MerusCase custom fields are recreated as Pipedrive dealFields via the /dealFields API. Field type is matched: MerusCase Currency maps to Pipedrive monetary, Date maps to date, Numeric maps to integer or varchar depending on precision. MerusCase Yes/No maps to a Pipedrive set of choices (Yes/No).

Ledger entries with task codes (UTBMS L-Code, A-Code, E-Code) are summarized on the Deal as custom fields tracking total billed time and expenses. Individual ledger entries are preserved as Pipedrive Activity records with the task code in the activity subject so the detailed billing history remains accessible.

Settlement amount and date migrate as Pipedrive deal fields (Settlement_Amount__c, Settlement_Date__c). The deal moves to a designated 'Settled' stage. Settlement terms stored as free-text custom fields on the deal record.

MerusCase documents linked to a case file are downloaded and re-uploaded as Pipedrive deal attachments. File size limits apply (Pipedrive allows up to 50MB per file). Large Document Archives from MerusCase are delivered as ZIP packages linked from a custom deal field pointing to the download URL.

MerusCase staff members are matched to Pipedrive users by email address. Unmatched staff are flagged before migration so the firm can create Pipedrive accounts or assign records to a fallback user. Each staff member's case assignments become Pipedrive deal owner assignments.

MerusCase Workflows triggered by activity tag or description text have no direct equivalent in Pipedrive. FlitStack exports the full workflow definition (trigger rules, actions, assigned staff) as a JSON specification. A Pipedrive admin rebuilds these as Pipedrive Automations using the exported definition as a reference guide.

MerusCase Statute records (filing deadlines tied to a calendar date) become Pipedrive Activities with the filing date as the due date and the statute name as the subject. Pipedrive Automations (Advanced plan and above) recreate deadline reminders based on the statute date and assigned staff.

MerusCase case types (Workers' Comp, Personal Injury, Criminal, Employment) map to separate Pipedrive Pipelines. Each pipeline has its own stage set reflecting the legal process for that practice area. Pipeline assignment is set via a Practice_Area__c custom field during ingestion.