Data migration route
Laserfiche to Clio Manage migration
Laserfiche is a server-based document management system, and Clio Manage is a cloud practice management system. Documents and email move out of a store organised by profile and onto the matters they belong to.
LaserficheServer- Documents: Carried across
- Emails: Carried across
- Notes: Carried across
- Custom fields: Carried with mapping
- Tasks: Confirmed in the analysis
- Templates: Confirmed in the analysis
- Intake: Confirmed in the analysis
Clio ManageCloud- 3 carried
- 1 mapped
- 3 to confirm
What moves
What moves from Laserfiche to Clio Manage
Each row is a kind of record Laserfiche holds, whether Clio Manage has a place for it, and what is planned. On this route three kinds of record carry across, one kind needs mapping and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldEntries in repository folders: scanned pages with text, or electronic files. | Has a placeFiled under the matter; Clio scopes document migration separately from data. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partImported emails use an Email template that holds the message details. | Has a placeHeld as communications on the matter, with phone logs. | Carried across |
| NotesFile notes, matter notes and contact notes | Held in partAnnotations on documents are stored in the repository database. | Has a placeMatter notes and contact notes each have a template. | Carried across |
| TasksTo-dos and workflow steps assigned to people | To be confirmedWorkflow and forms are part of the platform; use varies by installation. | Has a placeTasks have a migration template. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldFields and templates are defined in repository administration. | Has a placeCreated first, then filled from the custom field templates. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a placeRebuilt as Clio document templates with its merge fields. | Confirmed in the analysis |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | No placeLeads and intake forms belong in Clio Grow. | Confirmed in the analysis |
What the plans mean
- Carried across
- Clio Manage has a place for this kind of record. It is loaded there and checked against Laserfiche.
- Carried with mapping
- Clio Manage 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 Clio Manage is a translation from one to the other, and it depends on the client and matter numbers in Laserfiche matching matters that exist in Clio Manage. 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. Clio Manage 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
Leaving Laserfiche
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Clio Manage
Clio Manage is loaded through its migration templates, one spreadsheet per kind of record, imported in a fixed order with contacts first. Clio’s own migration guide is plain about the limit: balances come across, financial history does not. So a load into Clio is planned as records plus opening positions, with the old system kept for the history behind them.
Matters link by client name
The matters template ties each matter to its client by an exact match on first name, last name or company name. A client spelt two ways in the old system becomes two contacts, or a matter assigned to an unknown client. This is why contact clean-up is finished before the first trial load, not after it.
Decide the numbering scheme first
Clio numbers imported matters itself unless the account is set to manual numbering, in which case the old number is supplied in the template. That setting and the firm’s preferred scheme are decided before any matter is loaded. The Client Reference field is available for an old file number the firm still wants to see.
Balances, one line each
Under Clio’s standard migration, an outstanding balance arrives as one line per matter and a trust balance as one line per matter or contact. Past invoices, billed time, payments and trust transactions are listed as data that cannot be migrated. The trust total is reconciled against the old system’s closing report on the trial load.
Custom fields must exist
Matter and contact custom fields are created in Clio before their values are imported, each with a field type. Accounts set up for a particular practice area come with preconfigured fields and matter templates, which affects the mapping. We compare those with the old system’s fields and add only what is missing.
Rates and permissions by hand
Billable rates for users, clients and matters are not part of an import. Neither are user permissions or settings. They are entered in Clio during set-up from a schedule the firm confirms, and a sample of imported unbilled time is checked against that schedule before the trial load is signed off.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Clio Manage on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Laserfiche holds and how it is organised, then agree with you where each kind of record will sit in Clio Manage. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into Clio Manage 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.
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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Laserfiche holds
What is in it, how its records link, and where each piece would sit in Clio Manage. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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 Clio Manage
Loaded data is not yet a working system. This is what NewLaw sets up in Clio Manage, beyond the migration, so that people can work in it from the first day.
Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.
Set-up decisions in Clio Manage
- Matter numbering scheme, practice areas and matter stages
- Custom fields for matters and contacts, by practice area
- Document templates with merge fields, uploaded from Word or PDF
- Billing settings, user and client rates, and trust accounts
- Roles and permissions for each user
- Outlook add-in, Clio Drive and the accounting connection
Questions
Laserfiche to Clio Manage: 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 Clio Manage?
Clio Manage stores documents. Filed under the matter; Clio scopes document migration separately from data. 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 Clio Manage?
Most of it does on paper. 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 Clio Manage is kept as a readable archive, and you see which before the move.
What has to be decided before Laserfiche data is loaded into Clio Manage?
Custom fields are carried with mapping, so each mapping is agreed with you first. 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.
Other routes
Other routes from Laserfiche and into Clio Manage
Other destinations from Laserfiche
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Laserfiche and Clio Manage are the names and marks of their owners, used here only to identify the two systems.
Moving from Laserfiche to Clio Manage?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.