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

Data migration route

HoneyBook to Soluno migration

HoneyBook is a cloud CRM and intake system, and Soluno is a cloud accounting and billing system. Only names and any financial records have a place in a set of books, so little of this moves.

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

What moves

What moves from HoneyBook to Soluno

Each row is a kind of record HoneyBook holds, whether Soluno has a place for it, and what is planned. On this route two kinds of record carry across and nine kinds are confirmed in the analysis.

Records in HoneyBook and their place in Soluno
RecordIn HoneyBookIn SolunoWhat is planned
ContactsClients, other parties and referrersHeldThe contacts list downloads as CSV: name, email, phone, address, notes, date created.Has a placeEach contact is numbered; a file must have a primary contact.Carried across
DocumentsFiles stored in or linked from the systemHeld in partContracts, proposals and questionnaires sent to clients are kept on the project.To be confirmedNo matter document store is described; NetDocuments can be linked.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedTo be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesHeld in partA notes field on each contact.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldA scheduler takes client bookings.To be confirmedConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeldTo be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledTo be confirmedHas a placeConfirmed in the analysis
BillingInvoices, payments and debtor balancesHeldInvoices and online payments.Has a placeCarried across
Custom fieldsFields and record types the firm added itselfTo be confirmedTo be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeldTemplates for contracts, proposals, invoices and questionnaires.To be confirmedConfirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesHeldLead forms feed a project pipeline; leads can also be imported from a spreadsheet.To be confirmedConfirmed in the analysis

What the plans mean

Carried across
Soluno has a place for this kind of record. It is loaded there and checked against HoneyBook.
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

Little of this belongs in the accounts.

Soluno is an accounting package. It takes customers, suppliers, invoices and ledger entries, and has no place for documents, case notes, calendars or leads. From HoneyBook, that usually leaves the contact list, loaded as customers, and any financial records it happens to keep. The table above shows which. This is a small job, and it is better to say so plainly before a firm plans around it.

Loading customers into an accounting system has consequences a contact list elsewhere does not. Every customer can be invoiced, so duplicates and half-complete records turn into billing mistakes. The list is cleaned and matched against the customers already in Soluno before anything is added. The rest of what HoneyBook holds is exported in open formats and kept as an archive, or moved on a different route to a system built for it.

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 Soluno 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

Soluno, which Actionstep now sells as Actionstep Legal Accounting, is an accounting system first, and it expects accounting discipline from the data it is given. Contacts and files need numbers. Entries need dates that fall in open financial periods. Billing, rate and file groups should exist before files are created so that defaults apply. Where documents, calendars and case detail will live is settled alongside.

  1. Numbers for contacts and files

    Every contact has a number and every file has a file number, which Soluno can generate on its own or by contact. A firm can keep its old numbers by typing over the suggested value. The format is agreed first, since the help centre puts later number changes behind an administrator setting once NetDocuments is in use.

  2. Groups before files

    File, billing and rate groups set the defaults a new file picks up, and a file can override them. Loading thousands of files without the groups in place means fixing each one by hand later. The groups are designed from the source system’s rate tables and billing terms during the analysis.

  3. Periods must be open

    Soluno closes financial periods, and a file cannot be closed while it has entries dated after the last closed period. Historic transactions are loaded with the relevant periods open, checked, and then the periods are closed in order. That sequence is rehearsed on the full trial load with the firm’s accountant.

  4. Closed matters need zero balances

    A file closes only when it has no work in progress, no receivable and no retainer or trust balance. Old matters that the source system marked closed while still carrying a few dollars will not close here. Those small balances are written off or cleared in the source before extraction, with partner approval.

  5. Documents live beside it

    Its help centre covers accounting, banking, billing, contacts and files, and describes links to NetDocuments and to Actionstep practice management. It describes no matter document store. A firm arriving from an all-in-one product should expect to need a second destination for its documents, emails and calendar, and the two loads are planned together so matter numbers match in both.

More about moving into Soluno

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 Soluno. 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 Soluno 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 Soluno 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 toSoluno

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

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

Most of the set-up in Soluno is financial structure. The chart of accounts, bank accounts and financial periods come first, then the groups that control billing and rates, then users and what each group of users may do. Lawyers need task code shortcuts and rates before they can enter time. If NetDocuments or Actionstep practice management is to be linked, that connection is made once numbering is final.

Set-up decisions in Soluno

  • Chart of accounts, bank accounts and opening financial periods
  • File, billing and rate groups with their default arrangements
  • Contact and file numbering format, set firm-wide or by contact
  • User groups and what each group may see or do
  • Task and activity codes and each lawyer’s shortcuts
  • Link to NetDocuments or to Actionstep practice management

Questions

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

Soluno has a place for invoices and payments. Open invoices and debtor balances are loaded and agreed to the aged debtors report from HoneyBook. How many years of paid invoices come across as records is the firm’s choice, and older ones are often kept as PDF copies.

Does everything in HoneyBook have a place in Soluno?

Most of it does on paper. Documents, emails, notes, calendar entries, tasks, time entries, custom fields, templates and intake records 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 Soluno is kept as a readable archive, and you see which before the move.

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

Documents, emails, notes, calendar entries, tasks, time entries, custom fields, templates and intake records 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 Soluno are the names and marks of their owners, used here only to identify the two systems.

Moving from HoneyBook to Soluno?

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

We reply within one business day.