Data migration route
HoneyBook to MyCase migration
HoneyBook is a cloud CRM and intake system, and MyCase is a cloud practice management system. Contacts and intake history move, and the matters themselves start life in MyCase.
HoneyBookCloud- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Billing: Carried with mapping
- Templates: Carried with mapping
- Intake: Carried with mapping
- Emails: Confirmed in the analysis
- Time and expenses: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
MyCaseCloud- 5 carried
- 3 mapped
- 3 to confirm
What moves
What moves from HoneyBook to MyCase
Each row is a kind of record HoneyBook holds, whether MyCase 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 placePeople and companies load separately and are then linked to cases. | 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 placeFiled in folders under each case. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partSaved emails can be filed to a case; it does not hold mailboxes. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held in partA notes field on each contact. | Has a place | Carried across |
| CalendarAppointments, court dates and deadlines | HeldA scheduler takes client bookings. | Has a place | 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 | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | HeldInvoices and online payments. | Has a place in partAn outstanding balance per case is supported; fuller invoice history is confirmed in the analysis. | Carried with mapping |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeFields are created on cases or contacts before records are loaded. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldTemplates for contracts, proposals, invoices and questionnaires. | Has a place in partTemplates are rebuilt as Word documents with MyCase 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 place in partLeads and intake forms exist; loading open leads in bulk is confirmed in the analysis. | Carried with mapping |
What the plans mean
- Carried across
- MyCase has a place for this kind of record. It is loaded there and checked against HoneyBook.
- Carried with mapping
- MyCase 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 enquiries move. Matters begin in the new system.
A CRM knows people: who enquired, who referred them, what was sent and when. It does not know matters the way a practice system does. So the move from HoneyBook to MyCase is mostly a contacts job, and contacts are where duplicates live. The same person appears as a lead, a client and a referrer, sometimes under three email addresses. They are merged before extraction where they can be identified, because MyCase will invoice and receipt against these records.
Pipelines, campaigns and automations seldom have a direct equivalent in a practice system. Open enquiries can be loaded as contacts with a note of their stage, or opened as matters if the firm wants them worked from the first day. Intake forms and email sequences are set up again in whatever MyCase or its intake tool provides. Past correspondence is kept as notes or documents on the contact, so the history of a relationship can still be read.
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 MyCase 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 MyCase
Loading a firm into MyCase means turning matters into cases and deciding what each case is called, numbered and filed under. The users, practice areas and custom fields have to exist first, because the records point at them. Money needs the most thought: an opening balance can be brought in simply, but how much invoice and trust history is rebuilt behind it is agreed in the analysis.
Every case name is unique
MyCase will not accept two cases with the same name. A firm with forty matters called Estate Planning, or two files for the same pair of litigants, needs a naming pattern before the trial load. Client surname plus the old matter number is one option, and it keeps the old number in view.
Old numbers fit as they are
The case number field takes letters, digits and punctuation, so a number such as 2019-0457/LIT can be kept without reformatting. It is worth keeping it tidy: the email tools match incoming mail to a case by finding the case number in the subject line.
Open or closed, nothing between
A case in MyCase is either open or closed, with a closed date. Source systems often have more states than that: pending, on hold, archived, awaiting payment. Each is mapped to open or closed during the analysis, and the original status can be kept in a custom field.
Practice areas build themselves
On import, MyCase creates a practice area for every distinct value it is given. Family, Family Law and Fam. Law would become three. The source list is reduced to one agreed set during clean-up, so the firm starts with a short list of practice areas it chose.
Lead attorney must exist
The lead attorney on a case has to be a user in the account. Departed fee earners who still own closed matters are a common snag. They are either mapped to a current user, or their name is recorded in a custom field on the case.
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 MyCase. 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 MyCase 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 MyCase 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 MyCase. 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 MyCase
Loaded data is not yet a working system. This is what NewLaw sets up in MyCase, beyond the migration, so that people can work in it from the first day.
A loaded MyCase account is not yet a working one. The firm still has to decide how cases are classified, who can see what, how money is handled and what clients are shown in the portal. Document templates are rebuilt against MyCase’s own merge fields, since precedents written for another system’s field codes will not merge here. Staff are trained on their own cases once the trial load has been checked.
Set-up decisions in MyCase
- Practice areas and custom fields for cases and contacts
- Trust and operating bank accounts with opening balances per case
- Word document templates rebuilt with MyCase merge fields
- Intake forms and lead pipeline for each practice area
- User roles and who can open which cases
- QuickBooks sync or the MyCase Accounting add-on
Questions
HoneyBook to MyCase: 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 MyCase?
In part. An outstanding balance per case is supported; fuller invoice history is confirmed in the analysis. Open items are matched to what MyCase 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 MyCase?
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 MyCase is kept as a readable archive, and you see which before the move.
What has to be decided before HoneyBook data is loaded into MyCase?
Billing records, templates and intake records 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 MyCase
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 MyCase are the names and marks of their owners, used here only to identify the two systems.
Moving from HoneyBook to MyCase?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.