Data migration route
CasePacer data to SQLite
CasePacer is a cloud case management system for personal injury work, 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 CasePacer holds and keeps it readable and open to queries.
CasePacerCloud- 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
- Intake: Exported in full
- Documents: Exported with mapping
- Emails: Confirmed in the analysis
- Billing: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
SQLiteFiles- Templates: Kept as a readable archive
- 7 carried
- 1 mapped
- 5 to confirm
- 1 archived
What moves
What moves from CasePacer to SQLite
Each row is a kind of record CasePacer holds, whether SQLite has a place for it, and what is planned. On this route seven kinds of record carry across, one kind needs mapping, one kind has no place in SQLite and is archived and five kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCases, with master cases connecting related mass tort claims. | Has a placeA matters table keyed by matter number. | Exported in full |
| ContactsClients, other parties and referrers | Held | Has a placeContacts and their roles on matters as linked tables. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldCloud storage reached through CP Hub as a mapped drive. CP Link tracks versions. | 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 | To be confirmedEmail integration is advertised. What is stored against a case was not confirmed. | Has a place in partAs message files in folders, indexed in a table. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | HeldNotes and an activity log on each case. | Has a placeA notes table linked to matters. | Exported in full |
| CalendarAppointments, court dates and deadlines | HeldCalendar inside the case, with Outlook syncing. | Has a placeA table of dated entries, with no calendar view. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | HeldTask workflows that run automatically. | 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 | HeldTime and expense tracking by case. | Has a placeA table of time and expense entries. | Exported in full |
| BillingInvoices, payments and debtor balances | To be confirmed | Has a placeInvoice and receipt tables; invoice PDFs kept as files. | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a placeTrust transactions as rows, for look-up and not for accounting. | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | Has a placeLedger journals as rows, where the source held them. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeColumns added to the table they belonged to. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldDocument templates and task workflows. | 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 is part of the case workflow. Clients complete smart forms in CP Direct. | 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 CasePacer.
- 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.
- 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.
- Kept as a readable archive
- SQLite has no place for it. It is exported in a format that opens without CasePacer 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 CasePacer 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 CasePacer 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.
CasePacer 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 CasePacer will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving CasePacer
A CasePacer move is a personal injury or mass tort data set leaving a cloud system: cases, parties, insurers, treatment and settlement figures, and a large volume of documents. The size of the docket matters more than the number of users, because a mass tort firm can hold thousands of near-identical claims under a handful of master cases.
Master cases and their claims
A mass tort is held as a master case with the individual claims connected beneath it. That connection is what lets the firm see one litigation as a whole. Each destination models this differently, as related matters, a project or a group, so the structure is agreed first and the claims are loaded against it.
Files seen through CP Hub
Staff open documents through CP Hub, a mapped drive in File Explorer, so the folder layout they see is the working structure. That layout is recorded case by case before extraction, and the folder a document sat in is kept, since paralegals find medical records and pleadings by where they were filed.
Version history in CP Link
CP Link keeps versions of a document as it is edited. Whether earlier versions can be extracted, and whether the destination keeps versions at all, is settled in the analysis. Where they cannot be carried as versions, the current one is loaded and the earlier ones are filed beside it with a dated name.
Client uploads from CP Direct
Clients send photos, videos and documents from their phones through CP Direct, and answer questionnaires that write straight into the case. Those uploads arrive without a firm naming convention. They are marked as client-supplied in the new system, so evidence from the plaintiff is not mixed in with correspondence the firm produced.
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 CasePacer holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything CasePacer 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 CasePacer: record counts, totals where CasePacer 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 CasePacer, the export is run a final time and checked again. There is nothing to go live. CasePacer 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 CasePacer 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 CasePacer 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
CasePacer to SQLite: what firms ask
How are master cases handled in a system that has no such thing?
The claims become ordinary cases and the connection is rebuilt with whatever the destination offers: a related-matter link, a group field, or a parent record. Reports that ran across the whole litigation are rebuilt on that link. The trial load is checked by counting claims under each master case on both sides.
Will the folders we see in File Explorer look the same afterwards?
The folder names and the documents in them can be reproduced. How staff reach them will change, because the mapped drive belongs to CasePacer. Some destinations offer a desktop sync or a document add-in, and others work only in the browser. That difference is shown to the firm before it chooses, not after.
Do closed cases have to move?
No. Settled cases can come across in full, come across as a summary with their documents, or stay in an export the firm keeps. The usual test is how often a closed case is reopened for a lien query or a later claim. That choice is the firm’s, and the scope is written down before the trial load.
Does the copy in SQLite hold trust ledgers from CasePacer?
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 CasePacer before the plan is fixed.
What happens to records SQLite has no place for?
On this route that is templates. They are exported from CasePacer 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 CasePacer is written out to SQLite?
Documents are exported with mapping, so each mapping is agreed with you first. Emails, billing records, trust ledgers, the firm’s accounts and custom fields are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from CasePacer 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.
CasePacer and SQLite are the names and marks of their owners, used here only to identify the two systems.
Moving from CasePacer 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.