Data migration route
PracticeMaster to Rocket Matter migration
PracticeMaster is a server-based 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.
PracticeMasterServer- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Emails: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Intake: Carried with mapping
Rocket MatterCloud- 7 carried
- 4 mapped
What moves
What moves from PracticeMaster to Rocket Matter
Each row is a kind of record PracticeMaster holds, whether Rocket Matter has a place for it, and what is planned. On this route seven kinds of record carry across and four kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClient file mirrored with Tabs3 Billing, one record per Client ID. | Has a placeMatter File # and matter name are required on import. | Carried across |
| ContactsClients, other parties and referrers | Held | Has a placeImported as clients or as other contact types. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldDocument Management records link files to a client or contact, with check-out and versions. | Has a placeNative storage, or a linked OneDrive, Dropbox, Box or NetDocuments account. | Carried across |
| EmailsEmails saved to matters or to the store | HeldEmail records in the Journal, created through the Outlook integration. | 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 notes | HeldNote, phone call and research records in the Journal. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | HeldFirm-wide calendar with Outlook integration and calendar plan templates. | Has a place | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTasks and reminders on the calendar. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | Held in partTimer records and fees that pass to Tabs3 Billing. | Has a placeUnbilled time and expenses load from a financial import sheet, keyed to the matter. | Carried across |
| Custom fieldsFields and record types the firm added itself | HeldAreas of Practice with the firm’s own files and fields. | Has a placeCustom fields and custom pages on contacts and matters. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument assembly with Word or HotDocs, WorkFlows and calendar plan templates. | Has a place in partWord merge templates are rebuilt with the product’s own merge fields. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partTabs3 CRM handles leads and intake and passes them to PracticeMaster. | 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 PracticeMaster.
- 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.
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 PracticeMaster. 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.
PracticeMaster runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Rocket Matter is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving PracticeMaster
PracticeMaster is the part of Tabs3 that looks most like other practice systems, and the part firms have customised most. Contacts, calendar and journal records move in a familiar way. The detail is in the Areas of Practice the firm built, the documents it linked, and the WorkFlows it depends on, none of which have the same shape in another product.
Areas of Practice are tables
Each Area of Practice has its own files, and firms add files and fields through File Maintenance. A probate area might hold assets and heirs, a family area children and hearings. These can hold many rows for one matter. Every file is listed with its row counts, and each needs a home or a decision.
The Journal mixes record types
Timer records, phone calls, emails, research and notes are all stored in one Journal file, told apart by a record type. Destinations usually split those into time entries, emails and file notes. Journal records are sorted by type on the way out, so a timer record already billed is not loaded a second time as a note.
Documents are linked, with versions
The Document Management file links documents to a client or contact, with check-out, check-in and versions. Each record is only the link, and the document is a file on the firm’s storage. PracticeMaster has its own verify function for these links, and it is run before extraction so broken ones are known.
Template paths by practice area
Document assembly templates sit in a Template Path for each Area of Practice, by default a DOCS folder under that area, and may be Word or HotDocs templates. Their merge codes refer to PracticeMaster fields. Templates are rebuilt against the new system’s fields, starting with the ones produced most often.
WorkFlows and calendar plans
WorkFlows fire when records are added or changed, and calendar plan templates lay down a series of dated events. Events already created come across as calendar entries. The automation itself is described and rebuilt with the destination’s own tools, because rules do not transfer between products.
Where it is going
Arriving in Rocket Matter
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.
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.
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.
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.
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.
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.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover.
Analysis
We read what PracticeMaster 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.
Clean-up
Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in PracticeMaster, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Rocket Matter as a trial and checked against PracticeMaster: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in PracticeMaster 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 PracticeMaster as at the cutover date. PracticeMaster 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 PracticeMaster 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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what PracticeMaster 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.
- 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
PracticeMaster to Rocket Matter: what firms ask
Do emails saved from Outlook come across?
Emails saved through the Outlook integration become journal records on the client. They are loaded to the matter as emails where the destination has an email record, otherwise as dated notes with the message saved as a file.
We want to keep PracticeMaster and replace billing. Is that possible?
The two are tied by mirrored client files and only integrate when installed together. Replacing Billing alone breaks the flow of fees from PracticeMaster. If the plan is to split them, the analysis sets out the manual steps that would stand in for the link, and what they cost in staff time.
What happens to conflict searching?
Conflict searching in PracticeMaster reads the fields the firm marked for it, across clients, contacts and linked documents. After the move, searches run in the new system over the migrated contacts and matters. Names that lived only in free text or old documents are worth a check, since they may not be indexed the same way.
Do documents from PracticeMaster keep their folders and dates in Rocket Matter?
Rocket Matter stores documents. Native storage, or a linked OneDrive, Dropbox, Box or NetDocuments account. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.
Does everything in PracticeMaster have a place in Rocket Matter?
On paper, yes: each kind of record PracticeMaster holds has a place in Rocket Matter. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.
What has to be decided before PracticeMaster data is loaded into Rocket Matter?
Emails, custom fields, templates and intake records are carried with mapping, so each mapping is agreed with you first. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from PracticeMaster and into Rocket Matter
Other destinations from PracticeMaster
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
PracticeMaster and Rocket Matter are the names and marks of their owners, used here only to identify the two systems.
Moving from PracticeMaster 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.