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

Data migration route

HoneyBook to SmartAdvocate migration

HoneyBook is a cloud CRM and intake system, and SmartAdvocate is a cloud case management system for personal injury work. Contacts and intake history move, and open enquiries become leads or cases in SmartAdvocate.

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

What moves

What moves from HoneyBook to SmartAdvocate

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

Records in HoneyBook and their place in SmartAdvocate
RecordIn HoneyBookIn SmartAdvocateWhat is planned
ContactsClients, other parties and referrersHeldThe contacts list downloads as CSV: name, email, phone, address, notes, date created.Has a placeCarried across
DocumentsFiles stored in or linked from the systemHeld in partContracts, proposals and questionnaires sent to clients are kept on the project.Has a placeDocuments page, by category and subcategory.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeEmails are attached to cases.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 placeAppointments and critical deadlines.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeCarried across
Time and expensesTime and expense entries, billed and unbilledTo be confirmedHas a placeTracked time entries.Confirmed in the analysis
BillingInvoices, payments and debtor balancesHeldInvoices and online payments.Has a place in partInvoices for hourly matters. Past invoices are scoped in the analysis.Carried with mapping
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a place in partConfirmed in the analysis for each field with no standard home.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldTemplates for contracts, proposals, invoices and questionnaires.Has a place in partTemplates are rebuilt with SmartAdvocate merge codes.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLead forms feed a project pipeline; leads can also be imported from a spreadsheet.Has a placeIntake and lead records.Carried across

What the plans mean

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

Intake history moves. The pipeline is rebuilt.

Intake data is the front end of a case. A lead in HoneyBook carries the first conversation, the screening answers, the referrer and often a signed retainer. Many case management systems have an intake stage of their own, so a lead can land as a prospective case with that history attached. Where SmartAdvocate has no such stage, open enquiries are loaded as contacts with their status in a note, and the firm decides which to open as cases.

Screening questions are the mapping work. Each intake form is a set of fields, and each field has to find a place on the case or be kept as a note. Referral sources are tidied into one list first, because they are usually typed by hand and reporting depends on them. Marketing automations, email sequences and web forms do not move as data. They are set up again in SmartAdvocate or in the tool that feeds 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 SmartAdvocate 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

SmartAdvocate keeps injury detail in structured fields and screens, so mapping counts for more than usual: the more precisely the old data is placed, the more of those screens are filled on the first day. Parties, incidents, insurers, providers and bills are loaded to their own screens, and the vendor’s implementation team runs conversions into it.

  1. Map to fields, not notes

    The case summary, dashboards and settlement screen read from structured fields. Injury details, insurance limits and provider bills dumped into a note leave those screens empty. The mapping takes each old field to its SmartAdvocate counterpart, and only what truly has no counterpart is loaded as a note.

  2. Case types and statuses

    Cases are loaded against case types and statuses that drive WorkPlans and reports. These are agreed with the firm before the trial load, and old statuses are translated to the new list. A status with no match is not guessed at. It is listed, and someone who knows the files decides.

  3. Document categories

    Documents are searched by category, subcategory, sender, recipient and date as well as by folder. The old system’s folders are translated into categories on the way in. Files that arrive uncategorised can still be found by description, but they fall outside the category views staff are trained to use.

  4. Working with the vendor’s conversion

    SmartAdvocate’s implementation team converts client data into the system and trains staff through its own classes. The firm’s side of that is supplying a clean source, checking the converted cases against the old system, and deciding what to do with the exceptions. Independent help is used on those tasks.

  5. Choosing Server or Cloud

    The firm decides before loading whether it will run the Server edition on its own Windows server or use the hosted Cloud edition. Either way the data load is the same. What differs is who looks after backups, updates and remote access afterwards, and that is settled with the firm’s IT provider.

More about moving into SmartAdvocate

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of SmartAdvocate says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in HoneyBook and checking each trial against HoneyBook.

  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 SmartAdvocate. 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 SmartAdvocate 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 SmartAdvocate 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 toSmartAdvocate

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

Loaded data is not yet a working system. The maker of SmartAdvocate runs or arranges the set-up of its product, so this is what has to be decided and put in place in SmartAdvocate, whoever does the work, before people rely on it from the first day.

Setting up SmartAdvocate is a matter of deciding how much of its detail the firm will use from the start. Case types, statuses and WorkPlans come first because they drive everything else. Templates follow. The vendor trains staff through its own classes, and the decisions below are best made before the first of those.

Set-up decisions in SmartAdvocate

  • Choose the Server or Cloud edition with IT
  • Define case types, statuses and staff roles
  • Build WorkPlans and Automated Procedures for each case type
  • Convert letters and forms into templates with merge codes
  • Install the Outlook plugin and agree email filing habits
  • Set up intake screens, lead sources and dashboards

Questions

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

In part. Invoices for hourly matters. Past invoices are scoped in the analysis. Open items are matched to what SmartAdvocate 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 SmartAdvocate?

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

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

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

Moving from HoneyBook to SmartAdvocate?

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

We reply within one business day.