Migrate from Rocket Matter to Twenty CRM

Rocket Matter clients store individual contacts linked to matters. We map each client to a Twenty Person record, preserving full name, email, phone, and address fields. Primary matter association is recorded on the Person record via a custom field or Opportunity link.

When a Rocket Matter client has an organization name (law firm, corporate client), that organization maps to a Twenty Company record using the domain or firm name as the unique key. Each Person links to its primary Company via Twenty's standard companyId relation.

Rocket Matter matters are legal cases with stages, assigned attorneys, billing rates, and documents attached. We map matters to Twenty Opportunities because both track a progression toward a goal (case close vs. deal win). Matter stage maps to Opportunity stage pick-list values. Custom matter-type fields become Twenty custom fields on the Opportunity.

Rocket Matter matter custom fields (e.g., practice area, court jurisdiction, opposing counsel) have no direct Twenty equivalent. We create matching custom fields on the Twenty Opportunity object using the same field type (select, text, date, etc.) so the data is preserved and queryable.

Rocket Matter client custom fields (e.g., referral source, bar number, conflict status) map to custom fields on the Twenty Person object. We replicate the field type and pick-list values so the data transfers without loss. This ensures that all client-specific metadata is preserved and remains searchable in the new system.

Both platforms have task objects. We map Rocket Matter tasks to Twenty Tasks, preserving the parent record link (matter or client), due date, assignee, and completion status. Kanban task categories from Rocket Matter map to a custom select field on Twenty Tasks.

Rocket Matter calendar events (depositions, hearings, client meetings) map to Twenty Tasks with a custom event-type field because Twenty has no native calendar object. Original start/end times are stored as custom datetime fields for reference. This approach preserves scheduling context while adapting to Twenty's data structure limitations.

Rocket Matter notes attached to matters or clients map to Twenty Notes. We preserve the note body, author (via owner email match), create date, and the parent record link so the full matter context is visible in Twenty. This maintains the historical record and ensures continuity of client communications and matter discussions.

Rocket Matter documents (contracts, briefs, exhibits) have no native equivalent in Twenty's data model. We export file metadata (filename, upload date, linked matter) and re-upload documents to Twenty as Notes with file attachments. File bodies themselves are re-hosted since Twenty has no document storage module.

Rocket Matter trust accounting (IOLTA accounts, client fund tracking, trust ledgers) has no Twenty CRM equivalent. We export trust account balances and transaction history as a CSV audit file for import into separate accounting software. This gap is disclosed upfront—no trust data migrates into Twenty's object model.

Rocket Matter invoices, batch bills, and payment records do not map to Twenty CRM. We export invoice headers, line items, and payment history as CSV for reconciliation in your chosen billing tool. The invoice-to-payment history is preserved but must be reviewed manually post-migration.

Rocket Matter user accounts (attorneys, paralegals, admins) are matched to Twenty Workspace Members by email address. Unmatched users are flagged before migration so the team can invite them to Twenty first. Role mapping (attorney vs. paralegal) becomes a custom field on the Workspace Member.

Rocket Matter matter templates (e.g., Personal Injury Intake, Real Estate Closing) provide pre-populated task lists and custom field defaults. Twenty has no template feature at the Opportunity level. We export template structures as documentation for manual rebuilding in Twenty. This provides a clear blueprint for recreating standardized matter workflows in the new system.

Rocket Matter automations (task triggers, billing alerts, matter-stage actions) do not migrate. We export automation definitions as a structured JSON file that documents trigger conditions and actions, which your team uses to rebuild logic in Twenty's workflow builder or a separate automation tool.

Rocket Matter supports LEDES 1998B and LEDES XML billing codes for insurance and corporate clients. Twenty has no LEDES support. We preserve LEDES code assignments on time entries as a custom text field for reference, but billing codes must be managed in a separate LEDES-compliant tool.