Data migration route
Tabs3 to Rocket Matter migration
Tabs3 is a server-based practice management system, and Rocket Matter is a cloud one. Both run a whole practice, so this is a full move, and the financial records set the timetable.
Tabs3Server- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Trust money: Carried across
- Emails: Carried with mapping
- Billing: Carried with mapping
- Firm accounts: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Intake: Carried with mapping
Rocket MatterCloud- 8 carried
- 6 mapped
What moves
What moves from Tabs3 to Rocket Matter
Each row is a kind of record Tabs3 holds, whether Rocket Matter has a place for it, and what is planned. On this route eight kinds of record carry across and six kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldA matter is the part of the Client ID after the decimal point. | 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 | Held in partPracticeMaster links documents to clients and contacts. | Has a placeNative storage, or a linked OneDrive, Dropbox, Box or NetDocuments account. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partPracticeMaster keeps email records in its Journal. | 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 | Held in partNote, phone and research records in the PracticeMaster Journal. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | Held in partIn PracticeMaster. | Has a place | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held in partIn PracticeMaster. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldIn Tabs3 Billing, with timers in PracticeMaster. | Has a placeUnbilled time and expenses load from a financial import sheet, keyed to the matter. | Carried across |
| BillingInvoices, payments and debtor balances | HeldIn Tabs3 Billing. | 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 balances | Held in partWith the Trust Accounting module. | Has a placeBank accounts are created first; ledger history depth is agreed in the analysis. | Carried across |
| Firm accountsGeneral ledger, office account and payables | Held in partWith the General Ledger and Accounts Payable modules. | Has a place in partNextGen has a chart of accounts and journals; prior-year ledger detail is confirmed first. | Carried with mapping |
| Custom fieldsFields and record types the firm added itself | Held in partPracticeMaster Areas of Practice carry 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 | Held in partDocument assembly in PracticeMaster; statement layouts in Billing. | 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 covers leads and intake and works with 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 Tabs3.
- 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
The whole practice moves, accounts included.
Tabs3 and Rocket Matter are related: they share a maker, or one is built on the other. Where a maker offers its own path between two of its products, that path is looked at first, and the analysis establishes what it carries and what it leaves. The points below apply wherever the two differ.
A move between two practice management systems is the widest kind there is. Tabs3 and Rocket Matter each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.
The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with Tabs3’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.
Tabs3 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 Tabs3
The first question for a firm on Tabs3 is which modules it owns, because each one is a different set of records. Billing holds time, fees and receivables. PracticeMaster holds contacts, calendar, documents and the journal. Trust, payables and the ledger are separate programs again. All of them share the Client ID, which is what ties a move together.
One ID for client and matter
A Client ID is up to twelve characters including a decimal point. The part before the point is the client and the part after is the matter. Firms chose a numeric, alphabetic or mixed key type at set-up, and how many decimal places to allow. The ID is split on the way out and both halves are kept.
Everything in one directory
The modules integrate only when installed in the same directory, which the software calls the current working directory. Its data is a set of DAT and IDX files there. A complete copy of that directory, taken with all users out, is the source for every trial load.
Standard and Platinum
The Platinum edition adds a server component with scheduled HotBackup and SQL access to the data, and the standard edition has neither. Which edition the firm runs changes how a consistent copy is taken and what can read it, so it is established in the first conversation.
Figures that are not stored
The vendor’s own help notes that accounts receivable and work in process are calculated from ledger and fee records, not held as fields. So balances cannot be lifted out as a column. They are rebuilt from the transactions and then agreed to the reports the firm prints.
Cloud or server
Firms on Tabs3 Cloud use the suite as hosted by the vendor, and some on-premises firms run it with one of the vendor’s hosting partners. Where the files are, and who is able to copy them, is settled before a cutover date is set.
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.
Trust money moves on this route, so the trust cutover gets a rehearsal of its own.
Analysis
We read what Tabs3 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 Tabs3, 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 Tabs3: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Tabs3 are frozen for an agreed window, the data is collected a final time and Rocket Matter goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. Tabs3 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 Tabs3 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 Tabs3 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
Tabs3 to Rocket Matter: what firms ask
We only have Tabs3 Billing and PracticeMaster. Is that a problem?
No. It means trust and the general ledger are kept in some other program, and that program is added to the plan. The move covers what Tabs3 holds, and the analysis names the other systems that have to agree with it at cutover.
Can we keep the client dot matter numbering?
If the destination allows a firm-set matter number, the full ID can be kept as it is, decimal point included. Where clients and matters are numbered separately, the two halves go into their own fields. Either way the original ID stays searchable, because it is printed on years of statements.
How are the modules extracted together?
From one copy of the working directory, taken at one moment, so billing, trust and ledger all describe the same day. Taking them at different times is how totals end up disagreeing. For the final cutover the copy is taken after month-end procedures are run and before anyone posts again.
Do trust balances in Tabs3 have a place in Rocket Matter?
Yes. Rocket Matter keeps trust ledgers. Bank accounts are created first; ledger history depth is agreed in the analysis. Balances are loaded by matter and agreed to the trust report from Tabs3 as at the cutover date. That load cannot be re-run the way a document load can, so it is rehearsed on a full trial load first.
Does everything in Tabs3 have a place in Rocket Matter?
On paper, yes: each kind of record Tabs3 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 Tabs3 data is loaded into Rocket Matter?
Emails, billing records, the firm’s accounts, 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 Tabs3 and into Rocket Matter
Other destinations from Tabs3
Other systems that move into Rocket Matter
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.
Tabs3 and Rocket Matter are the names and marks of their owners, used here only to identify the two systems.
Moving from Tabs3 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.