Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

HoneyBook to Rocket Matter migration

HoneyBook is a cloud CRM and intake system, and Rocket Matter is a cloud practice management system. Contacts and intake history move, and the matters themselves start life in Rocket Matter.

FromHoneyBookCloud
  1. Contacts: Carried across
  2. Documents: Carried across
  3. Notes: Carried across
  4. Calendar: Carried across
  5. Tasks: Carried across
  6. Billing: Carried with mapping
  7. Templates: Carried with mapping
  8. Intake: Carried with mapping
  9. Emails: Confirmed in the analysis
  10. Time and expenses: Confirmed in the analysis
  11. Custom fields: Confirmed in the analysis
ToRocket MatterCloud
  • 5 carried
  • 3 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from HoneyBook to Rocket Matter

Each row is a kind of record HoneyBook holds, whether Rocket Matter 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.

Records in HoneyBook and their place in Rocket Matter
RecordIn HoneyBookIn Rocket MatterWhat is planned
ContactsClients, other parties and referrersHeldThe contacts list downloads as CSV: name, email, phone, address, notes, date created.Has a placeImported as clients or as other contact types.Carried across
DocumentsFiles stored in or linked from the systemHeld in partContracts, proposals and questionnaires sent to clients are kept on the project.Has a placeNative storage, or a linked OneDrive, Dropbox, Box or NetDocuments account.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partEmails can be filed to matters; it does not hold whole mailboxes.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeld in partA notes field on each contact.Has a placeCarried across
CalendarAppointments, court dates and deadlinesHeldA scheduler takes client bookings.Has a placeCarried across
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeCarried across
Time and expensesTime and expense entries, billed and unbilledTo be confirmedHas a placeUnbilled time and expenses load from a financial import sheet, keyed to the matter.Confirmed in the analysis
BillingInvoices, payments and debtor balancesHeldInvoices and online payments.Has a place in partOpen balances are supported; how much invoice history loads is confirmed in the analysis.Carried with mapping
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCustom fields and custom pages on contacts and matters.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldTemplates for contracts, proposals, invoices and questionnaires.Has a place in partWord merge templates are rebuilt with the product’s own merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLead forms feed a project pipeline; leads can also be imported from a spreadsheet.Has a place in partIntake forms exist; loading open leads is confirmed in the analysis.Carried with mapping

What the plans mean

Carried across
Rocket Matter has a place for this kind of record. It is loaded there and checked against HoneyBook.
Carried with mapping
Rocket Matter 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 Rocket Matter 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 Rocket Matter 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 Rocket Matter 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 Rocket Matter are finished.

Where the data is now

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving off HoneyBook

Where it is going

This describes loading into Rocket Matter NextGen, the platform the vendor’s website now presents. Its import runs in a fixed order: contacts, then matters, then time, expenses and balances. The vendor’s import sheets show what each record must carry. Most of the preparation is giving every matter a file number and getting the accounting set-up finished before any financial record goes in.

  1. A file number on every matter

    Matter File # and matter name are the two required fields. The file number is also the key that time, expenses and balances are matched to on the way in. Source matters with no number, or with numbers reused across clients, are given clean ones before the trial load and the old value is kept in a custom field.

  2. Clients and address-book contacts

    A contact is either a client, who can have matters, or an address-book contact such as an opposing lawyer or an expert. Source systems that hold everyone in one list need each record classified. A person who is a client on one matter and a witness on another is loaded once, as a client.

  3. Accounting set-up comes first

    Timekeepers, matter owners, bank accounts and the chart of accounts must exist before financial data is imported, and the client and matter records must already be in place. The trial load follows that order. Time recorded by people who have left still needs a timekeeper to belong to, so former staff are added before their entries are loaded.

  4. Pick the document store early

    Documents can sit in native storage or in a linked OneDrive, Dropbox, Box or NetDocuments account. With a linked account, the system creates a folder for each matter, named from the file number, client and matter name. Changing that pattern later only affects new matters, so it is settled before the load.

  5. One ledger of record

    NextGen has its own chart of accounts, journal entries and bank reconciliation, and it can also sync with QuickBooks Online from a chosen start date. A firm should run one of them as its books. That decision shapes how opening trust and debtor balances are entered, and the accountant is part of it.

More about moving into Rocket Matter

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  1. Analysis

    We read what HoneyBook holds and how its records link, then agree with you, field by field, where each piece will sit in Rocket Matter. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. 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.

  3. Trial load

    The data is loaded into Rocket Matter as a trial and checked against HoneyBook: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in HoneyBook are frozen for an agreed window, the data is collected a final time and Rocket Matter 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

Step 1 of 5: Start with the route

Moving fromHoneyBook
Moving toRocket Matter

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what HoneyBook holds

    What is in it, how its records link, and where each piece would sit in Rocket Matter. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. 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 Rocket Matter

Loaded data is not yet a working system. This is what NewLaw sets up in Rocket Matter, beyond the migration, so that people can work in it from the first day.

Beyond the data, a firm starting on Rocket Matter has a set of choices that are awkward to change once people are billing. Who the timekeepers and matter owners are, how matters are numbered, which bank accounts exist and whether the books run inside the product or in QuickBooks Online all need an answer before go-live. Matter templates and Word merge documents are then built on top.

Set-up decisions in Rocket Matter

  • Timekeepers, matter owners and the rates each one bills at
  • Matter File number format and matter templates by work type
  • Bank accounts, chart of accounts and the QuickBooks Online decision
  • Custom fields and custom pages for contacts and matters
  • Document storage choice and the matter folder naming pattern
  • Word merge templates, invoice layouts and intake forms

Questions

HoneyBook to Rocket Matter: 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 Rocket Matter?

In part. Open balances are supported; how much invoice history loads is confirmed in the analysis. Open items are matched to what Rocket Matter 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 Rocket Matter?

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 Rocket Matter is kept as a readable archive, and you see which before the move.

What has to be decided before HoneyBook data is loaded into Rocket Matter?

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.

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.

How we do itDiscovery to rollout, step by step

HoneyBook and Rocket Matter are the names and marks of their owners, used here only to identify the two systems.

Moving from HoneyBook to Rocket Matter?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.