Moving off a system
Migrating from HoneyBook
Client management platform for independent businesses that combines enquiries, proposals, contracts, invoices and online payments in one account. This page sets out what HoneyBook holds, what moving off it involves and where its records can go.
Where it can go
Routes from HoneyBook
Each route has a page of its own: what moves, what has no place in the destination and how the move is run.
Practice management systems
Actionstep8 of 11 kinds of record have a place
Centerbase8 of 11 kinds of record have a place
Clio Manage7 of 11 kinds of record have a place
MyCase8 of 11 kinds of record have a place
Rocket Matter8 of 11 kinds of record have a place
SimpleLaw8 of 11 kinds of record have a place
Smokeball8 of 11 kinds of record have a place
SurePoint Finance Enterprise3 of 11 kinds of record have a place
Case management systems
Document management systems
Accounting and billing systems
CRM and intake systems
File storage
Box3 of 11 kinds of record have a place
Dropbox3 of 11 kinds of record have a place
Google Drive3 of 11 kinds of record have a place
OneDrive3 of 11 kinds of record have a place
Server drives3 of 11 kinds of record have a place
SharePoint6 of 11 kinds of record have a place
Sync.com3 of 11 kinds of record have a place
What it holds
The records HoneyBook keeps
Fourteen kinds of record matter to a move. HoneyBook keeps eight of them, two in part, and three could not be confirmed from its maker’s own material.
- MattersNoWork is organised as projects with a type and a pipeline stage, not as matters.
- ContactsYesThe contacts list downloads as CSV: name, email, phone, address, notes, date created.
- DocumentsIn partContracts, proposals and questionnaires sent to clients are kept on the project.
- EmailsTo be confirmedEmails saved to matters or to the store
- NotesIn partA notes field on each contact.
- CalendarYesA scheduler takes client bookings.
- TasksYesTo-dos and workflow steps assigned to people
- Time and expensesTo be confirmedTime and expense entries, billed and unbilled
- BillingYesInvoices and online payments.
- Trust moneyNoTrust or client account ledgers and balances
- Firm accountsNoGeneral ledger, office account and payables
- Custom fieldsTo be confirmedFields and record types the firm added itself
- TemplatesYesTemplates for contracts, proposals, invoices and questionnaires.
- IntakeYesLead forms feed a project pipeline; leads can also be imported from a spreadsheet.
Moving off it
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.
The system
What HoneyBook is
HoneyBook is made for independent service businesses such as photographers, event planners and consultants. A sole practitioner or small firm that uses it has generally chosen it for the client-facing side: an enquiry form, a booking calendar, a contract the client signs online and an invoice they can pay by card. It has no legal features such as matter numbering or trust accounting.
Everything is hosted by HoneyBook and used in a browser or the mobile app. Work is organised into projects that move through pipeline stages from enquiry to completion. A project gathers the client’s contact details with the proposals, contracts, questionnaires and invoices sent to them, and tasks and automations run alongside.
- Kind
- CRM and intake
- Runs as
- Cloud, hosted by its maker
- Made by
- HoneyBook, Inc.
- Mainly used in
- The United States and Canada
- Also known as
- Honeybook, Honey Book
How NewLaw runs it
Four steps, in this order.
Financial records move on most routes, 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 the new system. 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 the new system 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 the new system 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
Choose where the HoneyBook data is going, or tell us you have not decided. 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 the new system. 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.
After the move
Setting up the system you move to
A migration ends with data in a new system. Whether people can work in it on the first day depends on how that system was set up: matter types, templates, billing, permissions. NewLaw does that work as well, and each destination’s page says what its set-up involves.
Set-up, by destination
- Actionstep
- Box
- Centerbase
- Clio Manage
- Dropbox
- Filevine
- Full data export
- Gladiate
- Google Drive
- iManage Cloud
- Lawmatics
- LexWorkplace
- Litify
- Microsoft SQL Server
- MyCase
- Neos
- NetDocuments
- OneDrive
- QuickBooks Online
- Rocket Matter
- Server drives
- SharePoint
- SimpleLaw
- SmartAdvocate
- Smokeball
- Soluno
- SQLite
- SurePoint Finance Enterprise
- Sync.com
Questions
Moving off HoneyBook: 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.
Where to start
Still deciding where to move?
Choose the system before you plan the move, and see where AI fits once your data is in it.
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 the other product names and logos on this page belong to their owners and are used only to identify the systems.
Moving off HoneyBook?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.