Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

Rocket Matter to Litify migration

Rocket Matter is a cloud practice management system, and Litify is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.

FromRocket MatterCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Calendar: Carried across
  5. Tasks: Carried across
  6. Time and expenses: Carried across
  7. Intake: Carried across
  8. Emails: Carried with mapping
  9. Billing: Carried with mapping
  10. Custom fields: Carried with mapping
  11. Templates: Carried with mapping
  12. Notes: Confirmed in the analysis
  13. Trust money: Confirmed in the analysis
  14. Firm accounts: Confirmed in the analysis
ToLitifyCloud
  • 7 carried
  • 4 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Rocket Matter to Litify

Each row is a kind of record Rocket Matter holds, whether Litify has a place for it, and what is planned. On this route seven kinds of record carry across, four kinds need mapping and three kinds are confirmed in the analysis.

Records in Rocket Matter and their place in Litify
RecordIn Rocket MatterIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldEach matter sits under a client. Completed and closed are separate states.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldContacts carry custom fields and tags.Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemHeldHeld in Rocket Matter or synced two ways with Box, Dropbox, OneDrive or NetDocuments.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails brought in through the Office 365 or IMAP connection can be saved to a matter.Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesHeldTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldTwo-way sync with Google Calendar and Outlook.Has a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldMatter templates create tasks and events; there is a Kanban view.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldHas a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldPrebills, batch billing and LEDES invoices; each matter has a Matter Ledger.Has a place in partBilling is part of the product. Loading past invoices is scoped in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTo be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeld in partOriginal platform relies on QuickBooks Online; NextGen has a general ledger built in.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldClient, matter and contact custom fields.Has a placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates with merge fields, and matter templates.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partLeads and intake are handled in a CRM module.Has a placeLoaded as intakes.Carried across

What the plans mean

Carried across
Litify has a place for this kind of record. It is loaded there and checked against Rocket Matter.
Carried with mapping
Litify holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
Confirmed in the analysis
We could not confirm this from the two products’ own material, so it is checked against your data before the plan is fixed.

The table states what the two products hold and what NewLaw plans for. It is not a promise that every record moves: that is settled against your own data in the analysis.

This kind of move

Matters become cases. The ledgers need a home.

Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Litify. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.

Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from Rocket Matter has to be given a case type in Litify, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Litify is exported as reports and ledgers the firm can open without Rocket Matter, and kept as the record of what was billed and held.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Rocket Matter depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Rocket Matter is kept running until the checks on Litify are finished.

Where the data is now

This describes leaving the original Rocket Matter platform; NextGen is covered separately. The move is mostly a matter of tracing things that Rocket Matter lets a firm set up in more than one way. Matter numbers may be buried in matter names. Documents may be in Dropbox, not in the product. The books are in QuickBooks Online. Each of those is traced during the analysis so the trial load is built from the right source.

  1. Completed is not closed

    A completed matter is finished but still open for billing. Closed means inactive: the matter takes no time entries and does not appear in the global search bar. Most destinations have only open and closed. Completed matters with money outstanding are loaded as open and flagged, so the accounts team can still bill and collect on them.

  2. Numbers inside the name

    Matter Naming builds each matter’s name from parts such as a client number, the client’s surname and a running matter number. A separate matter number field exists only where the custom number feature was switched on. Where it was not, the number is pulled out of the name text and checked for gaps and repeats.

  3. QuickBooks holds the books

    The sync sends clients to QuickBooks Online as customers, matters as sub-customers and practice areas as classes, with journal entries for fees, payments and trust movements. QuickBooks can simply stay as it is. What changes is the feed into it, so the last synced date is agreed and recorded at the freeze.

  4. Balances on the Matter Ledger

    Opening balances in Rocket Matter were often entered as debit or credit adjustments on the Matter Ledger, not as invoices. Those adjustments have no invoice number behind them. They are listed with their descriptions in the analysis, because a destination that expects every debtor balance to belong to an invoice needs one created.

  5. Files may be in Dropbox

    With the two-way Box, Dropbox or OneDrive integration, each matter’s folder also exists in the firm’s own storage account. The analysis compares what Rocket Matter lists with what is in that account. Sometimes the cleanest source for documents is the storage account itself, with Rocket Matter supplying the matter each folder belongs to.

More about moving off Rocket Matter

Where it is going

Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.

  1. The design comes first

    Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.

  2. One party, many roles

    Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.

  3. Open enquiries load as intakes

    Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.

  4. Documents load after records

    Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.

  5. Validation rules reject bad rows

    A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.

More about moving into Litify

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Litify says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Rocket Matter and checking each trial against Rocket Matter.

  1. Analysis

    We read what Rocket Matter holds and how its records link, then agree with you, field by field, where each piece will sit in Litify. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Rocket Matter, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Litify as a trial and checked against Rocket Matter: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Rocket Matter are frozen for an agreed window, the data is collected a final time and Litify goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in Rocket Matter as at the cutover date. Rocket Matter is kept read only as the fall-back record.

Fixed price, agreed after the analysis. How NewLaw moves legal data

Start

Start this migration

Tell us what is in Rocket Matter and roughly how much of it. The first step is the analysis, and the price is fixed once it is done.

Step 1 of 5

Step 1 of 5: Start with the route

Moving fromRocket Matter
Moving toLitify

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what Rocket Matter holds

    What is in it, how its records link, and where each piece would sit in Litify. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. A fixed price in writing

    Set after the analysis, so it reflects what is in your data. You have it before any work starts.

Beyond the data

Setting up Litify

Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.

A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.

Set-up decisions in Litify

  • Define intake questionnaires and the rules for conversion
  • Set case types, matter stages and page layouts
  • Build matter plans that create tasks at each stage
  • Design document folders and generation templates per case type
  • Configure user roles and sharing for restricted matters
  • Decide on timekeeping, billing and accounting integrations

Questions

Rocket Matter to Litify: what firms ask

How do we know whether we are on the original Rocket Matter or NextGen?

The quickest sign is accounting. If the firm keeps a chart of accounts and reconciles its bank accounts inside Rocket Matter, it is on NextGen. Books in QuickBooks Online, with a Matter Stream and a Matter Ledger on each matter, point to the original platform. The analysis confirms it either way.

What happens to posts in the Matter Stream?

The stream itself is a view of tasks, events, notes, documents and billable entries, and those move as their own records. Messages staff typed into the stream are different. They have no counterpart in most systems, so they are carried as dated notes on the matter.

Can our existing matter numbers be used as the Matter File # in a new account?

Usually, provided each one is unique. The file number is what later imports of time and balances are matched against, so duplicates have to be resolved first. Firms whose old numbers restart for each client often combine the client number and matter number into one value.

Do trust balances in Rocket Matter have a place in Litify?

That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Rocket Matter before the plan is fixed. If Litify turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

Does everything in Rocket Matter have a place in Litify?

Most of it does on paper. Notes, trust ledgers and the firm’s accounts could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Litify is kept as a readable archive, and you see which before the move.

What has to be decided before Rocket Matter data is loaded into Litify?

Emails, billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes, trust ledgers and the firm’s accounts are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.

Where to start

Before and after the move.

Choosing the system comes before a migration. Setting it up and putting AI to work come after.

How we do itDiscovery to rollout, step by step

Rocket Matter and Litify are the names and marks of their owners, used here only to identify the two systems.

Moving from Rocket Matter to Litify?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.