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

Data migration route

Neos to Filevine migration

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

FromNeosCloud
  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. Time and expenses: Carried with mapping
  9. Billing: Carried with mapping
  10. Trust money: Carried with mapping
  11. Custom fields: Carried with mapping
  12. Templates: Carried with mapping
  13. Intake: Carried with mapping
ToFilevineCloud
  • 7 carried
  • 6 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Neos to Filevine

Each row is a kind of record Neos holds, whether Filevine has a place for it, and what is planned. On this route seven kinds of record carry across and six kinds need mapping.

Records in Neos and their place in Filevine
RecordIn NeosIn FilevineWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases laid out in tabs, with a Management tab for fee and referral details.Has a placeLoaded as projects of a defined project type.Carried across
ContactsClients, other parties and referrersHeldParties, providers, counsel, case contacts and related contacts.Has a placeContact cards, linked to projects.Carried across
DocumentsFiles stored in or linked from the systemHeldCase Docs tab with sub-tabs, viewable as a list or as folders.Has a placeDocs section with folders. Templated project folders can be set per type.Carried across
EmailsEmails saved to matters or to the storeHeldEmails can be tagged to the case file. Outlook is integrated.Has a placeHeld in the activity feed of the project.Carried across
NotesFile notes, matter notes and contact notesHeldCase notes, including Special Notes.Has a placeHeld as notes in the activity feed.Carried across
CalendarAppointments, court dates and deadlinesHeldCase calendars, with statute and deadline alerts.Has a placeDeadlines and calendar events.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldChecklists and case tasks, which feed staff dashboards.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldTimers on a case, which can create value items.Has a place in partNeeds the Billing product enabled.Carried with mapping
BillingInvoices, payments and debtor balancesHeldInvoices in PDF, Word or LEDES format. Payments through LawPay.Has a place in partNeeds the Billing product enabled.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeld in partTrust requests can be raised and paid through LawPay.Has a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis.Carried with mapping
Custom fieldsFields and record types the firm added itselfHeldUser-defined fields can be added to case tabs.Has a placeCustom sections and fields per project type.Carried with mapping
TemplatesPrecedents, document templates and automationHeldA document generation wizard merges templates for one case or many.Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntakes tab and intake forms.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 Neos.
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.

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. Neos 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 Neos 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 Neos is kept running until the checks on Filevine are finished.

Where the data is now

A firm leaving Neos is leaving a cloud system whose data sits in a database dedicated to that firm. The structure runs tab by tab, and each tab is in effect a table. Many Neos firms came from Needles or Trialworks, so the data often carries conventions two systems old, and the analysis has to read those as well.

  1. A database per firm

    Assembly holds each firm’s records in a separate Azure SQL database. For a migration that means the data set is self-contained, with nothing shared with other customers. How a copy is obtained is arranged with the firm at the start, and the copy and the document files are taken at the same point in time.

  2. Value items hold the money

    Bills, costs, time and settlement entries are value items on the Value tab, with transactions beneath them for payments. A general system splits those across disbursements, time, invoices and receipts. Each value code is mapped to one of them, and the case totals are compared before and after.

  3. Fields inherited from Trialworks

    When a Trialworks firm is converted to Neos, some standard fields land in user-defined fields and in document sub-tabs named after the old tabs. A firm that has been through that carries two layers of structure. Both are read, so a field that looks custom is recognised as the old system’s standard field.

  4. Checklists and calendars

    Work in progress is split between checklist items and case calendar entries, and dashboards are built from both. Open checklist items become tasks in the destination. Calendar entries become events. The two are counted separately in the trial load, because losing either leaves a fee earner with an empty list on the first morning.

More about moving off Neos

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.

Trust money moves on this route, so the trust cutover gets a rehearsal of its own.

  1. Analysis

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

  3. Trial load

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

  4. Cutover

    Changes in Neos are frozen for an agreed window, the data is collected a final time and Filevine goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. Neos 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 Neos 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 fromNeos
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 Neos 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

Neos to Filevine: what firms ask

We have seen NEOS Web and NEOS DB listed. Are they different from Neos?

Assembly’s own site describes a single product, Neos, used in a browser, with each firm’s records in a dedicated Azure SQL database. Some software lists show NEOS Web and NEOS DB as separate entries. Which system a firm actually holds, and where its data sits, is identified at the start of the analysis.

We are on Needles. Is Neos just an upgrade?

No, it is a migration. Needles keeps its data in a SAP ASE database on the firm’s server and Neos uses Azure SQL in the cloud, so records and documents are converted, not upgraded in place. Assembly says the case logic is the same, which shortens the mapping compared with a move elsewhere.

Can Neos replace our accounting system?

Not the general ledger. Neos records case money as value items, raises invoices and trust requests, and takes payments through LawPay, and it links to QuickBooks Desktop or Online for the books. A firm moving from a system with built-in accounting plans a QuickBooks set-up as part of the same project.

Do trust balances in Neos have a place in Filevine?

In part. Trust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. The analysis sets out which trust records have a place in Filevine and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

Does everything in Neos have a place in Filevine?

On paper, yes: each kind of record Neos holds has a place in Filevine. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.

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

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

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

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