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

Data migration route

LeanLaw to Server drives migration

LeanLaw is a cloud accounting and billing 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.

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

What moves

What moves from LeanLaw to Server drives

Each row is a kind of record LeanLaw holds, whether Server drives have a place for it, and what is planned. On this route one kind needs mapping, five kinds have no place in Server drives and are archived and four kinds are confirmed in the analysis.

Records in LeanLaw and their place in Server drives
RecordIn LeanLawIn Server drivesWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters as billing records, with budgets, rates and fee arrangements.No placeA matter becomes a folder; its details survive only in an index file.Kept as a readable archive
ContactsClients, other parties and referrersHeld in partClients and billing contacts only.No placeCan be kept only as an exported spreadsheet.Kept as a readable archive
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs a text or PDF file per matter, not as separate records.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedNo placeConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime and expenses tied to client and matter.No placeOnly as exported reports or spreadsheets.Kept as a readable archive
BillingInvoices, payments and debtor balancesHeldHourly, flat fee and recurring fixed fees; LEDES on some plans.Has a place in partInvoices as PDF files; no ledger.Kept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldClient and matter trust ledgers, with the trust bank account kept in QuickBooks Online.No placeOnly as exported ledger reports kept as files.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedNo placeConfirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partInvoice templates.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 pipelinesTo be confirmedNo placeConfirmed in the analysis

What the plans mean

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 LeanLaw 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 LeanLaw 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 LeanLaw, 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.

LeanLaw 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 LeanLaw will release depends on its export tools, and that is confirmed in the analysis.

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

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 LeanLaw 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 LeanLaw: 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 LeanLaw, a final pass over a weekend picks up what changed since the trial. 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 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 LeanLaw 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

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

No. Server drives do not keep trust ledgers. Only as exported ledger reports kept as files. Trust records from LeanLaw are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.

What happens to records Server drives have no place for?

On this route that is matters, contacts, time entries, billing records and trust ledgers. They are exported from LeanLaw 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 LeanLaw data is loaded into Server drives?

Templates are carried with mapping, so each mapping is agreed with you first. Notes, tasks, custom fields and intake records 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

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

Moving from LeanLaw 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.