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

Data migration route

Laserfiche to Litify migration

Laserfiche is a server-based document management system, and Litify is a cloud case management system. The move is matching each file in Laserfiche to its case in Litify.

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

What moves

What moves from Laserfiche to Litify

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

Records in Laserfiche and their place in Litify
RecordIn LaserficheIn LitifyWhat is planned
DocumentsFiles stored in or linked from the systemHeldEntries in repository folders: scanned pages with text, or electronic files.Has a placeLoaded to the document component and attached to matters.Carried across
EmailsEmails saved to matters or to the storeHeld in partImported emails use an Email template that holds the message details.Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesHeld in partAnnotations on documents are stored in the repository database.To be confirmedConfirmed in the analysis
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 placeCustom fields are created before loading.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt in Litify’s document generation.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeLoaded as intakes.Confirmed in the analysis

What the plans mean

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

Every document goes to the case it belongs to.

A case management system expects each document to sit on a case, usually in a category such as correspondence, medical records or court documents. Laserfiche organises files its own way, by profile or by folder. So the move needs two rules: which case a file belongs to, and which category it goes in. The first comes from client and matter references or folder names. The second comes from a document type or a subfolder, and where neither exists the files arrive uncategorised and are marked as such.

Cases must exist in Litify before documents can be attached to them. If the system is already live, files are matched to its case list and the unmatched ones are reported. If it is new, the case list is created first. Dates, authors and file names are kept. Email comes across as message files. Where several versions of a document exist, the firm chooses between loading the latest and loading them all.

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. Litify 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 Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.

  1. The design comes first

    Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.

  2. One party, many roles

    Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.

  3. Open enquiries load as intakes

    Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.

  4. Documents load after records

    Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.

  5. Validation rules reject bad rows

    A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.

More about moving into Litify

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Litify on this route, which makes it repeatable: a load can be run again until it is right. The maker of Litify 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 Laserfiche and checking each trial against Laserfiche.

  1. Analysis

    We read what Laserfiche holds and how it is organised, then agree with you where each kind of record will sit in Litify. 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 Litify 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 toLitify

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 Litify. 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 Litify

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

A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.

Set-up decisions in Litify

  • Define intake questionnaires and the rules for conversion
  • Set case types, matter stages and page layouts
  • Build matter plans that create tasks at each stage
  • Design document folders and generation templates per case type
  • Configure user roles and sharing for restricted matters
  • Decide on timekeeping, billing and accounting integrations

Questions

Laserfiche to Litify: 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 Litify?

Litify stores documents. Loaded to the document component and attached to matters. 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 Litify?

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

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

Emails and custom fields are carried with mapping, so each mapping is agreed with you first. Notes, 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 Litify are the names and marks of their owners, used here only to identify the two systems.

Moving from Laserfiche to Litify?

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

We reply within one business day.