Data migration route
Harvest to Lawmatics migration
Harvest is a cloud accounting and billing system, and Lawmatics is a cloud CRM and intake system. Lawmatics is built around people and enquiries, so the contact list leads this move, and the table shows what else has a place.
HarvestCloud- Matters: Carried across
- Contacts: Carried across
- Notes: Carried across
- Tasks: Carried across
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Documents: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
LawmaticsCloud- 4 carried
- 2 mapped
- 3 to confirm
What moves
What moves from Harvest to Lawmatics
Each row is a kind of record Harvest holds, whether Lawmatics has a place for it, and what is planned. On this route four kinds of record carry across, two kinds need mapping and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partProjects under clients stand in for matters; there are three project types. | Has a placeLoaded from CSV with a status of PNC, Hired or Lost and a pipeline stage. | Carried across |
| ContactsClients, other parties and referrers | Held in partClients and client contacts, kept mainly as invoice recipients. | Has a placeContacts and companies load from CSV; relationships link further parties to a matter. | Carried across |
| DocumentsFiles stored in or linked from the system | To be confirmed | Has a place in partFiles and folders on each matter, added by upload or API, not by the spreadsheet import. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held in partFree-text notes on each time entry. | Has a placeNotes on matters, contacts and companies. | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held in partTasks are categories of work for time entries, not to-dos. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimers and timesheets by person, project and task, with approvals. | Has a place in partTime entries and expenses, where the Time & Billing module is enabled. | Carried with mapping |
| BillingInvoices, payments and debtor balances | HeldInvoices and estimates, with online payment through Stripe or PayPal. | Has a place in partInvoices and payments; a past invoice is entered as sent, then marked paid. | Carried with mapping |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeMatter, contact and company fields. A field must exist before data is imported into it. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partDocument and email templates are rebuilt with Lawmatics merge fields. | Confirmed in the analysis |
What the plans mean
- Carried across
- Lawmatics has a place for this kind of record. It is loaded there and checked against Harvest.
- Carried with mapping
- Lawmatics 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
Mostly a contact list, cleaned before it lands.
Lawmatics is built for contacts, leads and the conversations around them. What Harvest can offer it first is a list of people and companies, and sometimes a history that can be attached as notes. Whether anything else it holds has a place depends on what Lawmatics keeps besides contacts, and the table above shows that kind by kind. What has no place stays where it is or is archived.
A contact list taken from a system that was never a CRM needs work before it is useful. Names are split or joined differently, the same client appears under several spellings, and there is no record of who agreed to be contacted. The list is cleaned and de-duplicated, matched against what Lawmatics already holds, and loaded with a source tag, so the firm can tell these contacts from the ones that came through intake.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Harvest 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 Harvest is kept running until the checks on Lawmatics are finished.
Where the data is now
Leaving Harvest
Harvest knows about clients, projects, tasks, people, time entries, expenses, invoices and estimates. It does not know about matters or trust money. A firm leaving it for a practice system is turning projects into matters and carrying across time and invoice history, while the firm’s books stay in the accounting package Harvest was feeding.
Client, then project
A Harvest client record holds a name, an address and a currency, with contacts added mainly so invoices reach the right person. The detail a legal system wants about a client, such as other parties or a responsible lawyer, was never recorded here and is gathered from elsewhere or added after loading.
Tasks are not to-dos
In Harvest a task is a category of work, such as drafting or attendance, that a time entry is logged against, and it can carry its own billable rate. Tasks map to activity codes in a practice system. They are not a list of things waiting to be done on a matter.
Three ways to set rates
A Time & Materials project bills at a project rate, a rate per person or a rate per task. The same lawyer can therefore have different rates on different projects. Historical time is loaded with the rate it was recorded at, and the going-forward rate table is built separately in the new system.
Invoices copied to the ledger
Where the QuickBooks Online or Xero integration is on, invoices and payments were copied across, but time and expenses went only as invoice lines. The accounting package holds the receivables and Harvest holds the time behind them. Both are read, and the invoice numbers are used to match one to the other.
Archived clients and projects
Clients and projects that are finished can be archived instead of deleted, and archived records are easy to leave out of an export. The analysis counts active and archived records separately, and the firm chooses whether closed work comes across as closed matters or stays behind in the Harvest account.
Where it is going
Arriving in Lawmatics
Lawmatics takes matters, contacts and companies from CSV files, and its API accepts notes, tasks, appointments, files, time entries and invoices. It is an intake and client relationship system, so a firm arriving from full practice management has to decide what it is for. People and matters load well. There is no general ledger, and years of billing history have no natural home.
Contacts and matters load separately
The import expects two spreadsheets: one for contacts or companies with no case, such as referrers and other lawyers, and one for matters. A matter import creates the matter and its primary contact together. Every matter has exactly one primary contact, so joint clients are loaded as one primary and one relationship.
Set up before loading
Owner, stage, practice area, source and campaign are matched by name. A value on the spreadsheet that does not match one in Lawmatics exactly creates a new one, which is how a firm ends up with two spellings of the same practice area. Users, pipelines, practice areas and marketing sources are set up first, and custom fields must exist before data is loaded into them.
Statuses and matter numbers
Each imported matter must be PNC (potential new client), Hired or Lost, with open and closed handled as sub-statuses the firm creates. The case number is a system field assigned by an auto-numbering pattern and cannot be edited by hand afterwards. Whether old matter numbers can be loaded into it, or belong in a custom field, is tested in the trial load.
Duplicates are matched by email
With Match Contacts by Email switched on, a contact whose email already exists is skipped or updated, never doubled. Names and phone numbers are not checked. Matters are not deduplicated at all, so two rows with one email create two matters on one contact. Clean-up therefore happens in the spreadsheet, and automations are switched off for every load.
What has no place
There is no general ledger. The Time & Billing module holds time entries, expenses, invoices and a trust account with a running balance per matter, and past invoices are entered as already sent and then marked paid. A firm that needs its full accounting history keeps the old system read only or carries the books in an accounting package.
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 Harvest holds and how its records link, then agree with you, field by field, where each piece will sit in Lawmatics. 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 Harvest, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Lawmatics as a trial and checked against Harvest: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Harvest are frozen for an agreed window, the data is collected a final time and Lawmatics 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 Harvest as at the cutover date. Harvest 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 Harvest 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 Harvest holds
What is in it, how its records link, and where each piece would sit in Lawmatics. 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 Lawmatics
Loaded data is not yet a working system. This is what NewLaw sets up in Lawmatics, beyond the migration, so that people can work in it from the first day.
In Lawmatics the design comes before the data. The pipeline stages, practice areas, custom fields and relationship types decide what the import can hold, and the forms and automations decide what the firm’s intake looks like from the first day. If a practice system sits behind it, the field mapping between the two is part of the same job.
Set-up decisions in Lawmatics
- Pipelines and stages for intake and for open matters
- Practice areas, sub-statuses, relationship types and the matter numbering pattern
- Custom fields on matters, contacts and companies
- Intake forms, booking links and e-signature document templates
- Follow-up automations, with marketing sources and campaigns
- Mail and calendar sync, user roles and practice system integration
Questions
Harvest to Lawmatics: what firms ask
Harvest has projects, not matters. How does that convert?
Each project becomes a matter under the same client, keeping its name and any code as the matter reference. Firms that used one long-running project per client, with all work logged to it, decide during clean-up whether to split it into separate matters or carry it as a single general matter.
Will our old time entries keep their notes?
Time entries are read with their date, person, project, task, hours, billable flag and the notes typed on them. In the new system the notes become the narrative on each entry. Entries already invoiced are linked to their invoice where the destination supports that, and listed as billed where it does not.
We have no trust records in Harvest. Is that a problem?
It is common. Harvest has no trust accounting, so client money has been tracked in the accounting package or a spreadsheet. Those records become the source for opening trust balances in the new system, and each one is agreed to the trust bank statement before it is loaded.
Does billing history from Harvest move into Lawmatics?
In part. Invoices and payments; a past invoice is entered as sent, then marked paid. Open items are matched to what Lawmatics can hold, and the rest of the billing history is kept as reports that open without Harvest.
Does everything in Harvest have a place in Lawmatics?
Most of it does on paper. Documents, custom fields and templates 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 Lawmatics is kept as a readable archive, and you see which before the move.
What has to be decided before Harvest data is loaded into Lawmatics?
Time entries and billing records are carried with mapping, so each mapping is agreed with you first. Documents, custom fields and templates 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 Harvest and into Lawmatics
Other destinations from Harvest
Other systems that move into Lawmatics
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.
Harvest and Lawmatics are the names and marks of their owners, used here only to identify the two systems.
Moving from Harvest to Lawmatics?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.