Data migration route
PracticeEvolve to SimpleLaw migration
PracticeEvolve and SimpleLaw are each a cloud practice management system. Both run a whole practice, so this is a full move, and the financial records set the timetable.
PracticeEvolveCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Intake: Carried across
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
SimpleLawCloud- Firm accounts: Kept as a readable archive
- 7 carried
- 4 mapped
- 2 to confirm
- 1 archived
What moves
What moves from PracticeEvolve to SimpleLaw
Each row is a kind of record PracticeEvolve holds, whether SimpleLaw has a place for it, and what is planned. On this route seven kinds of record carry across, four kinds need mapping, one kind has no place in SimpleLaw and is archived and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held | Has a place | Carried across |
| ContactsClients, other parties and referrers | HeldIncludes a conflict search across the system. | Has a placeAs leads, clients or other contacts in the CRM. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldIndexed for searching, including image-based PDFs. | 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 | HeldMatter emails are filed and saved centrally. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partEvents are held on the matter. | Has a place | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTo-do lists, recurring tasks and workflows. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldAutomatic activity tracking converts to time entries. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | HeldFlexible billing with approval flows. | Has a place in partInvoices are created in the product; loading invoice history is confirmed in the analysis. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | HeldClient funds management within the legal accounts. | Has a place in partTrust balances are supported; history depth is confirmed in the analysis. | Carried with mapping |
| Firm accountsGeneral ledger, office account and payables | HeldLegal accounts with balance sheet, debtors, cash flow and budget reporting. | No placeGeneral ledger stays in QuickBooks or another accounting package. | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | Held in partEvolvePlus is described as fully customisable; the extent is confirmed in the analysis. | Has a place | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldA supplied library of automated forms and precedents, plus the firm’s own. | Has a place in partTemplates are rebuilt using SimpleLaw’s own automation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLead tracking for prospective clients. | 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 PracticeEvolve.
- 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.
- Kept as a readable archive
- SimpleLaw has no place for it. It is exported in a format that opens without PracticeEvolve 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
The whole practice moves, accounts included.
A move between two practice management systems is the widest kind there is. PracticeEvolve and SimpleLaw 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 PracticeEvolve’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.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of PracticeEvolve 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 PracticeEvolve is kept running until the checks on SimpleLaw are finished.
Where the data is now
Leaving PracticeEvolve
PracticeEvolve keeps a firm’s data in the vendor’s Azure hosting, so extraction is arranged with the vendor. Which product the firm is on comes first, EvolveGo or EvolvePlus, because the two differ in how much has been customised. The accounts are inside the system, so client funds and office ledgers form part of every move.
EvolveGo or EvolvePlus
The vendor sells two cloud products. EvolveGo is the one built for quick implementation. EvolvePlus allows full customisation and workflows built without code. An EvolvePlus firm is likely to have fields, screens and processes of its own, and the analysis has to find them. An EvolveGo firm is closer to the product as supplied.
Supplied precedents versus yours
PracticeEvolve provides a large library of automated forms and precedents and keeps it up to date. Those belong to the vendor’s library. Precedents the firm added or adapted are the firm’s. We separate the two lists early, because only the second is rebuilt in the new system, and it is usually much shorter than staff expect.
Where the documents are held
Documents and filed emails are saved centrally and indexed for search. We confirm whether they are held by PracticeEvolve itself or by a separate document management product connected to it, as that decides who supplies the files and how each one is tied back to its matter.
Messages in Communicate
The built-in Communicate platform carries secure messages and shared files between the firm and its clients. Those conversations are part of the file for some matters. We check whether they are exported with the matter. If not, the messages for open matters are saved to the file as documents before cutover.
Accounts in the same system
Legal accounts, billing and client funds run inside PracticeEvolve, with its own reports for debtors, cash flow and budgets, and the UK site lists Making Tax Digital among its features. Leaving means choosing where office accounting goes next, and closing a tax period in the old system before balances are taken.
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.
Trust money moves on this route, so the trust cutover gets a rehearsal of its own.
Analysis
We read what PracticeEvolve 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 PracticeEvolve, 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 PracticeEvolve: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in PracticeEvolve are frozen for an agreed window, the data is collected a final time and SimpleLaw 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. PracticeEvolve 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 PracticeEvolve 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 PracticeEvolve 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
PracticeEvolve to SimpleLaw: what firms ask
How do we get our data out of a hosted system?
Through the vendor, at the firm’s request. We specify what is needed: the database or a full export, every document with its matter reference, and closing accounts reports taken at the same time. How it is delivered is confirmed with PracticeEvolve during the analysis, and the first copy is tested before a cutover date is set.
Do the automated forms come with us?
The supplied forms stay with PracticeEvolve. Documents already produced from them are on the matters and move as files. The firm’s own precedents are exported and their merge fields replaced with the destination’s. If the new system has its own forms library, we compare it with the forms the firm uses most.
Is the Australian version different from the UK one?
The vendor publishes separate UK and Australian sites, and each edition follows its own country’s rules for client money and tax. Our method is the same for both. The checks on the financial cutover are written against the rules of the jurisdiction the firm practises in.
Do trust balances in PracticeEvolve have a place in SimpleLaw?
In part. Trust balances are supported; history depth is confirmed in the analysis. The analysis sets out which trust records have a place in SimpleLaw and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.
What happens to records SimpleLaw has no place for?
On this route that is the firm’s accounts. They are exported from PracticeEvolve 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 PracticeEvolve data is loaded into SimpleLaw?
Billing records, trust ledgers, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails and notes 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 PracticeEvolve and into SimpleLaw
Other destinations from PracticeEvolve
Other systems that move 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.
PracticeEvolve and SimpleLaw are the names and marks of their owners, used here only to identify the two systems.
Moving from PracticeEvolve 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.