Migrate from Rocket Matter to Pipedrive

Rocket Matter Clients map directly to Pipedrive People. The Client's primary email becomes Person.Email, primary phone becomes Person.phone, and the client name maps to Person.name. Clients without email are flagged for manual review before migration — Pipedrive requires an email for some automation triggers.

If a Rocket Matter Client has an associated firm or company name beyond the individual client name, that organization data maps to a Pipedrive Organization. Each Person in Pipedrive is then linked to its primary Organization via the Person.org_id field.

Rocket Matter Matters are the core legal work unit. Each Matter maps to a Pipedrive Deal — Matter.name becomes Deal.title, Matter.status maps to a Deal.stage via value mapping (Open, Pending, Closed Won, Closed Lost), and Matter.matter_number is preserved as a custom field on the Deal. If your firm uses multiple matter types, each type may warrant its own Pipedrive pipeline.

Rocket Matter's matter status values (Open, Pending, On Hold, Closed) map to Pipedrive Deal stage values. The mapping is value-by-value: each Rocket Matter status label is assigned to a corresponding Pipedrive stage. Stage-entered timestamps in Rocket Matter are preserved as custom datetime fields on the Deal.

Rocket Matter matter templates define a repeatable structure for new matters. In Pipedrive, each matter template becomes either a Pipeline or a custom field on the Deal — your team chooses whether to model template type as separate Pipedrive pipelines or as a Deal.custom_matter_template field. Template tasks and phase transitions do not migrate automatically.

Rocket Matter tasks attached to matters map to Pipedrive Activities. The task subject becomes Activity.subject, due date maps to Activity.due_date, and assigned user maps to Activity.user_id. Completed status, notes, and time logged against the task are preserved as custom fields on the Activity record.

Rocket Matter time entries record billable hours per matter. Aggregated time-entry totals (hours logged, total billed amount) migrate as custom number/currency fields on the Pipedrive Deal representing that matter. Individual time-entry line items are preserved as a linked custom object or as notes on the Deal for audit purposes.

Rocket Matter client custom fields (created via Tools > Manage Custom Fields) map to Pipedrive custom fields on the Person object. Field types are matched: select-list fields become Pipedrive select fields, text fields become varchar fields, date fields become date fields. The Pipedrive field key (a 40-character hash) is assigned at creation time and used in API calls.

Rocket Matter matter custom fields map to Pipedrive custom fields on the Deal object. Multi-select list values in Rocket Matter are stored as concatenated strings in Pipedrive unless your Pipedrive plan supports multi-select fields. We flag multi-select fields before migration and present mapping options.

Rocket Matter notes attached to matters migrate as Pipedrive Notes linked to the corresponding Person or Deal. The note body, author, and creation timestamp are preserved. Notes are imported via Pipedrive's Notes API endpoint with the linked Person or Deal ID as the parent reference.

Rocket Matter's trust accounting tracks client funds held in IOLTA accounts. This has no Pipedrive equivalent. We preserve the trust-account status (Active Trust, No Trust, etc.) as a custom pick-list field on the Person or Organization so the billing team can see it during client intake without rebuilding trust tracking inside Pipedrive.

Rocket Matter users (attorneys, paralegals, staff) are matched to Pipedrive users by email address. Unmatched Rocket Matter users are flagged — your Pipedrive admin creates the user first, then the migration assigns records. Owner resolution on Deals uses the matched Pipedrive user ID.