Data migration route
CasePacer to SimpleLaw migration
CasePacer is a cloud case management system for personal injury work, and SimpleLaw is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in SimpleLaw, often from a separate accounts package.
CasePacerCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Intake: Carried across
- Templates: Carried 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
SimpleLawCloud- 8 carried
- 1 mapped
- 5 to confirm
What moves
What moves from CasePacer to SimpleLaw
Each row is a kind of record CasePacer holds, whether SimpleLaw has a place for it, and what is planned. On this route eight kinds of record carry across, one kind needs mapping 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 place | Carried across |
| ContactsClients, other parties and referrers | Held | Has a placeAs leads, clients or other contacts in the CRM. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldCloud storage reached through CP Hub as a mapped drive. CP Link tracks versions. | Has a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmedEmail integration is advertised. What is stored against a case was not confirmed. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | HeldNotes and an activity log on each case. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | HeldCalendar inside the case, with Outlook syncing. | Has a place | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTask workflows that run automatically. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime and expense tracking by case. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | To be confirmed | Has a place in partInvoices are created in the product; loading invoice history is confirmed in the analysis. | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a place in partTrust balances are supported; history depth is confirmed in the analysis. | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | No placeGeneral ledger stays in QuickBooks or another accounting package. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a place | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldDocument templates and task workflows. | Has a place in partTemplates are rebuilt using SimpleLaw’s own automation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partIntake is part of the case workflow. Clients complete smart forms in CP Direct. | Has a placeLeads and intake forms. | Carried across |
What the plans mean
- Carried across
- SimpleLaw has a place for this kind of record. It is loaded there and checked against CasePacer.
- Carried with mapping
- SimpleLaw 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.
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 SimpleLaw brings those two sources together. The case records come from CasePacer. 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 SimpleLaw, 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.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of CasePacer depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to CasePacer is kept running until the checks on SimpleLaw are finished.
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 SimpleLaw
Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.
Lead, client or contact
A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.
Billing type on each matter
Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.
Storage chosen before loading
If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.
Custom fields named for templates
Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.
Portal access client by client
The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.
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 CasePacer holds and how its records link, then agree with you, field by field, where each piece will sit in SimpleLaw. 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 CasePacer, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into SimpleLaw as a trial and checked against CasePacer: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in CasePacer are frozen for an agreed window, the data is collected a final time and SimpleLaw 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 CasePacer as at the cutover date. CasePacer 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 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 SimpleLaw. 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 SimpleLaw
Loaded data is not yet a working system. This is what NewLaw sets up in SimpleLaw, beyond the migration, so that people can work in it from the first day.
The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.
Set-up decisions in SimpleLaw
- Labels for documents, activities, expenses and contact IDs
- Custom fields and intake forms for each practice area
- Document templates and the attorney-client agreement
- Workflows for case types that follow a standard process
- User permission sets and client portal visibility
- QuickBooks connection and the online payment processor
Questions
CasePacer to SimpleLaw: 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.
Do trust balances in CasePacer have a place in SimpleLaw?
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. If SimpleLaw turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
Does everything in CasePacer have a place in SimpleLaw?
Most of it does on paper. Emails, billing records, trust ledgers, the firm’s accounts and custom fields could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in SimpleLaw is kept as a readable archive, and you see which before the move.
What has to be decided before CasePacer data is loaded into SimpleLaw?
Templates are carried 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 sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from CasePacer and into SimpleLaw
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 SimpleLaw are the names and marks of their owners, used here only to identify the two systems.
Moving from CasePacer to SimpleLaw?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.