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

Data migration route

HoneyBook to Server drives migration

HoneyBook is a cloud CRM and intake system, and Server drives are plain files on equipment the firm controls. What moves is the files, plus a readable export of everything else the old system holds.

FromHoneyBookCloud
  1. Documents: Carried across
  2. Notes: Carried with mapping
  3. Templates: Carried with mapping
  4. Emails: Confirmed in the analysis
  5. Time and expenses: Confirmed in the analysis
  6. Custom fields: Confirmed in the analysis
ToServer drivesFiles
  1. Contacts: Kept as a readable archive
  2. Calendar: Kept as a readable archive
  3. Tasks: Kept as a readable archive
  4. Billing: Kept as a readable archive
  5. Intake: Kept as a readable archive
Readable archiveNo place in Server drives
  • 1 carried
  • 2 mapped
  • 3 to confirm
  • 5 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from HoneyBook to Server drives

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

Records in HoneyBook and their place in Server drives
RecordIn HoneyBookIn Server drivesWhat is planned
ContactsClients, other parties and referrersHeldThe contacts list downloads as CSV: name, email, phone, address, notes, date created.No placeCan be kept only as an exported spreadsheet.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeld in partContracts, proposals and questionnaires sent to clients are kept on the project.Has a placeFiles in folders, named and dated during the load.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs .msg or .eml files in each matter’s correspondence folder.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeld in partA notes field on each contact.Has a place in partAs a text or PDF file per matter, not as separate records.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldA scheduler takes client bookings.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldNo placeKept as a readable archive
Time and expensesTime and expense entries, billed and unbilledTo be confirmedNo placeOnly as exported reports or spreadsheets.Confirmed in the analysis
BillingInvoices, payments and debtor balancesHeldInvoices and online payments.Has a place in partInvoices as PDF files; no ledger.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedNo placeConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeldTemplates for contracts, proposals, invoices and questionnaires.Has a place in partPrecedents as Word files; merge fields tied to the old system stop working.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLead forms feed a project pipeline; leads can also be imported from a spreadsheet.No placeKept as a readable archive

What the plans mean

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

An export the firm can open without the system.

Server drives hold files, and most of what HoneyBook holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used HoneyBook, by client or by year, with a short index file saying what is where.

Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in Server drives is limited before the export is copied in.

HoneyBook is hosted by its maker and Server drives sit on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What HoneyBook will release depends on its export tools, and that is confirmed in the analysis.

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

Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.

  1. Agree the tree and the names

    A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.

  2. Budget the path length

    Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.

  3. Dates have to be set deliberately

    A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.

  4. Emails become message files

    Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.

  5. Keep an index beside the files

    A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.

More about moving into Server drives

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Server drives on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what HoneyBook holds and how it is organised, then agree with you where each kind of record will sit in Server drives. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into Server drives and checked against HoneyBook: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in HoneyBook, a final pass over a weekend picks up what changed since the trial. 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 toServer drives

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 Server drives. 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

Structure, permissions and handover

Server drives are storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.

What is agreed and set up

  • Share and top-level folders for clients, precedents and administration
  • Security groups and folder permissions, with restricted matters separate
  • Drive letter mapped for every user at sign-in
  • Backup schedule and shadow copies for earlier versions
  • Written naming rule for client, matter and document names
  • Read-only area for closed matters and archived system exports

Questions

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

No. Server drives have no place for invoices or payments. Invoices as PDF files; no ledger. Billing history from HoneyBook is exported as reports and invoice copies and kept as a readable archive.

What happens to records Server drives have no place for?

On this route that is contacts, calendar entries, tasks, billing records and 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 Server drives?

Notes 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 decides which closed matters and how many versions of a document are in scope.

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

Moving from HoneyBook to Server drives?

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

We reply within one business day.