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

Data migration route

Zola Suite to Filevine migration

Zola Suite is a cloud practice management system, and Filevine is a cloud case management system. Matter records move into cases, and the firm decides where its accounting runs from the cutover date.

FromZola SuiteCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Emails: Carried across
  5. Notes: Carried across
  6. Calendar: Carried across
  7. Tasks: Carried across
  8. Time and expenses: Carried with mapping
  9. Billing: Carried with mapping
  10. Trust money: Carried with mapping
  11. Custom fields: Carried with mapping
  12. Templates: Carried with mapping
  13. Intake: Carried with mapping
  14. Firm accounts: Confirmed in the analysis
ToFilevineCloud
  • 7 carried
  • 6 mapped
  • 1 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Zola Suite to Filevine

Each row is a kind of record Zola Suite holds, whether Filevine has a place for it, and what is planned. On this route seven kinds of record carry across, six kinds need mapping and one kind is confirmed in the analysis.

Records in Zola Suite and their place in Filevine
RecordIn Zola SuiteIn FilevineWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldHas a placeLoaded as projects of a defined project type.Carried across
ContactsClients, other parties and referrersHeldHas a placeContact cards, linked to projects.Carried across
DocumentsFiles stored in or linked from the systemHeldAny file type, indexed for search, with a new version saved on each edit.Has a placeDocs section with folders. Templated project folders can be set per type.Carried across
EmailsEmails saved to matters or to the storeHeldAn email client is part of the product and files messages against matters.Has a placeHeld in the activity feed of the project.Carried across
NotesFile notes, matter notes and contact notesHeldHas a placeHeld as notes in the activity feed.Carried across
CalendarAppointments, court dates and deadlinesHeldHas a placeDeadlines and calendar events.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldHas a place in partNeeds the Billing product enabled.Carried with mapping
BillingInvoices, payments and debtor balancesHeldOne matter can be split between several billing clients, each with its own invoice.Has a place in partNeeds the Billing product enabled.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldHas a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis.Carried with mapping
Firm accountsGeneral ledger, office account and payablesHeldVendor bills, cheque writing and financial statements sit in the same system.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldHas a placeCustom sections and fields per project type.Carried with mapping
TemplatesPrecedents, document templates and automationHeldHas a place in partTemplates are rebuilt as Filevine document templates. They are not converted.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLeads and intake forms are handled in the built-in CRM.Has a place in partLeads belong in Lead Docket, which passes signed clients to Filevine.Carried with mapping

What the plans mean

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

Matters become cases. The ledgers need a home.

Going from a practice management system to a case management system is a move towards the file and away from the ledger. Matters, parties, documents, notes and deadlines have a natural place in Filevine. Time, invoices, trust and the general ledger often do not, or only in part, and the table above shows which. Before the move is planned the firm settles where billing and trust accounting will run, because that decides what is loaded and what is archived.

Case systems are usually built around a practice area, with their own stages, roles and document sets. A general matter from Zola Suite has to be given a case type in Filevine, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Filevine is exported as reports and ledgers the firm can open without Zola Suite, and kept as the record of what was billed and held.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Zola Suite 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 Zola Suite is kept running until the checks on Filevine are finished.

Where the data is now

Nobody moves off Zola Suite as such any more. The records are in CARET Legal, and that is the system the data is taken from. Firms that joined in the Zola years tend to have the longest history in it, with billing arrangements and document links set up long ago that current staff may not know about. Finding those early is most of the analysis.

  1. One account, two names

    Staff who say Zola and staff who say CARET are talking about the same login. The vendor announced a new name, not a new system, so there should be no older archive to hunt for. Old bookmarks, saved report names and procedure documents may still carry the Zola name, and it helps to list them before cutover.

  2. Split billing on a matter

    A single matter can be billed to several clients at set percentages, with fees and costs split separately and a distinct invoice number for each payer. Many systems expect one bill-to client per matter. Split matters are listed in the analysis, and the firm chooses between sub-matters and a manual split in the destination.

  3. Payables and cheques

    Vendor bills, outgoing payments and cheque runs are recorded here, along with the costs passed on to matters. When the firm leaves, its unpaid vendor bills and its vendor list need a home in whatever accounting package comes next. That list is reconciled to the payables report on the day of the freeze.

  4. Worldox or NetDocuments links

    Some firms never used the built-in document store. They linked each matter to a Worldox cabinet or a NetDocuments workspace and worked from there. Those documents are not in the practice management database at all. The analysis records which store each matter points to, so no folder is assumed to be empty when it is only held elsewhere.

  5. Every edit kept as a version

    Editing a Word document inside the product saves a new version each time, and any earlier one can be restored. A long-running matter may hold dozens of versions of one agreement. The firm decides whether all of them move or only the current one, and the document count in the trial load is checked against that decision.

More about moving off Zola Suite

Where it is going

Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.

  1. Project types before data

    Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.

  2. One contact card per person

    Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.

  3. Lists become collection items

    Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.

  4. History goes into the feed

    File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.

  5. Billing is a separate switch

    The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.

More about moving into Filevine

How NewLaw runs it

Four steps, in this order.

Trust money moves on this route, so the trust cutover gets a rehearsal of its own.

  1. Analysis

    We read what Zola Suite holds and how its records link, then agree with you, field by field, where each piece will sit in Filevine. 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 Zola Suite, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Filevine as a trial and checked against Zola Suite: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Zola Suite are frozen for an agreed window, the data is collected a final time and Filevine goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. Zola Suite 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 Zola Suite 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 fromZola Suite
Moving toFilevine

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 Zola Suite holds

    What is in it, how its records link, and where each piece would sit in Filevine. 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 Filevine

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

Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.

Set-up decisions in Filevine

  • Design project types, sections and fields for each practice area
  • Define phases and the tasks each phase should trigger
  • Build document templates that fill from project fields
  • Set teams, permissions and protected sections for restricted matters
  • Decide whether Billing and Payments are switched on
  • Connect Lead Docket so signed leads become projects

Questions

Zola Suite to Filevine: what firms ask

Is Zola Suite still available?

Not under that name. The vendor renamed it CARET Legal after AbacusNext became CARET, and the Zola Suite web address now leads to the CARET Legal site. It was presented as a rebrand, so a firm that never left is simply using CARET Legal.

Our invoices go back to when we started on Zola. Can the full billing history move?

It depends on what the destination will accept. Some systems take historic invoices and payments as records. Others take only open balances, with the old invoices attached as PDFs. Split-billed matters need the closest look, since each payer has its own invoice number.

Do we plan the move as Zola Suite or as CARET Legal?

As CARET Legal, because that is what the firm logs into and what the vendor supports. The planning is the same either way. One extra step for a long-standing Zola firm is checking for features switched on years ago, such as split billing or a Worldox link.

Do trust balances in Zola Suite have a place in Filevine?

In part. Trust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. The analysis sets out which trust records have a place in Filevine and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

Does everything in Zola Suite have a place in Filevine?

Most of it does on paper. The firm’s accounts 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 Filevine is kept as a readable archive, and you see which before the move.

What has to be decided before Zola Suite data is loaded into Filevine?

Time entries, billing records, trust ledgers, custom fields, templates and intake records are carried with mapping, so each mapping is agreed with you first. The firm’s accounts 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

Zola Suite and Filevine are the names and marks of their owners, used here only to identify the two systems.

Moving from Zola Suite to Filevine?

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

We reply within one business day.