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

Data migration route

Laserfiche to SimpleLaw migration

Laserfiche is a server-based document management system, and SimpleLaw is a cloud practice management system. Documents and email move out of a store organised by profile and onto the matters they belong to.

FromLaserficheServer
  1. Documents: Carried across
  2. Notes: Carried across
  3. Custom fields: Carried with mapping
  4. Emails: Confirmed in the analysis
  5. Tasks: Confirmed in the analysis
  6. Templates: Confirmed in the analysis
  7. Intake: Confirmed in the analysis
ToSimpleLawCloud
  • 2 carried
  • 1 mapped
  • 4 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Laserfiche to SimpleLaw

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

Records in Laserfiche and their place in SimpleLaw
RecordIn LaserficheIn SimpleLawWhat is planned
DocumentsFiles stored in or linked from the systemHeldEntries in repository folders: scanned pages with text, or electronic files.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 partImported emails use an Email template that holds the message details.To be confirmedConfirmed in the analysis
NotesFile notes, matter notes and contact notesHeld in partAnnotations on documents are stored in the repository database.Has a placeCarried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedWorkflow and forms are part of the platform; use varies by installation.Has a placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldFields and templates are defined in repository administration.Has a placeCarried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt using SimpleLaw’s own automation.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeLeads and intake forms.Confirmed in the analysis

What the plans mean

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

Profiled documents become matter documents.

A document management system files by profile: client, matter, author, document type, version. A practice management system files by matter. The move from Laserfiche to SimpleLaw is a translation from one to the other, and it depends on the client and matter numbers in Laserfiche matching matters that exist in SimpleLaw. Where they do not match, documents have nowhere to land. So the matter list is settled first and the documents follow it.

Versions and security each need a decision. Some practice systems keep every version of a document, others keep the latest and treat the rest as separate files. A restricted workspace has to become a restricted matter, or the restriction is lost on the way. Filed email comes across as message files against the matter. A document store holds no ledgers, so this route has no financial cutover.

Laserfiche runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. SimpleLaw is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

Where the data is now

Many Laserfiche documents are not files in the usual sense. An imaged document is a set of scanned pages with recognised text stored beside them, held in a volume and described in the database. Getting it out means generating a PDF from those pages. Electronic documents come out in their original format. The export has to handle both kinds and carry the template fields with them.

  1. Imaged and electronic documents

    An imaged document has page images and text but no original file, and opens in Laserfiche’s own viewer. An electronic document is tied to a file such as a Word document. On export, imaged documents are rendered to PDF with their text, and that conversion is tested for page counts and for whether the result can be searched.

  2. Templates carry client and matter

    Fields are grouped into templates. Where a firm built a client-file template with client number, matter number and document type, those fields drive the mapping. Documents with no template, or with the General template only, are filed from their folder path instead, and the two groups are counted separately.

  3. Volumes and the database

    In a self-hosted repository the content is in volumes, which can be spread over several drives or servers, and everything that says what it is sits in the database. Extraction is done through Laserfiche, not by copying volume folders, because a volume on its own does not say which pages make up which document.

  4. Retention rules

    A repository used for records management has retention rules applied to its folders. A legal document system may record when a matter closed but rarely has the same machinery. The rules in force are written down before cutover, so the firm’s retention obligations are not lost along with the software.

  5. Rights on fields and templates

    Access can be set on folders and documents, and also on individual fields and templates, so a user may see a document but not one sensitive field on it. Field-level restrictions rarely have an equivalent elsewhere. Sensitive fields are dropped, loaded to a restricted note, or the documents themselves are restricted.

More about moving off Laserfiche

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.

Nothing financial lands in SimpleLaw on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Laserfiche holds and how it is organised, then agree with you where each kind of record will sit in SimpleLaw. 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 SimpleLaw and checked against Laserfiche: 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 Laserfiche, a final pass over a weekend picks up what changed since the trial. Laserfiche 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 Laserfiche 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 fromLaserfiche
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 Laserfiche 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

Laserfiche to SimpleLaw: what firms ask

Most of our Laserfiche is scanned paper. Does it stay searchable?

It can. Laserfiche stores the recognised text for each scanned page, and an export to PDF can include it as a text layer. Whether the new system searches that layer or runs its own recognition differs by product. A sample is loaded and searched during the trial, before the full volume is converted.

Can folder structure and template fields both be kept?

Usually one becomes the primary key and the other is kept as supporting data. If the destination files by client and matter, those fields decide where a document goes, and the old folder path is written into a description or sub-folders. Fields with no equivalent are listed for the firm to keep as notes or drop.

Do documents from Laserfiche keep their folders and dates in SimpleLaw?

SimpleLaw stores documents. Uploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.

Does everything in Laserfiche have a place in SimpleLaw?

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

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

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

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

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