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

Data migration route

CloudLex to Filevine migration

CloudLex is a cloud case management system for personal injury work. Filevine is a case management system, run the same way. The records line up case for case, and the detail is in the fields and stages.

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

What moves

What moves from CloudLex to Filevine

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

Records in CloudLex and their place in Filevine
RecordIn CloudLexIn FilevineWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters with type, status and sub-status. Intakes are a separate record.Has a placeLoaded as projects of a defined project type.Carried across
ContactsClients, other parties and referrersHeldA firm-level directory, linked to matters by role.Has a placeContact cards, linked to projects.Carried across
DocumentsFiles stored in or linked from the systemHeldPer matter, in categories and folders, with version control and party association.Has a placeDocs section with folders. Templated project folders can be set per type.Carried across
EmailsEmails saved to matters or to the storeHeldMatter email syncs with Microsoft 365. Gmail and Outlook add-ins file to a matter.Has a placeHeld in the activity feed of the project.Carried across
NotesFile notes, matter notes and contact notesHeldMatter notes, also reachable from the global side panel.Has a placeHeld as notes in the activity feed.Carried across
CalendarAppointments, court dates and deadlinesHeldEvents tied to the matter, including deadlines.Has a placeDeadlines and calendar events.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldManual tasks and tasks generated by workflow templates.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledTo be confirmedHas a place in partNeeds the Billing product enabled.Confirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedHas a place in partNeeds the Billing product enabled.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedTo be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCustom sections and fields per project type.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partWorkflow templates by matter type and status. Document templates were not confirmed.Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLead Manager and Intake Manager. An intake is converted to a matter.Has a place in partLeads belong in Lead Docket, which passes signed clients to Filevine.Carried with mapping

What the plans mean

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

Case to case, field by field.

Two case management systems look alike from a distance and differ in almost every detail. Each has its own idea of a case type, a stage, a party role and a deadline. CloudLex and Filevine may both hold a limitation date, yet one calculates it and the other stores what was typed. The mapping goes field by field and status by status, and the trial load is checked by opening real cases in both systems side by side.

Custom fields hold most of what the firm has built up. Years of intake answers, injury details or visa histories sit in fields the firm added itself. Each is matched to a field in Filevine, and anything unmatched is kept as a note on the case so that it can still be searched. Workflows and document templates are rebuilt in the new system’s own tools. Open tasks come across with their owners and due dates.

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

Where the data is now

Leaving CloudLex is a three-part job, because the firm’s records are split between Intake Manager, Matter Manager and Digital Archiver. Active matters carry the most structure, in the Details sections. Archived matters carry the most volume. The plan covers each part separately and states which archived files, if any, are being brought into the new system.

  1. The Details sections

    Medical information, medical bills, insurance, liens, expenses and settlement are separate sections of a matter, each a list of rows with amounts and dates. They map well to an injury-specific destination. In a general one, each section needs a home agreed in advance, and the outstanding balances on bills and liens are checked after loading.

  2. Closed matters in Digital Archiver

    Closed files are moved off the active list into Digital Archiver, where they stay searchable for the retention period. They are easy to forget when counting matters. The archive is inventoried at the start, and the firm chooses between loading those files, keeping an export, or leaving them where they are until retention ends.

  3. Negotiations and the settlement calculator

    A matter records its negotiations, and a calculator applies settlement rules to work out fees and the client’s share. The negotiation history is useful in the next system as a dated list. Calculator rules are firm settings, and they are entered again in the destination if it has an equivalent.

  4. Contacts linked by role

    One contact record serves every matter it appears on, as a provider, adjuster, attorney or referrer. That is tidy, and it means a merge or a typo affects many matters at once. Roles are extracted with the link, so an insurer on forty matters arrives once and is attached forty times.

  5. Client messages and texts

    Texts sent through Client Messenger are logged against the intake or matter. They are part of the file and often the only record of what a client was told. Such messages are carried as dated notes or as a transcript document on the matter, depending on what the destination can display.

More about moving off CloudLex

Where it is going

Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.

  1. Project types before data

    Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.

  2. One contact card per person

    Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.

  3. Lists become collection items

    Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.

  4. History goes into the feed

    File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.

  5. Billing is a separate switch

    The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.

More about moving into Filevine

How NewLaw runs it

Four steps, in this order.

No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Filevine, they get a rehearsed cutover of their own.

  1. Analysis

    We read what CloudLex holds and how it is organised, then agree with you where each kind of record will sit in Filevine. 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 Filevine and checked against CloudLex: 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

    After a short freeze on changes in CloudLex, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. CloudLex 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 CloudLex 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 fromCloudLex
Moving toFilevine

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

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

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

Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.

Set-up decisions in Filevine

  • Design project types, sections and fields for each practice area
  • Define phases and the tasks each phase should trigger
  • Build document templates that fill from project fields
  • Set teams, permissions and protected sections for restricted matters
  • Decide whether Billing and Payments are switched on
  • Connect Lead Docket so signed leads become projects

Questions

CloudLex to Filevine: what firms ask

CloudLex calls them matters. Does that make the move simpler?

Only in the naming. The structure under a matter is still personal injury data: treatment, bills, liens, insurance and settlement. A destination that also says matter may have no sections for those. What decides the effort is whether the new system has a place for each Details section, and that is settled in the analysis.

What do we do about files in Digital Archiver?

Decide early. Archived matters are retained for years and are rarely opened, so loading them into the new system is optional. The options are a full load, a summary record with documents, or an export held by the firm. Whatever is chosen, the count of archived matters is agreed and checked.

Will emails filed to a matter come across?

Emails saved to a matter from Outlook, Gmail or the built-in mail are part of the matter record and are in scope. They move as email files or as documents, with the date sent preserved so the correspondence still sorts in order. Mailboxes themselves stay in Microsoft 365 or Google and are not touched.

Do trust balances in CloudLex have a place in Filevine?

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

Most of it does on paper. Time entries, billing records, trust ledgers, the firm’s accounts and custom fields 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 Filevine is kept as a readable archive, and you see which before the move.

What has to be decided before CloudLex data is loaded into Filevine?

Templates and intake records are carried with mapping, so each mapping is agreed with you first. Time entries, billing records, trust ledgers, the firm’s accounts and custom fields 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

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

Moving from CloudLex to Filevine?

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

We reply within one business day.