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

Data migration route

LeanLaw to Neos migration

LeanLaw is a cloud accounting and billing system, and Neos is a cloud case management system for personal injury work. Only part of what LeanLaw holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.

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

What moves

What moves from LeanLaw to Neos

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

Records in LeanLaw and their place in Neos
RecordIn LeanLawIn NeosWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters as billing records, with budgets, rates and fee arrangements.Has a placeCases by case type.Carried across
ContactsClients, other parties and referrersHeld in partClients and billing contacts only.Has a placeParties, providers and case contacts. Contacts can be imported from CSV.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeLoaded as checklist items.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime and expenses tied to client and matter.Has a place in partTime can be held as value items. The treatment of old entries is confirmed in the analysis.Carried with mapping
BillingInvoices, payments and debtor balancesHeldHourly, flat fee and recurring fixed fees; LEDES on some plans.Has a place in partInvoices exist in Neos. Loading past invoices is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldClient and matter trust ledgers, with the trust bank account kept in QuickBooks Online.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeUser-defined fields are created on the relevant tab first.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partInvoice templates.Has a place in partTemplates are rebuilt for Neos document generation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeIntakes tab. Simple intake imports from CSV are supported.Confirmed in the analysis

What the plans mean

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

Clients and jobs move. The books stay books.

An accounting or billing system and a case management system overlap less than firms expect. LeanLaw knows clients, jobs, time and invoices. Neos knows cases, parties, documents and deadlines. The client list moves well, and jobs can seed the case list. Time and invoice history has a place only where the case system has a billing side, and the table above shows whether this one does. A general ledger does not belong in a case system.

So the plan has two halves. Records with a place in Neos are loaded and checked there. The rest is exported from LeanLaw as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If LeanLaw is staying as the accounting system, nothing financial needs to move at all, and the job is to line up client and case numbers so the two can be reconciled.

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

Where the data is now

LeanLaw and QuickBooks Online hold two halves of the same financial record, kept in step by a live sync. A firm leaving LeanLaw is usually keeping QuickBooks, at least at first. So the question is less what to extract than how to change the system feeding QuickBooks without posting anything twice, and where the matter-level detail that only LeanLaw holds will live afterwards.

  1. QuickBooks keeps the ledger

    Every invoice, payment and trust transaction entered in LeanLaw is also in QuickBooks Online. If the destination connects to the same QuickBooks company, it must start from an agreed date and recognise what is already there. Where the destination has its own general ledger, QuickBooks is closed off at a period end and balances are carried in.

  2. Matter detail lives in LeanLaw

    QuickBooks knows the totals. LeanLaw knows which timekeeper did what on which matter, at what rate, and against what budget. That is the part to extract: time and expense entries with their narratives, and the invoice lines they became. The sums are checked back to the QuickBooks figures client by client.

  3. Trust in two places

    The trust bank account is an account in QuickBooks Online, and the ledger for each client and matter is in LeanLaw. Both have to agree with the bank statement. The three-way reconciliation is completed and saved for the last period before cutover, and opening trust balances are taken from it.

  4. Compensation and origination

    LeanLaw tracks attorney compensation and origination credit as time is billed and collected, and partners may be paid on those reports. Not every system records origination against a matter. The firm checks early whether the destination can, and saves the historic compensation reports whatever the answer.

  5. It was never the case file

    Parties, deadlines, documents and correspondence were never in LeanLaw. Some firms pair it with Clio or MyCase for those, and others use folders and Outlook. A move to an all-in-one system therefore draws on several sources, and the matter list from LeanLaw is used as the index that ties them together.

More about moving off LeanLaw

Where it is going

Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.

  1. Every figure needs a value code

    Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.

  2. Lists are set up first

    Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.

  3. Documents go to sub-tabs

    Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.

  4. Reminders split two ways

    Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.

  5. Assembly runs its own conversions

    Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.

More about moving into Neos

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 Neos 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 LeanLaw and checking each trial against LeanLaw.

  1. Analysis

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

  3. Trial load

    The data is loaded into Neos as a trial and checked against LeanLaw: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in LeanLaw are frozen for an agreed window, the data is collected a final time and Neos 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 LeanLaw as at the cutover date. LeanLaw 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 LeanLaw 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 fromLeanLaw
Moving toNeos

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 LeanLaw holds

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

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

Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.

Set-up decisions in Neos

  • Set case types, statuses and staff roles
  • Agree the value code list with accounts staff
  • Build checklists for each case type and stage
  • Create user-defined fields for data the tabs lack
  • Prepare document templates for the generation wizard
  • Connect Microsoft 365, QuickBooks and the phone system

Questions

LeanLaw to Neos: what firms ask

If we stop using LeanLaw, do we lose our QuickBooks Online data?

No. QuickBooks Online is a separate subscription in the firm’s own name, and the invoices, payments and trust entries that synced into it stay there. What goes when LeanLaw goes is the legal layer on top: time narratives, matter ledgers and the reports built from them, which is why those are extracted.

Can the new system take over the same QuickBooks company?

Often, yes. It needs to be told which customers and open invoices already exist so that it links to them and does not create a second set. The switch is made at an agreed date, with LeanLaw’s sync turned off first and the receivables total compared on both sides.

We use LeanLaw with Clio for case management. Which is the source for matters?

Both, for different things. Clio would hold the case detail, documents and calendar, and LeanLaw the time, bills and trust ledgers. The two matter lists are compared in the analysis. A matter that appears in one and not the other is traced and resolved before anything is loaded.

Do trust balances in LeanLaw have a place in Neos?

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 LeanLaw before the plan is fixed. If Neos 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 LeanLaw have a place in Neos?

Most of it does on paper. Notes, tasks, trust ledgers, custom fields 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 Neos is kept as a readable archive, and you see which before the move.

What has to be decided before LeanLaw data is loaded into Neos?

Time entries, billing records and templates are carried with mapping, so each mapping is agreed with you first. Notes, tasks, trust ledgers, custom fields 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

LeanLaw and Neos are the names and marks of their owners, used here only to identify the two systems.

Moving from LeanLaw to Neos?

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

We reply within one business day.