Your personal injury firm has run on Needles for a decade, or moved to Neos when the cloud version arrived, and Filevine is next. The worry is not whether Filevine can hold the data. It is whether fifteen years of parties, checklists, provider records, lien notes and documents on a network share can come out in a form that means anything on the other side.
They can, with planning. Needles has a data model built around PI work that Filevine also understands, under different names. This page covers the specifics; the general steps are in the Filevine data migration checklist and the full set of pairs is at migrations. The SmartAdvocate to Filevine and CasePeer to Filevine pages describe similar moves.
Getting the data out of Needles (and out of Neos)
Needles is an on-premise application with a database on your own server, and access to that database is the first question. The built-in reporting can export case and party lists but usually not the full note history or checklist detail at volume, so a full extract may need the vendor, a reseller, or someone with direct database access. Find out who has administrator access and whether the database can be queried directly before you set dates.
Neos, the cloud successor, is easier: exports come through its reporting or the vendor on request, and there is no server to find. Either way, get the vendor's answer in writing on what they will provide and when; for firms still on Needles, the extract is often the longest single task.
Count everything on arrival (cases, parties, checklist items, notes, calendar entries, provider records, documents) in a reconciliation sheet you will check the destination against.
Parties, roles, and how they become Filevine contacts
Needles stores the people on a case as Parties, each with a Role: client, defendant, insurance carrier, adjuster, medical provider, lienholder, opposing counsel and so on. It maps well to Filevine, where contacts attach to a project with a role, provided the extract preserves the party-to-case link and duplicates are merged first.
A decade of intake produces the same insurance adjuster entered eleven different ways. Deduplicate before the load, using name plus phone or email as the key, and keep a mapping of the merged identifiers so case links still resolve. Decide which Needles roles map to which Filevine contact types, and which are really project fields (a "Court" party is often better as a court field on the litigation section).
Client records carry extra fields (date of birth, Social Security number if stored, intake source); confirm where those live in Filevine and who can see them.
Checklists become tasks and phases
Needles checklists drive the daily work: items per case type with due dates, done dates and assigned staff. Filevine handles the same job with Phases, task templates tied to phase changes, and deadlines.
For each Needles case type, print the checklist. Group the items into the phases your Filevine Project Type will use (intake, treatment, demand, negotiation, litigation, settlement, closing). Milestones become phase transitions; work items become task templates that fire when the phase begins. Items with statutory significance (statute of limitations, notice deadlines) become Filevine deadlines with their calculation rules, not ordinary tasks.
For open cases, migrate the completed checklist items as history (notes or completed tasks with their done dates) and the open items as live tasks with due dates and assignees. Do not migrate a checklist as a wall of text; it is the only structured record of what has been done.
Medical providers, liens, and the negotiation history
Needles tracks providers per case with treatment dates, billed amounts, records requested and received, and lien status. It tracks the value side too: demand amounts, offers, counteroffers and settlement.
In Filevine this data belongs in collection fields on the Project Type: a Medical Providers collection with one entry per provider holding dates, amounts, records status and lien amount, and a Negotiations collection holding each offer and date. Design those collections before the load so the extract can be shaped to fit. Reconcile them by summing billed amounts and lien amounts per case and comparing to the Needles totals.
Once providers are structured this way, the records request process can be driven from the data rather than from memory, which is the basis for medical records request automation after the migration settles.
Documents living on a network share
Needles typically stores a path to each document rather than the file, with the files themselves on a file server organized by case number or client name. Neos stores documents in the cloud. For Needles, the migration means crawling the share, matching folders to cases by the identifier in the path, and flagging everything that does not match.
Expect orphans: folders named for a client whose case number changed, scanned files dropped at the root, duplicates from years of "copy of copy of." Sort them into matched, probably matched (a human confirms) and unmatched (a holding project). Decide the destination folder scheme per Project Type, map old folder names to it, and keep original filenames and modified dates on upload.
Email is a separate workstream, since Outlook held it rather than Needles. Our page on migrating documents and email to a new case management system covers whether to import historical mail into Filevine or leave it archived. After the load, verify file count and size per case and spot check ten cases per paralegal. Firms that want help designing the Project Types usually start with Filevine consulting.
Questions we get
We still have Needles on an old server nobody maintains. Is that a problem?
It is the main problem, and solvable. Keep the server running until the extract is confirmed complete and reconciled. If nobody at the firm has database access, budget for someone who can obtain it, and get a full backup taken before anyone touches it.
Should we migrate closed cases from Needles?
Bring the last few years as Filevine projects if you need them for referrals, reopenings or reporting. Older closed files can be archived as a spreadsheet index plus the document folders, kept outside Filevine.
Does Neos to Filevine differ from Needles to Filevine?
The extraction is easier from Neos and the data model is close to the same, so the mapping work (parties, checklists, providers, documents) is nearly identical. The timeline is usually shorter.
If you are trying to figure out what your Needles or Neos data will look like in Filevine, tell us what you are working with.