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

Data migration route

HoneyBook to Clio Manage migration

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

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. Emails: Confirmed in the analysis
  9. Time and expenses: Confirmed in the analysis
  10. Custom fields: Confirmed in the analysis
ToClio ManageCloud
  1. Intake: Kept as a readable archive
Readable archiveNo place in Clio Manage
  • 5 carried
  • 2 mapped
  • 3 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from HoneyBook to Clio Manage

Each row is a kind of record HoneyBook holds, whether Clio Manage has a place for it, and what is planned. On this route five kinds of record carry across, two kinds need mapping, one kind has no place in Clio Manage and is archived and three kinds are confirmed in the analysis.

Records in HoneyBook and their place in Clio Manage
RecordIn HoneyBookIn Clio ManageWhat is planned
ContactsClients, other parties and referrersHeldThe contacts list downloads as CSV: name, email, phone, address, notes, date created.Has a placePeople and companies, with related contacts linked to matters by a separate template.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 placeFiled under the matter; Clio scopes document migration separately from data.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeHeld as communications on the matter, with phone logs.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeld in partA notes field on each contact.Has a placeMatter notes and contact notes each have a template.Carried across
CalendarAppointments, court dates and deadlinesHeldA scheduler takes client bookings.Has a placeCalendar events have a migration template.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeTasks have a migration template.Carried across
Time and expensesTime and expense entries, billed and unbilledTo be confirmedHas a place in partUnbilled time entries load; billed time entries do not, by Clio’s migration guide.Confirmed in the analysis
BillingInvoices, payments and debtor balancesHeldInvoices and online payments.Has a place in partAn outstanding balance loads as one line per matter; past invoices do not.Carried with mapping
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCreated first, then filled from the custom field templates.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldTemplates for contracts, proposals, invoices and questionnaires.Has a placeRebuilt as Clio document templates with its merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLead forms feed a project pipeline; leads can also be imported from a spreadsheet.No placeLeads and intake forms belong in Clio Grow.Kept as a readable archive

What the plans mean

Carried across
Clio Manage has a place for this kind of record. It is loaded there and checked against HoneyBook.
Carried with mapping
Clio Manage 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.
Kept as a readable archive
Clio Manage has no place for it. It is exported in a format that opens without HoneyBook and handed to the firm as a read-only archive.

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 Clio Manage 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 Clio Manage 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 Clio Manage 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 Clio Manage 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

Clio Manage is loaded through its migration templates, one spreadsheet per kind of record, imported in a fixed order with contacts first. Clio’s own migration guide is plain about the limit: balances come across, financial history does not. So a load into Clio is planned as records plus opening positions, with the old system kept for the history behind them.

  1. Matters link by client name

    The matters template ties each matter to its client by an exact match on first name, last name or company name. A client spelt two ways in the old system becomes two contacts, or a matter assigned to an unknown client. This is why contact clean-up is finished before the first trial load, not after it.

  2. Decide the numbering scheme first

    Clio numbers imported matters itself unless the account is set to manual numbering, in which case the old number is supplied in the template. That setting and the firm’s preferred scheme are decided before any matter is loaded. The Client Reference field is available for an old file number the firm still wants to see.

  3. Balances, one line each

    Under Clio’s standard migration, an outstanding balance arrives as one line per matter and a trust balance as one line per matter or contact. Past invoices, billed time, payments and trust transactions are listed as data that cannot be migrated. The trust total is reconciled against the old system’s closing report on the trial load.

  4. Custom fields must exist

    Matter and contact custom fields are created in Clio before their values are imported, each with a field type. Accounts set up for a particular practice area come with preconfigured fields and matter templates, which affects the mapping. We compare those with the old system’s fields and add only what is missing.

  5. Rates and permissions by hand

    Billable rates for users, clients and matters are not part of an import. Neither are user permissions or settings. They are entered in Clio during set-up from a schedule the firm confirms, and a sample of imported unbilled time is checked against that schedule before the trial load is signed off.

More about moving into Clio Manage

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 Clio Manage. 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 Clio Manage 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 Clio Manage 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 toClio Manage

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 Clio Manage. 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 Clio Manage

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

Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.

Set-up decisions in Clio Manage

  • Matter numbering scheme, practice areas and matter stages
  • Custom fields for matters and contacts, by practice area
  • Document templates with merge fields, uploaded from Word or PDF
  • Billing settings, user and client rates, and trust accounts
  • Roles and permissions for each user
  • Outlook add-in, Clio Drive and the accounting connection

Questions

HoneyBook to Clio Manage: 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 Clio Manage?

In part. An outstanding balance loads as one line per matter; past invoices do not. Open items are matched to what Clio Manage can hold, and the rest of the billing history is kept as reports that open without HoneyBook.

What happens to records Clio Manage has no place for?

On this route that is intake records. They are exported from HoneyBook in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

What has to be decided before HoneyBook data is loaded into Clio Manage?

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.

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 Clio Manage are the names and marks of their owners, used here only to identify the two systems.

Moving from HoneyBook to Clio Manage?

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

We reply within one business day.