Data migration route
Rocket Matter NextGen data to SQLite
Rocket Matter NextGen is a cloud practice management system, and SQLite is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what Rocket Matter NextGen holds and keeps it readable and open to queries.
Rocket Matter NextGenCloud- Matters: Exported in full
- Contacts: Exported in full
- Notes: Exported in full
- Calendar: Exported in full
- Tasks: Exported in full
- Time and expenses: Exported in full
- Billing: Exported in full
- Trust money: Exported in full
- Firm accounts: Exported in full
- Intake: Exported in full
- Documents: Exported with mapping
- Emails: Exported with mapping
- Custom fields: Exported with mapping
SQLiteFiles- Templates: Kept as a readable archive
- 10 carried
- 3 mapped
- 1 archived
What moves
What moves from Rocket Matter NextGen to SQLite
Each row is a kind of record Rocket Matter NextGen holds, whether SQLite has a place for it, and what is planned. On this route ten kinds of record carry across, three kinds need mapping and one kind has no place in SQLite and is archived.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldMatter File # plus a system Matter ID; matters are switched between active and inactive. | Has a placeA matters table keyed by matter number. | Exported in full |
| ContactsClients, other parties and referrers | HeldClients, address-book contacts and a separate list of payees. | Has a placeContacts and their roles on matters as linked tables. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldNative storage with versions, or a linked OneDrive, Dropbox, Box or NetDocuments account. | Has a place in partListed in a table; the files themselves stay in folders beside the database. | Exported with mapping |
| EmailsEmails saved to matters or to the store | Held in partEmails forwarded to the firm’s address or sent by the Outlook add-in are tagged to matters. | Has a place in partAs message files in folders, indexed in a table. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | Held | Has a placeA notes table linked to matters. | Exported in full |
| CalendarAppointments, court dates and deadlines | Held | Has a placeA table of dated entries, with no calendar view. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | Held | Has a placeA table of tasks and their status at the final date. | Exported in full |
| Time and expensesTime and expense entries, billed and unbilled | Held | Has a placeA table of time and expense entries. | Exported in full |
| BillingInvoices, payments and debtor balances | HeldIncludes split billing and matter-level fee allocations. | Has a placeInvoice and receipt tables; invoice PDFs kept as files. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | HeldThree-way reconciliation reports are built in. | Has a placeTrust transactions as rows, for look-up and not for accounting. | Exported in full |
| Firm accountsGeneral ledger, office account and payables | HeldChart of accounts, journal entries, accounts payable and bank reconciliation. | Has a placeLedger journals as rows, where the source held them. | Exported in full |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields are grouped into custom pages on matters and contacts. | Has a placeColumns added to the table they belonged to. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | HeldWord merge templates and matter templates. | No placePrecedent files are kept in folders, not in the database. | Kept as a readable archive |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partIntake form templates that can be shared with clients through the portal. | Has a placeAn enquiries table, where the source tracked them. | Exported in full |
What the plans mean
- Exported in full
- SQLite has a place for this kind of record. It is loaded there and checked against Rocket Matter NextGen.
- Exported with mapping
- SQLite holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
- Kept as a readable archive
- SQLite has no place for it. It is exported in a format that opens without Rocket Matter NextGen and handed to the firm as a read-only archive.
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
Not a new system. A complete copy the firm can query.
Writing Rocket Matter NextGen out to SQLite is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.
What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Rocket Matter NextGen as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.
Rocket Matter NextGen is hosted by its maker and SQLite sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Rocket Matter NextGen will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving Rocket Matter NextGen
A firm on NextGen has more in its practice system than a firm on the original Rocket Matter did, because the general ledger and payables can live there too. Leaving therefore starts with two questions. Which platform is the firm really on, and are its books inside the product or in QuickBooks Online? The answers decide whether this is a practice management move or an accounting move as well.
Same name, different platform
Staff call both generations Rocket Matter, and the help articles for the two are published on different sites. NextGen keeps its records differently from the original platform. A firm that began on the original should say so at the start, since the analysis then checks whether its older matters were filled in under different rules.
File number and Matter ID
Every matter has the Matter File # the firm typed and a Matter ID the system assigned. People quote the file number. Exports and imports can be keyed on either one. The extraction keeps both, so a time entry can always be traced back to its matter even where a file number was later edited.
Folders named by a pattern
Where documents are held in a linked Box, Dropbox or OneDrive account, each matter folder is named from the file number, client name and matter name. That makes the storage account readable without the application. A change to the naming setting applies only to new matters, so a firm that changed it has folders in two patterns.
Pages follow the area of law
Custom fields are grouped into custom pages, and a matter page can be tied to particular areas of law. A page tied to all areas still only appears on matters that have an area assigned. Field mapping is done page by page, and matters with no area of law are reviewed first so nothing entered on them is overlooked.
Payees and payables
Payees are kept apart from contacts, each with the name to print on a cheque, a default account and a flag for 1099 reporting. Unpaid bills and credits sit in accounts payable. If the destination does not do payables, these go to the firm’s accounting package, with the 1099 flags preserved for year end.
Where it is going
Arriving in SQLite
A SQLite archive suits a firm that wants the old system’s records kept, seldom consulted, and free of any server or subscription. Everything structured goes into one file. That simplicity moves the responsibility elsewhere: the file has no security of its own and no administrator watching it, so where it is stored and who can reach it are the real decisions.
One file, kept with the archive
Matters, contacts, time, invoices and trust transactions become tables in a single file. It is stored with the firm’s closed-matter records and can be copied like any document. A checksum recorded when the file is finalised lets anyone confirm, years later, that the copy they hold has not been altered, and the firm decides whether to keep one.
No logins inside the file
SQLite has no users or passwords. Anyone who can open the file can read every client’s ledger. Protection comes from where it is kept, such as a restricted folder or an encrypted volume, and that choice is the firm’s. It can suit an archive consulted by two people, and it is said plainly so nobody assumes otherwise.
Built for reading, not sharing
Only one program can write to the file at a time, and SQLite’s authors point people to a client/server database where many users share data over a network. A finished archive never meets that limit. It is the reason SQLite is used here for records that are closed and not for anything staff still update.
Documents stay outside it
Documents remain ordinary files in matter folders, and a table in the database lists each one with its matter, title, dates and path. Keeping them as files means they open with a double-click and can be handed to a client. The table is how a file is found by matter number instead of by guessing its name.
Someone has to open it
SQLite publishes its own command-line program for opening a database file, and other tools read the format too. None of that helps if nobody remembers how. Saved queries for the usual look-ups and a short note on which tool to use can sit in the same folder as the file, and the firm decides what it needs.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what Rocket Matter NextGen holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything Rocket Matter NextGen holds is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to SQLite as a trial and checked against Rocket Matter NextGen: record counts, totals where Rocket Matter NextGen holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in Rocket Matter NextGen, the export is run a final time and checked again. There is nothing to go live. Rocket Matter NextGen is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
Fixed price, agreed after the analysis. How NewLaw moves legal data
Start
Start this migration
Tell us what is in Rocket Matter NextGen 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 Rocket Matter NextGen holds
What is in it, how its records link, and where each piece would sit in SQLite. 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
Structure, permissions and handover
SQLite is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
There is nothing to install on a server and nothing to license. The work is in making the file usable and safe to keep: naming it, documenting its tables, storing it where the firm’s records policy says archives go, and checking that a member of staff can open it and find a matter. Whether a second copy is held somewhere separate is the firm’s call.
What is agreed and set up
- File name, storage location and whether a second copy exists
- Whether a checksum is recorded for later verification
- Saved queries for matter, ledger and document look-ups
- Which tool staff will use to open the file
- Who may open the folder the file sits in
- Retention period and destruction date noted beside the file
Questions
Rocket Matter NextGen to SQLite: what firms ask
Is Rocket Matter NextGen the same as CosmoLex?
They are sold as separate products by the same company. Their knowledge bases share articles and document the same screens, and that is as far as the public material goes. For planning a move, the firm’s own account settles how its records are kept.
Our accounts are in QuickBooks Online, synced from NextGen. Does QuickBooks need to move?
No. QuickBooks Online is the firm’s own subscription and stays where it is. The sync from NextGen stops at cutover, and the new system’s feed into QuickBooks starts from an agreed date. Both sides are reconciled to that date so no invoice or payment is posted twice.
Can a matter with money still in trust be moved?
Yes, and it must be handled with care. NextGen itself will not let a matter be made inactive until its trust funds are disbursed, so active matters with trust balances are normal. Each balance is carried by client and matter, and the totals are checked against the last three-way reconciliation.
Does the copy in SQLite hold trust ledgers from Rocket Matter NextGen?
Yes. Trust transactions as rows, for look-up and not for accounting. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in Rocket Matter NextGen as at the export date.
What happens to records SQLite has no place for?
On this route that is templates. They are exported from Rocket Matter NextGen in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.
What has to be decided before Rocket Matter NextGen is written out to SQLite?
Documents, emails and custom fields are exported with mapping, so each mapping is agreed with you first. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from Rocket Matter NextGen and into SQLite
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.
Rocket Matter NextGen and SQLite are the names and marks of their owners, used here only to identify the two systems.
Moving from Rocket Matter NextGen to SQLite?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.