Data migration route
Rocket Matter data to Microsoft SQL Server
Rocket Matter is a cloud practice management system, and Microsoft SQL Server is a database on a server the firm runs. This is not a move to a new working system: the route writes out what Rocket Matter holds and keeps it readable and open to queries.
Rocket MatterCloud- 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
- Templates: Exported with mapping
Microsoft SQL ServerServer- 10 carried
- 4 mapped
What moves
What moves from Rocket Matter to Microsoft SQL Server
Each row is a kind of record Rocket Matter holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route ten kinds of record carry across and four kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldEach matter sits under a client. Completed and closed are separate states. | Has a placeA table of matters linked to clients, parties and fee earners. | Exported in full |
| ContactsClients, other parties and referrers | HeldContacts carry custom fields and tags. | Has a placePeople and companies, with their roles on each matter. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldHeld in Rocket Matter or synced two ways with Box, Dropbox, OneDrive or NetDocuments. | Has a place in partAs files in folders with an index table; storing files in the database is possible. | Exported with mapping |
| EmailsEmails saved to matters or to the store | Held in partEmails brought in through the Office 365 or IMAP connection can be saved to a matter. | Has a place in partAs message files with an index table, or as rows of header fields. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | Held | Has a placeRows of text linked to matters and contacts. | Exported in full |
| CalendarAppointments, court dates and deadlines | HeldTwo-way sync with Google Calendar and Outlook. | Has a placeRows of appointments and key dates; nothing displays them as a calendar. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | HeldMatter templates create tasks and events; there is a Kanban view. | Has a placeRows with assignee, due date and status. | Exported in full |
| Time and expensesTime and expense entries, billed and unbilled | Held | Has a placeTime and expense rows with rates and billed status. | Exported in full |
| BillingInvoices, payments and debtor balances | HeldPrebills, batch billing and LEDES invoices; each matter has a Matter Ledger. | Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | Held | Has a placeTransactions and balances for look-up; it is not a trust accounting system. | Exported in full |
| Firm accountsGeneral ledger, office account and payables | Held in partOriginal platform relies on QuickBooks Online; NextGen has a general ledger built in. | Has a placeGeneral ledger journals and balances, where the source held them. | Exported in full |
| Custom fieldsFields and record types the firm added itself | HeldClient, matter and contact custom fields. | Has a placeAs added columns, or a table of field names and values. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument templates with merge fields, and matter templates. | Has a place in partPrecedent files can be stored; automation does not run here. | Exported with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partLeads and intake are handled in a CRM module. | Has a placeEnquiry rows, where the source recorded them. | Exported in full |
What the plans mean
- Exported in full
- Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against Rocket Matter.
- Exported with mapping
- Microsoft SQL Server 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
Not a new system. A complete copy the firm can query.
Writing Rocket Matter out to Microsoft SQL Server 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 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 is hosted by its maker and Microsoft SQL Server 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 will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving Rocket Matter
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Microsoft SQL Server
There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.
Restored copy or rebuilt schema
Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.
No screens come with it
A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.
Documents sit beside the database
Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.
The edition follows the size
A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.
Backups and a test restore
An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.
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 holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Rocket Matter 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 Microsoft SQL Server as a trial and checked against Rocket Matter: record counts, totals where Rocket Matter 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, the export is run a final time and checked again. There is nothing to go live. Rocket Matter 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 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 holds
What is in it, how its records link, and where each piece would sit in Microsoft SQL Server. 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
Microsoft SQL Server 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.
Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.
What is agreed and set up
- Server, instance and edition agreed with the IT provider
- Read-only logins and roles for named staff
- Views for matter, ledger, time and document look-ups
- Backup schedule and who tests a restore
- Plain names and descriptions for tables and columns
- Excel or Power BI connected for reporting
Questions
Rocket Matter to Microsoft SQL Server: 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.
Does the copy in Microsoft SQL Server hold trust ledgers from Rocket Matter?
Yes. Transactions and balances for look-up; it is not a trust accounting system. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in Rocket Matter as at the export date.
Does everything in Rocket Matter have a place in Microsoft SQL Server?
On paper, yes: each kind of record Rocket Matter holds has a place in Microsoft SQL Server. 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 Rocket Matter is written out to Microsoft SQL Server?
Documents, emails, custom fields and templates 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 and into Microsoft SQL Server
Other destinations from 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.
Rocket Matter and Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.
Moving from Rocket Matter to Microsoft SQL Server?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.