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

Data migration route

LegalServer to SimpleLaw migration

LegalServer is a cloud case management system for legal aid work, and SimpleLaw is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in SimpleLaw, often from a separate accounts package.

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

What moves

What moves from LegalServer to SimpleLaw

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

Records in LegalServer and their place in SimpleLaw
RecordIn LegalServerIn SimpleLawWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases and matters, with case types configured for each site.Has a placeCarried across
ContactsClients, other parties and referrersHeldClients and the other people connected with a case.Has a placeAs leads, clients or other contacts in the CRM.Carried across
DocumentsFiles stored in or linked from the systemHeldStored on the case, or linked from SharePoint, Google Shared Drives or Dropbox.Has a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive.Carried across
EmailsEmails saved to matters or to the storeHeld in partBuilt-in email, and email sent to a case from Gmail through an integration.To be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesHeldCase notes.Has a placeCarried across
CalendarAppointments, court dates and deadlinesHeldAppointments, events, tasks and deadlines; entries can show in Outlook.Has a placeCarried across
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldTimekeeping, used for grant and funder reporting.Has a placeCarried across
BillingInvoices, payments and debtor balancesTo be confirmedBuilt for free legal services; client invoicing was not confirmed.Has a place in partInvoices are created in the product; loading invoice history is confirmed in the analysis.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a place in partTrust balances are supported; history depth is confirmed in the analysis.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeGeneral ledger stays in QuickBooks or another accounting package.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldSites add their own fields, forms and processes without code.Has a placeCarried with mapping
TemplatesPrecedents, document templates and automationHeldBuilt-in document templates; HotDocs, Docassemble and Gavel are integrations.Has a place in partTemplates are rebuilt using SimpleLaw’s own automation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldConfigurable client intake, with a poverty level assessment and conflict check.Has a placeLeads and intake forms.Carried across

What the plans mean

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

Cases come across. The accounts are set up new.

A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to SimpleLaw brings those two sources together. The case records come from LegalServer. Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.

Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in SimpleLaw, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.

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

Where the data is now

Each agency configures its own intake, case types and fields, so a move off LegalServer starts with that site’s configuration, not with a standard list of tables. The data most at risk is the data a commercial practice system never asks for: eligibility answers, funding codes, outcomes and the time recorded against each grant.

  1. Each site has its own shape

    Intake processes, case types and data fields are set up by the agency’s own administrators, often over many years. Two programs on the same product can hold quite different records. The analysis reads this site’s configuration first and lists every field that holds data, including ones no current staff member remembers adding.

  2. Time belongs to funders

    Timekeeping exists to show funders what their grant paid for, so entries are tied to grants and funding sources, not to a bill. A practice system records time against a matter for invoicing. The funding link has to be carried as its own field, or grant reports for the period before the move cannot be reproduced.

  3. Documents may live elsewhere

    LegalServer can store files itself, or link a case to folders in SharePoint, Google Shared Drives or Dropbox. On a site that uses those integrations the documents are not in the case management system at all. Where the files are is established before anything else, because it decides whether they are moved or simply linked again.

  4. Eligibility and outcome data

    Intake assesses a client against the poverty level and runs a conflict check, and outcomes are tracked across cases for reporting. These answers justify the service to an auditor. They are carried as fields where the destination allows, and otherwise as a dated intake summary filed on the case.

  5. Feeds from courts and agencies

    Some sites receive court data several times a day, create cases from a county system, or send counselling data to HUD. These connections are part of how the office works. Each is listed with what it sends or receives, and a decision is made on whether it is rebuilt, replaced by manual entry, or retired.

More about moving off LegalServer

Where it is going

Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.

  1. Lead, client or contact

    A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.

  2. Billing type on each matter

    Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.

  3. Storage chosen before loading

    If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.

  4. Custom fields named for templates

    Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.

  5. Portal access client by client

    The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.

More about moving into SimpleLaw

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  1. Analysis

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

  3. Trial load

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

  4. Cutover

    Changes in LegalServer are frozen for an agreed window, the data is collected a final time and SimpleLaw 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 LegalServer as at the cutover date. LegalServer 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 LegalServer 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 fromLegalServer
Moving toSimpleLaw

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

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

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

The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.

Set-up decisions in SimpleLaw

  • Labels for documents, activities, expenses and contact IDs
  • Custom fields and intake forms for each practice area
  • Document templates and the attorney-client agreement
  • Workflows for case types that follow a standard process
  • User permission sets and client portal visibility
  • QuickBooks connection and the online payment processor

Questions

LegalServer to SimpleLaw: what firms ask

Can a commercial practice system hold legal aid data?

It can hold the cases, people, notes, documents and time. It will not have funding codes, eligibility screening or funder reports unless they are built with custom fields and reports. The analysis sets out which of those can be rebuilt in the chosen system and which reporting would have to be done outside it.

What happens to cases closed years ago?

Closed cases matter in legal aid for conflict checks and for funder audits. Bringing every case means a returning client or an adverse party is still found. If older cases are left out, their names should still be loaded for conflict searching, and the full record stays in the read-only copy.

Our documents are in SharePoint, not in LegalServer. Must they move as well?

Not necessarily. If LegalServer only links to SharePoint, the files are already in the program’s own Microsoft 365. They can stay where they are and be linked from the new system, or be moved into it. The choice depends on how the destination stores documents and is made in the analysis.

Do trust balances in LegalServer have a place in SimpleLaw?

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

Most of it does on paper. Emails, billing records, 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 SimpleLaw is kept as a readable archive, and you see which before the move.

What has to be decided before LegalServer data is loaded into SimpleLaw?

Custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails, billing records, 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

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

Moving from LegalServer to SimpleLaw?

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

We reply within one business day.