Migrate from Rocket Matter to HighLevel

Rocket Matter clients map directly to HighLevel contacts. Email, phone, address, and custom contact fields transfer as-is. A client's matters attach to the contact record via opportunity associations. Unassigned clients (no matter history) land as standalone contacts. FlitStack matches client email addresses to existing HighLevel contacts, creating a link when a match is found and flagging duplicates. Original creation timestamps are preserved in the contact record's dateAdded field.

Rocket Matter matters become HighLevel opportunities. Matter name maps to Opportunity name; matter status (Active, Pending, Closed) maps to pipeline stage values. Multiple Rocket Matter attorneys on one matter create Opportunity Contact Roles in HighLevel. Matter type (practice area) migrates as a custom field for segmentation.

Rocket Matter matter templates (structured task sequences per practice area) do not migrate — they require manual rebuild in HighLevel's Pipeline builder. We export template names and task lists as a reference document your admin can replicate in HighLevel's Workflow section.

Rocket Matter bills and invoices have no native HighLevel equivalent. Bill amount, invoice date, status (Paid, Unpaid, Overdue), and payment method transfer as custom fields on the opportunity record. The invoice line items export as a reference CSV for rebuild in HighLevel's Products or a connected billing tool.

Individual time entries (date, duration, description, billable flag) transfer as a JSON blob or structured custom field on the related opportunity. For firms needing granular time tracking in HighLevel, we surface time entry totals per matter as read-only custom fields — actual time tracking requires manual log entry or a third-party integration.

Rocket Matter's legal trust accounting (IOLTA accounts, client trust balances, trust transactions) has no HighLevel equivalent. Trust balance, account type, and last reconciliation date migrate as read-only custom fields on the contact for reference. The firm must handle trust accounting in a separate legal-specific tool post-migration.

Rocket Matter tasks (assigned to, due date, priority, status) map to HighLevel tasks. Task dependencies in Rocket Matter do not transfer — HighLevel's task model does not support dependency chains natively. We flag dependency-linked tasks for manual rebuild as HighLevel Workflow tasks if critical.

Rocket Matter documents attached to matters re-upload to the related contact or opportunity in HighLevel Files. File size limits apply — HighLevel supports standard file attachments per record. Documents originally stored in NetDocuments, Dropbox, or Box require re-link or re-upload to HighLevel's file storage.

Rocket Matter calendar events (court dates, client meetings, deadlines) map to HighLevel calendar events with original date, time, and attendee information preserved. Events without attendees migrate as tasks with due dates. Recurring events are transferred with their frequency and end date, while location and reminder settings become HighLevel event metadata. If an event lacks a contact link, FlitStack attaches a placeholder contact to maintain data integrity.

Rocket Matter notes attached to matters or clients migrate to HighLevel notes on the related contact or opportunity record. Original author and create date transfer. Rich-text formatting in Rocket Matter notes may flatten to plain text during export. Note tags and categories are exported as plain‑text labels attached to the note body, and any embedded file links are recorded as URLs for manual re‑attachment if needed.

Rocket Matter Contact Custom Fields (per the KB article on screenstepslive) map 1:1 to HighLevel Contact Custom Fields. Field type (text, select list, date, number) is preserved. Select list options map value-by-value; we flag any option that exceeds HighLevel's character limits.

Rocket Matter Matter Custom Fields map to HighLevel Opportunity Custom Fields. Fields configured as 'Is default' in Rocket Matter are flagged in the migration plan so your admin can re-enable defaults in HighLevel's Custom Fields settings. Field type (text, number, date, select list) is preserved during transfer, and select list options map value‑by‑value. Any option exceeding HighLevel's character limit is flagged for manual review before final import.