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

Data migration route

Litify to Rocket Matter migration

Litify is a cloud case management system, and Rocket Matter is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in Rocket Matter, often from a separate accounts package.

FromLitifyCloud
  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. Emails: Carried with mapping
  8. Billing: Carried with mapping
  9. Custom fields: Carried with mapping
  10. Templates: Carried with mapping
  11. Intake: Carried with mapping
  12. Notes: Confirmed in the analysis
  13. Trust money: Confirmed in the analysis
  14. Firm accounts: Confirmed in the analysis
ToRocket MatterCloud
  • 6 carried
  • 5 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Litify to Rocket Matter

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

Records in Litify and their place in Rocket Matter
RecordIn LitifyIn Rocket MatterWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters, with parties, calendar events, tasks, time and costs attached.Has a placeMatter File # and matter name are required on import.Carried across
ContactsClients, other parties and referrersHeldParties, connected to intakes and matters through roles.Has a placeImported as clients or as other contact types.Carried across
DocumentsFiles stored in or linked from the systemHeldHeld in Litify’s document component, with tags, versions and templates.Has a placeNative storage, or a linked OneDrive, Dropbox, Box or NetDocuments account.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails appear on the case activity timeline. Mailboxes stay in the mail system.Has a place in partEmails can be filed to matters; it does not hold whole mailboxes.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldCalendar events on the matter and the activity timeline.Has a placeCarried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks, including those generated by matter plans.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldTimekeeping, with time entries tied to the matter.Has a placeUnbilled time and expenses load from a financial import sheet, keyed to the matter.Carried across
BillingInvoices, payments and debtor balancesHeldBilling and eBilling, aimed chiefly at insurance defence work.Has a place in partOpen balances are supported; how much invoice history loads is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeBank accounts are created first; ledger history depth is agreed in the analysis.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedHas a place in partNextGen has a chart of accounts and journals; prior-year ledger detail is confirmed first.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldFields are added through Salesforce configuration.Has a placeCustom fields and custom pages on contacts and matters.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates with conditional logic. Matter plans automate tasks.Has a place in partWord merge templates are rebuilt with the product’s own merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntakes with questionnaires, lead scoring and marketing source tracking.Has a place in partIntake forms exist; loading open leads is confirmed in the analysis.Carried with mapping

What the plans mean

Carried across
Rocket Matter has a place for this kind of record. It is loaded there and checked against Litify.
Carried with mapping
Rocket Matter 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

Cases come across. The accounts are set up new.

A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to Rocket Matter brings those two sources together. The case records come from Litify. Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.

Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in Rocket Matter, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Litify 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 Litify is kept running until the checks on Rocket Matter are finished.

Where the data is now

A firm leaving Litify is leaving a Salesforce environment that has usually been shaped by an implementation team and several years of administrators. Its data is all there and can be queried. The effort is in reading the configuration, separating Litify’s own objects from the firm’s additions, and collecting the documents, which are managed by a separate component.

  1. Parties and roles

    A person or company is a party, and a role ties that party to an intake or matter as client, defendant, insurer, provider or something the firm defined. One party can hold different roles on different matters. Roles are extracted with the party, so the destination gets one contact with its relationships and not a copy per matter.

  2. Intakes become matters

    An intake is its own record with a questionnaire and a status, converted to a matter when the client signs. Turned-down and referred-out intakes stay as intakes and can far outnumber matters in a high-volume practice. They are counted separately, and the firm decides how many go to the new system.

  3. Documents sit beside the records

    Files are managed by Docrio, Litify’s document component. How they are stored, and how a full copy is obtained, is established in the analysis. Records and files are generally extracted by different routes and joined on the matter. Counts are checked per matter after the join, including on closed matters.

  4. Injury detail in related records

    Plaintiff firms typically record damages, insurance, liens, negotiations and settlement figures in records related to the matter, and each firm names and extends them its own way. These lists are extracted as tables with the matter reference. Where the destination has no equivalent, each becomes a schedule saved to the matter.

  5. Automation stays behind

    Matter plans, flows and validation rules are Salesforce configuration. They explain why the data looks the way it does, for example why a field is always filled at a given stage, but they cannot be exported into another product. Each is documented and used as the specification for workflows in the destination.

More about moving off Litify

Where it is going

This describes loading into Rocket Matter NextGen, the platform the vendor’s website now presents. Its import runs in a fixed order: contacts, then matters, then time, expenses and balances. The vendor’s import sheets show what each record must carry. Most of the preparation is giving every matter a file number and getting the accounting set-up finished before any financial record goes in.

  1. A file number on every matter

    Matter File # and matter name are the two required fields. The file number is also the key that time, expenses and balances are matched to on the way in. Source matters with no number, or with numbers reused across clients, are given clean ones before the trial load and the old value is kept in a custom field.

  2. Clients and address-book contacts

    A contact is either a client, who can have matters, or an address-book contact such as an opposing lawyer or an expert. Source systems that hold everyone in one list need each record classified. A person who is a client on one matter and a witness on another is loaded once, as a client.

  3. Accounting set-up comes first

    Timekeepers, matter owners, bank accounts and the chart of accounts must exist before financial data is imported, and the client and matter records must already be in place. The trial load follows that order. Time recorded by people who have left still needs a timekeeper to belong to, so former staff are added before their entries are loaded.

  4. Pick the document store early

    Documents can sit in native storage or in a linked OneDrive, Dropbox, Box or NetDocuments account. With a linked account, the system creates a folder for each matter, named from the file number, client and matter name. Changing that pattern later only affects new matters, so it is settled before the load.

  5. One ledger of record

    NextGen has its own chart of accounts, journal entries and bank reconciliation, and it can also sync with QuickBooks Online from a chosen start date. A firm should run one of them as its books. That decision shapes how opening trust and debtor balances are entered, and the accountant is part of it.

More about moving into Rocket Matter

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  1. Analysis

    We read what Litify holds and how its records link, then agree with you, field by field, where each piece will sit in Rocket Matter. 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 Litify, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

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

  4. Cutover

    Changes in Litify are frozen for an agreed window, the data is collected a final time and Rocket Matter 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 Litify as at the cutover date. Litify 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 Litify 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 fromLitify
Moving toRocket Matter

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 Litify holds

    What is in it, how its records link, and where each piece would sit in Rocket Matter. 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 Rocket Matter

Loaded data is not yet a working system. This is what NewLaw sets up in Rocket Matter, beyond the migration, so that people can work in it from the first day.

Beyond the data, a firm starting on Rocket Matter has a set of choices that are awkward to change once people are billing. Who the timekeepers and matter owners are, how matters are numbered, which bank accounts exist and whether the books run inside the product or in QuickBooks Online all need an answer before go-live. Matter templates and Word merge documents are then built on top.

Set-up decisions in Rocket Matter

  • Timekeepers, matter owners and the rates each one bills at
  • Matter File number format and matter templates by work type
  • Bank accounts, chart of accounts and the QuickBooks Online decision
  • Custom fields and custom pages for contacts and matters
  • Document storage choice and the matter folder naming pattern
  • Word merge templates, invoice layouts and intake forms

Questions

Litify to Rocket Matter: what firms ask

Do we need a Salesforce administrator to get our data out?

Someone with administrator access is needed, yes. The extraction reads the environment’s objects directly, and the administrator grants that access and explains what was customised. If the person who built it has left, the configuration is read from the system itself, which takes longer.

Are our documents included when Litify data is exported?

Do not assume so. Documents are managed by a separate component, and an export of matter records should not be expected to contain the files themselves. Both routes are covered in the plan and joined on the matter. A matter is only counted as moved when its files are attached to it.

We are moving to Litify. Who does the configuration?

Litify or one of its implementation partners normally configures the system. The migration fits into that project: the data mapping follows their design, and trial loads go into a test environment before production. It helps to agree early who owns the field list, because data and configuration change each other.

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

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 Litify before the plan is fixed. If Rocket Matter 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 Litify have a place in Rocket Matter?

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 Rocket Matter is kept as a readable archive, and you see which before the move.

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

Emails, billing records, custom fields, templates and intake records 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

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

Moving from Litify to Rocket Matter?

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

We reply within one business day.