Data migration route
AdvoLogix to SimpleLaw migration
AdvoLogix 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.
AdvoLogixCloud- 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
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Trust money: Confirmed in the analysis
SimpleLawCloud- 8 carried
- 3 mapped
- 2 to confirm
What moves
What moves from AdvoLogix to SimpleLaw
Each row is a kind of record AdvoLogix holds, whether SimpleLaw has a place for it, and what is planned. On this route eight kinds of record carry across, three kinds need mapping and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldMatters are the central record, with stage, status and a closed flag. | Has a place | Carried across |
| ContactsClients, other parties and referrers | HeldSalesforce accounts and contacts, linked to matters as participants with roles. | Has a placeAs leads, clients or other contacts in the CRM. | Carried across |
| DocumentsFiles stored in or linked from the system | HeldSalesforce files on the matter, or a linked NetDocuments, iManage, SharePoint or Google Drive store. | 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 | Held in partEmails sent from a matter are logged. Mailbox filing depends on an email integration. | To be confirmed | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | HeldComments recorded against the matter. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | HeldA Matter Calendar, with date calculation rules. | Has a place | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldActivity plans and task checklists generate tasks on a matter. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime entries with timekeepers, rate groups and UTBMS codes. Expenses are tracked too. | Has a place | Carried across |
| BillingInvoices, payments and debtor balances | Held in partTime, expenses and fees become billings, split between billing parties. | 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 | To be confirmed | Has a place in partTrust balances are supported; history depth is confirmed in the analysis. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields are added to matters and participants through Salesforce set-up. | Has a place | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldAdvoDoc document assembly templates. A HotDocs integration is also listed. | Has a place in partTemplates are rebuilt using SimpleLaw’s own automation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntake records and intake forms, converted to matters. | 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 AdvoLogix.
- 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
The whole practice moves, accounts included.
A move between two practice management systems is the widest kind there is. AdvoLogix 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 AdvoLogix’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 AdvoLogix 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 AdvoLogix is kept running until the checks on SimpleLaw are finished.
Where the data is now
Leaving AdvoLogix
A move off AdvoLogix is a move out of a Salesforce org. The matter data is spread across the vendor’s packaged objects, standard Salesforce objects and whatever the firm’s administrator added over the years. An inventory of that org comes first: which objects hold live data, which fields are the firm’s own, and where the documents physically are.
Participants carry the relationships
A client, an opposing party or an expert is a Salesforce account or contact joined to the matter by a participant record with a role. Some participants are typed in as free text with no contact behind them. Both kinds are extracted, and the free-text ones are matched to real contacts or created as new ones before loading.
Documents may sit elsewhere
Files can be held as Salesforce files on the matter, or in NetDocuments, iManage, SharePoint or Google Drive through an integration. Many orgs have a mix, with older matters in one place and newer ones in another. Each matter is checked for where its files are before any document count is agreed.
Billings are derived records
Time and expense entries generate billing records, which can be split between billing parties and edited without changing the source entry. The two can therefore disagree by design. Which one is the record of truth for unbilled work is decided in the analysis, and totals are reconciled per matter against that choice.
Every org is configured differently
Matter stages, statuses, page layouts and automation are set by each firm’s Salesforce administrator. Two firms on the same product rarely share a field list. The mapping is written from the firm’s own org, including fields nobody remembers adding, and unused ones are listed for the firm to drop.
Where the books are kept
The help centre describes no ledger inside the matter application. An integration with Accounting Seed, a separate Salesforce application with its own objects, is offered for firms that keep their books on the platform. If the destination has built-in accounting, opening balances are taken from wherever the books were actually kept, not from the matter records.
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 AdvoLogix 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 AdvoLogix, 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 AdvoLogix: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in AdvoLogix 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 AdvoLogix as at the cutover date. AdvoLogix 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 AdvoLogix 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 AdvoLogix 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
AdvoLogix to SimpleLaw: what firms ask
Is AdvoLogix the same thing as Mitratech CaseCloud?
For practical purposes, yes. Mitratech introduced CaseCloud in November 2024 and describes it as built on Salesforce and AdvoLogix technologies. The help centre and many of the component names still say AdvoLogix. A firm that installed the product under the old name is holding the same kind of data in the same kind of org.
Do we lose our Salesforce history if we leave?
Salesforce keeps field history only where tracking was switched on, so what exists varies by org. Emails, tasks and events logged on a matter can be extracted with it. Field-level change history usually has no equivalent in a legal system, and it either comes across as a note or stays behind.
Can our time entries and rates come across?
Time entries, timekeepers and UTBMS codes are structured records with fields of their own. Rates are harder, because they are held in rate groups applied to matters and can be changed on a single matter. The analysis lists the rate that actually applied to each matter, so unbilled time is valued the same way after the move.
Do trust balances in AdvoLogix 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 AdvoLogix 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 AdvoLogix have a place in SimpleLaw?
Most of it does on paper. Emails and trust ledgers 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 AdvoLogix data is loaded into SimpleLaw?
Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails and trust ledgers 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 AdvoLogix and into SimpleLaw
Other destinations from AdvoLogix
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.
AdvoLogix and SimpleLaw are the names and marks of their owners, used here only to identify the two systems.
Moving from AdvoLogix 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.