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

Data migration route

Zola Suite to Litify migration

Zola Suite is a cloud practice management system, and Litify 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. Calendar: Carried across
  5. Tasks: Carried across
  6. Time and expenses: Carried across
  7. Intake: Carried across
  8. Emails: Carried with mapping
  9. Billing: Carried with mapping
  10. Custom fields: Carried with mapping
  11. Templates: Carried with mapping
  12. Notes: Confirmed in the analysis
  13. Trust money: Confirmed in the analysis
  14. Firm accounts: Confirmed in the analysis
ToLitifyCloud
  • 7 carried
  • 4 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Zola Suite to Litify

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

Records in Zola Suite and their place in Litify
RecordIn Zola SuiteIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldHas a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldHas a placeLoaded as parties and connected by roles.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 placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeldAn email client is part of the product and files messages against matters.Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesHeldTo be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeldHas a placeCalendar events on the matter.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldHas a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldOne matter can be split between several billing clients, each with its own invoice.Has a place in partBilling is part of the product. Loading past invoices is scoped in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTo be confirmedConfirmed in the analysis
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 fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationHeldHas a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLeads and intake forms are handled in the built-in CRM.Has a placeLoaded as intakes.Carried across

What the plans mean

Carried across
Litify has a place for this kind of record. It is loaded there and checked against Zola Suite.
Carried with mapping
Litify 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 Litify. 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 Litify, and that choice drives which fields and workflows it gets. The mapping is agreed type by type. Financial history with no place in Litify 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 Litify 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 Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.

  1. The design comes first

    Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.

  2. One party, many roles

    Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.

  3. Open enquiries load as intakes

    Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.

  4. Documents load after records

    Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.

  5. Validation rules reject bad rows

    A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.

More about moving into Litify

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 Litify 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 Zola Suite and checking each trial against Zola Suite.

  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 Litify. 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 Litify as a trial and checked against Zola Suite: record counts, financial 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 Litify 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 Zola Suite as at the cutover date. 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 toLitify

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

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

A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.

Set-up decisions in Litify

  • Define intake questionnaires and the rules for conversion
  • Set case types, matter stages and page layouts
  • Build matter plans that create tasks at each stage
  • Design document folders and generation templates per case type
  • Configure user roles and sharing for restricted matters
  • Decide on timekeeping, billing and accounting integrations

Questions

Zola Suite to Litify: 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 Litify?

That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Zola Suite before the plan is fixed. If Litify turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

Does everything in Zola Suite have a place in Litify?

Most of it does on paper. Notes, trust ledgers and 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 Litify 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 Litify?

Emails, billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes, trust ledgers and 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 Litify are the names and marks of their owners, used here only to identify the two systems.

Moving from Zola Suite to Litify?

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

We reply within one business day.