Data migration route
HoneyBook to Lawmatics migration
HoneyBook and Lawmatics are each a cloud CRM and intake system. The records move, and the pipeline, forms and automations are set up again in Lawmatics.
HoneyBookCloud- Contacts: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Intake: Carried across
- Documents: Carried with mapping
- Billing: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Time and expenses: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
LawmaticsCloud- 5 carried
- 3 mapped
- 3 to confirm
What moves
What moves from HoneyBook to Lawmatics
Each row is a kind of record HoneyBook holds, whether Lawmatics has a place for it, and what is planned. On this route five kinds of record carry across, three kinds need mapping and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | HeldThe contacts list downloads as CSV: name, email, phone, address, notes, date created. | 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 | Held in partContracts, proposals and questionnaires sent to clients are kept on the project. | Has a place in partFiles and folders on each matter, added by upload or API, not by the spreadsheet import. | Carried with mapping |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partEmails reach a matter through mail sync from a connected mailbox. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held in partA notes field on each contact. | Has a placeNotes on matters, contacts and companies. | Carried across |
| CalendarAppointments, court dates and deadlines | HeldA scheduler takes client bookings. | Has a placeAppointments, called events, with types and locations. | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | Has a place in partTime entries and expenses, where the Time & Billing module is enabled. | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | HeldInvoices and online payments. | 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 | HeldTemplates for contracts, proposals, invoices and questionnaires. | Has a place in partDocument and email templates are rebuilt with Lawmatics merge fields. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLead forms feed a project pipeline; leads can also be imported from a spreadsheet. | Has a placePipelines and stages, marketing sources and campaigns. | Carried across |
What the plans mean
- Carried across
- Lawmatics has a place for this kind of record. It is loaded there and checked against HoneyBook.
- 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
Contacts and leads move. Forms and automations are rebuilt.
Between two tools that manage contacts and enquiries, the records move cleanly and the machinery does not. Each pipeline stage in HoneyBook needs an equivalent in Lawmatics, and stage names seldom line up. Open leads are loaded at the matching stage so that follow-up carries on. Closed and lost leads come across with their outcome, because conversion reporting depends on them. Sources and referrers are put into one list first.
Forms, email templates, sequences and automations are rebuilt by hand. It is worth doing on purpose: most firms find a sequence still running that nobody remembers setting up. Web forms and booking links on the firm’s site are repointed at cutover, and a test enquiry is put through each one. Consent and unsubscribe records move with the contacts and are checked separately, since a mistake there means emailing people who opted out.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of HoneyBook 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 HoneyBook is kept running until the checks on Lawmatics are finished.
Where the data is now
Leaving HoneyBook
A practice leaving HoneyBook is usually moving from a general client tool to a legal one. Contacts come out as a spreadsheet. Projects, signed contracts and invoices are tied to those contacts inside the product and are gathered project by project. The main decision is how a HoneyBook project, which is a booking or a job, becomes a matter with a number and a type.
What the contact export holds
HoneyBook’s contact download is a CSV with each person’s name, email, phone number, address, notes and the date they were added. It says nothing about which projects they had or what they were invoiced. That link is rebuilt from the projects themselves, so that each contact can be attached to the right matters.
Projects become matters
A project has a name, a type and a pipeline stage. A matter needs more: a number, a responsible lawyer, a matter type the new system recognises, an open or closed status. A mapping from project types and stages to matter types and statuses is agreed first, and finished projects are loaded as closed matters.
Signed contracts are evidence
Costs agreements and engagement letters signed through HoneyBook exist as online files in the client’s project. Each signed contract is saved as a file, as a PDF where HoneyBook provides one, and filed against the new matter. This is done while every project can still be opened in the old account and checked against the copy.
Payments and what is owed
Invoices and payment schedules sit inside projects, and clients pay by card through HoneyBook. Paid invoices are history. Unpaid instalments and scheduled future payments are live, and each one is either collected before cutover or raised again in the new billing system. No client money is held in trust here, so there is no trust ledger to move.
Forms on the firm’s website
The enquiry form on the firm’s website and any public booking link feed straight into HoneyBook’s pipeline. They keep collecting enquiries into the old account until they are replaced. The new intake form and booking page are published at cutover, and the old ones are taken down the same day.
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 HoneyBook 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 HoneyBook, 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 HoneyBook: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in HoneyBook 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 HoneyBook as at the cutover date. HoneyBook 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 HoneyBook 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 HoneyBook 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
HoneyBook to Lawmatics: what firms ask
Can HoneyBook projects be turned into matters?
Yes, with a mapping. Each project supplies a client, a name, dates and a stage, and those are enough to create a matter once the firm has chosen a numbering scheme and matter types. Details a legal system expects, such as other parties or limitation dates, were never recorded and are added afterwards for open matters.
What happens to our templates and automations?
They are rebuilt, not copied. Contract and email templates are taken as text and set up again as precedents with the new system’s merge fields. Automations are written down step by step, and the firm decides which are still wanted, since a legal intake workflow usually differs from a booking workflow.
Does billing history from HoneyBook 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 HoneyBook.
Does everything in HoneyBook have a place in Lawmatics?
Most of it does on paper. Emails, time entries 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 Lawmatics is kept as a readable archive, and you see which before the move.
What has to be decided before HoneyBook data is loaded into Lawmatics?
Documents, billing records and templates are carried with mapping, so each mapping is agreed with you first. Emails, time entries 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 HoneyBook and 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.
HoneyBook and Lawmatics are the names and marks of their owners, used here only to identify the two systems.
Moving from HoneyBook 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.