Migrate from Rocket Matter to Mailchimp

Rocket Matter Clients are legal entities (individuals or companies) that own one or more matters. Each Client maps to one or more Mailchimp Subscribers — if the client is a company, the primary contact person within that client migrates as a subscriber. Company-level billing and trust data has no Mailchimp equivalent and is not migrated.

Rocket Matter Contact records (individual people linked to a client) map 1:1 to Mailchimp Subscribers within a designated audience. Each contact's email address becomes the Mailchimp subscriber email — this is the required unique identifier. Phone, address, and name fields map to standard Mailchimp merge fields FNAME, LNAME, PHONE, and ADDRESS.

Rocket Matter Client Custom Fields (select lists, text fields, date fields) migrate as Mailchimp Merge Fields within the target audience. We create each merge field via the Mailchimp API before importing records. Select-list fields map as dropdown merge fields with the same pick-list values; text fields map as text merge fields; date fields map as date merge fields.

Rocket Matter practice area labels (Family Law, Criminal Defense, Estate Planning, Personal Injury, etc.) do not have a direct Mailchimp equivalent. We map each practice area to a Mailchimp Tag applied to the subscriber at import time. Alternatively, these can become a 'PracticeArea' merge field pick-list so segments can filter subscribers by legal service type.

Rocket Matter Matters (legal cases with status, assigned attorney, open date, and billing records) have no Mailchimp equivalent. We surface the Matter ID and Matter Name as reference merge fields on the subscriber record so you can manually cross-reference Mailchimp contacts back to their Rocket Matter matters. Legal case data itself stays in Rocket Matter or is exported as a separate reference report.

Rocket Matter time entries track billable hours against matters. Mailchimp has no time-tracking or billing model. Time entries are not migrated. If billing history export is required, we can generate a CSV report from Rocket Matter data separate from the Mailchimp migration.

Rocket Matter invoices, trust account balances, and payment records are legal-specific financial data with no Mailchimp equivalent. These records remain in Rocket Matter and must continue to be accessed there for billing and accounting purposes. We do not migrate billing data to Mailchimp as Mailchimp is not a financial system. If needed, we can export a CSV summary of client billing totals (total billed, outstanding balance, last payment date) as a reference file to store alongside your Mailchimp subscriber records.

Rocket Matter documents and file attachments (contracts, court filings, correspondence) stored against matters or contacts have no Mailchimp equivalent. Mailchimp supports file attachments in campaigns but not document management — it has no document library, versioning, or access-control features. Documents remain in Rocket Matter or your existing document storage integration. If you need document references accessible in Mailchimp, we can add a document reference URL as a custom merge field on the subscriber record.

Rocket Matter calendar events and court dates have no Mailchimp equivalent. Mailchimp's Customer Journeys can trigger emails based on subscriber actions (tag applied, date merge field reached) but cannot import or display a legal calendar. Court date reminders can be rebuilt as Customer Journey automations in Mailchimp by setting up date-based triggers matching your court calendar dates.

Rocket Matter users (attorneys, paralegals, admins) are not Mailchimp contacts. If attorney email addresses need to be in Mailchimp for internal newsletters, they can be added manually or via a separate import. Owner resolution by email match is not applicable in this migration direction.

Rocket Matter tasks with dependencies and assignments are practice management constructs with no Mailchimp equivalent. Tasks are not migrated. If you use Mailchimp automations for client communication triggers, tasks can be recreated as Customer Journey entry points. For example, a matter status change in Rocket Matter can trigger a corresponding tag application that starts a Mailchimp Customer Journey sequence.

Rocket Matter matter status values (Active, Pending, Closed) map to Mailchimp tags applied at import. Active clients get an 'Active-Matter' tag; closed matters get 'Closed-Matter'. This allows you to create Mailchimp segments for different client communication cadences based on matter status.