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

Data migration route

SimpleLaw data to Full data export

SimpleLaw is a cloud practice management system, and Full data export is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what SimpleLaw holds and keeps it readable and open to queries.

FromSimpleLawCloud
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Documents: Exported in full
  4. Notes: Exported in full
  5. Calendar: Exported in full
  6. Tasks: Exported in full
  7. Time and expenses: Exported in full
  8. Billing: Exported in full
  9. Trust money: Exported in full
  10. Emails: Exported with mapping
  11. Custom fields: Exported with mapping
  12. Templates: Exported with mapping
  13. Intake: Exported with mapping
ToFull data exportFiles
  • 9 carried
  • 4 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from SimpleLaw to Full data export

Each row is a kind of record SimpleLaw holds, whether Full data export has a place for it, and what is planned. On this route nine kinds of record carry across and four kinds need mapping.

Records in SimpleLaw and their place in Full data export
RecordIn SimpleLawIn Full data exportWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldThe vendor uses matter and case interchangeably.Has a placeA matters table keyed by the original matter number.Exported in full
ContactsClients, other parties and referrersHeldLeads, clients and other contacts in one CRM.Has a placeA contacts table and a table of each contact’s role on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeldStored on SimpleLaw’s servers or in the firm’s Dropbox, Google Drive or OneDrive.Has a placeFiles under their original names, in client and matter folders.Exported in full
EmailsEmails saved to matters or to the storeHeld in partEmails sent from within SimpleLaw through Google or Outlook are tracked by matter.Has a place in partFiled emails as message files in the matter’s folder, if the source exposes them.Exported with mapping
NotesFile notes, matter notes and contact notesHeldClients can also add notes through the portal.Has a placeA notes table with matter, author and date for each note.Exported in full
CalendarAppointments, court dates and deadlinesHeldAppointments by firm member or type, synced with Google or Outlook.Has a placeA table of appointments and key dates; nothing shows it as a diary.Exported in full
TasksTo-dos and workflow steps assigned to peopleHeldWorkflows create tasks, appointments and documents for standard case types.Has a placeA table of tasks with assignee, due date and status.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldOne timer per matter, plus manual entries.Has a placeA time entries table with fee earner, matter, units, rate and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldHourly, flat fee, instalment, contingency, pro bono and LEDES invoices.Has a placeInvoice, line and receipt tables; invoice PDFs can be kept beside them.Exported in full
Trust moneyTrust or client account ledgers and balancesHeld in partTrust billing and initial trust payments are supported; ledger detail was not confirmed.Has a placeA trust transactions table; ledger reports can be kept as PDF beside it.Exported in full
Custom fieldsFields and record types the firm added itselfHeldCustom fields feed intake forms, reports and document automation.Has a placeExtra columns under their original field names.Exported with mapping
TemplatesPrecedents, document templates and automationHeldReusable templates filled from stored data and intake answers.Has a place in partTemplate files only; the merge fields in them will not run.Exported with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldWebsite forms, custom intake forms and lead tracking in the CRM.Has a place in partAn enquiries table, where the source tracked leads.Exported with mapping

What the plans mean

Exported in full
Full data export has a place for this kind of record. It is loaded there and checked against SimpleLaw.
Exported with mapping
Full data export holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.

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

Not a new system. A complete copy the firm can query.

Writing SimpleLaw out to Full data export is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in SimpleLaw as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

SimpleLaw is hosted by its maker and Full data export sits 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 SimpleLaw will release depends on its export tools, and that is confirmed in the analysis.

Where the data is now

SimpleLaw lets a firm rename and rearrange a good deal, so the first step in leaving it is learning this firm’s version: what it calls its record types, where it chose to store files and which clients were given portal access. With that understood the move itself is usually modest in size, since the product is sold to solo lawyers and small firms.

  1. Files in your drive or theirs

    A firm chooses whether documents sit on SimpleLaw’s servers or in its own Dropbox, Google Drive or OneDrive. In the second case the files already belong to the firm and need no extraction. What has to be preserved is the record of which folder belongs to which matter.

  2. The firm’s own labels

    Documents, activities, expenses and contact IDs can all be renamed to suit the firm. Staff describe their records in those terms, and screens and reports follow them. A short glossary is written first, so that something the firm calls a Disbursement or a File Ref is mapped to the right field in the destination.

  3. What clients added

    Through the portal, clients upload documents, add notes, complete intake forms and message the legal team. Client-written notes sit among the firm’s own. They are marked with their author on the way out, so that in the new system nobody mistakes a client’s comment for a lawyer’s file note.

  4. Referred and co-counsel matters

    Matters referred or shared with co-counsel through the SimpleLaw network are visible to both firms inside the platform. That shared view does not exist elsewhere. The other lawyer is recorded as a contact with a role on the matter, and the firm tells co-counsel how documents will be exchanged afterwards.

  5. Payments recorded in two ways

    Clients may pay through an integrated processor, or the firm may manage payments offline or through QuickBooks. Where the second route was used, the payment record inside SimpleLaw may be incomplete. Receivables are checked against the bank statement or QuickBooks before any balance is carried forward to the new system.

More about moving off SimpleLaw

Where it is going

A full export is judged by whether a stranger can use it. In five years the question will be something like: what was the trust balance on this matter the day it closed, and where is the signed agreement. The export is planned backwards from questions of that kind, and it is checked against the live system while the live system can still be opened.

  1. Tables that still join up

    Each kind of record becomes its own table: matters, contacts, time entries, invoices, trust transactions. The identifiers that link them are kept in every table, so a time entry can still be traced to its matter and its fee earner. An export that keeps the rows and drops the keys cannot be rejoined later.

  2. Documents with an index

    Documents are written to folders by client and matter under their original names. On their own they can be found only by name. An index listing each file with its matter number, title, author, dates and path is what lets someone find the right version of a lease among forty thousand files without the old system’s search. What the index records is settled in the analysis.

  3. Reports a person can read

    Raw tables do not satisfy an auditor or a former client. The firm decides which reports are also printed to PDF from the old system as at the final date: trust ledgers, matter ledgers, debtor lists and issued invoices are the usual candidates. They cannot be regenerated once the licence ends.

  4. What an export does not keep

    Screens, workflows, document automation, saved searches and user permissions belong to the software and stay with it. Figures the system calculated on the fly, such as a matter’s unbilled total, exist in an export only if they were captured as a report. The firm is told which of these are being let go.

  5. Checked while the source is open

    Record counts and financial totals in the export are reconciled to the live system: number of matters, sum of trust balances, total debtors, document count per matter on a sample. This is done before the subscription lapses or the server is turned off, because afterwards there is nothing left to compare against.

More about moving into Full data export

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what SimpleLaw holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything SimpleLaw holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to Full data export as a trial and checked against SimpleLaw: record counts, totals where SimpleLaw holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in SimpleLaw, the export is run a final time and checked again. There is nothing to go live. SimpleLaw is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

Fixed price, agreed after the analysis. How NewLaw moves legal data

Start

Start this migration

Tell us what is in SimpleLaw 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 fromSimpleLaw
Moving toFull data export

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

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

Full data export is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

With no product to configure, the set-up is custody, and the decisions are the firm’s. Someone there owns the export, knows where it is kept and can open it. Access needs restricting, because it contains every client’s affairs in one place with none of the old system’s security. The firm sets a destruction date from its retention obligations and decides how the next custodian will learn to use it.

What is agreed and set up

  • Folder layout for tables, documents and reports
  • What the key to tables, columns and identifiers records
  • Where the copies are stored and who is custodian
  • Who may open it, as approved by a partner
  • Which look-ups staff must be able to do unaided
  • Retention period and the date it is next reviewed

Questions

SimpleLaw to Full data export: what firms ask

Does SimpleLaw replace our accounting software?

No. It records time, raises invoices and takes payments, and it can sync with QuickBooks. The general ledger, payroll and tax reporting stay in the accounting package. A firm moving to it from an all-in-one system should plan where its books will be kept before the practice data is moved.

Our documents are in Google Drive. Do they have to be uploaded?

Not necessarily. SimpleLaw offers Google Drive, Dropbox and OneDrive as storage options alongside its own servers. If the firm keeps Google Drive, the work is arranging folders so each matter finds its files. How the connection handles an existing folder tree is confirmed in the analysis.

We are leaving SimpleLaw. Can clients still reach their documents?

Only for as long as the SimpleLaw account and its portal remain active. Documents clients uploaded are extracted with the matter. If the new system has a client portal, access is set up again there, and clients are told in advance where to find their files from the cutover date.

Does the copy in Full data export hold trust ledgers from SimpleLaw?

Yes. A trust transactions table; ledger reports can be kept as PDF beside it. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in SimpleLaw as at the export date.

Does everything in SimpleLaw have a place in Full data export?

On paper, yes: each kind of record SimpleLaw holds has a place in Full data export. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.

What has to be decided before SimpleLaw is written out to Full data export?

Emails, custom fields, templates and intake records are exported with mapping, so each mapping is agreed with you first. The firm also decides who may open the archive and how long it is kept.

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

SimpleLaw and Full data export are the names and marks of their owners, used here only to identify the two systems.

Moving from SimpleLaw to Full data export?

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

We reply within one business day.