Data migration route
Needles to Server drives migration
Needles is a server-based case management system for personal injury work, and Server drives are plain files on equipment the firm controls. Documents move into a folder for each client and matter, and the data behind them is kept as an export.
NeedlesServer- Documents: Carried across
- Notes: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Time and expenses: Confirmed in the analysis
- Billing: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
Server drivesFiles- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Tasks: Kept as a readable archive
- Custom fields: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 2 mapped
- 5 to confirm
- 6 archived
What moves
What moves from Needles to Server drives
Each row is a kind of record Needles holds, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping, six kinds have no place in Server drives and are archived and five kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCases with parties, insurance, counsel, value items and a checklist. | No placeA matter becomes a folder; its details survive only in an index file. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldNames used across cases as parties, providers, insurers and counsel. | No placeCan be kept only as an exported spreadsheet. | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldFiles in a document folder on the firm’s server, linked to the case. | Has a placeFiles in folders, named and dated during the load. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partAs .msg or .eml files in each matter’s correspondence folder. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | HeldCase notes. | Has a place in partAs a text or PDF file per matter, not as separate records. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | HeldCase calendar and statute tracking. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | HeldChecklist items per case. | No place | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | No placeOnly as exported reports or spreadsheets. | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | To be confirmed | Has a place in partInvoices as PDF files; no ledger. | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | No placeOnly as exported ledger reports kept as files. | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | No place | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldUser-defined tabs and fields added by the firm. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | HeldDocument templates merged from case data. | Has a place in partPrecedents as Word files; merge fields tied to the old system stop working. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntake is part of the product. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- Server drives has a place for this kind of record. It is loaded there and checked against Needles.
- Carried with mapping
- Server drives 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.
- Kept as a readable archive
- Server drives has no place for it. It is exported in a format that opens without Needles and handed to the firm as a read-only archive.
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
Out of the system, into folders the firm can read.
File storage has folders and files and nothing else. Moving from Needles into Server drives means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters Server drives do not allow in a name.
Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in Needles.
Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Needles stays untouched until the copy in Server drives has been checked.
Where the data is now
Leaving Needles
Needles data sits on the firm’s own server, in a database and a folder of documents beside it. Leaving it means taking a copy of both and reading them together. The standard case layout comes with the product. What varies is the user-defined tabs each firm added and how carefully documents were linked.
A database and a folder
Case records are in a SAP ASE database, the product once called Sybase, and the documents are ordinary files on the server that the database points to. Both are copied at the same moment. A database from Friday and a document folder from Monday will not agree, and the mismatch shows up as broken links.
Value items
Medical bills, liens, costs, settlement amounts and payments are entered as value items on the case, each with a code. This is where the money on an injury file is recorded. Value items are extracted by code and mapped to bills, liens, expenses or settlement records in the destination, with totals compared per case.
Checklists drive the work
Each case has a checklist that sets out items for staff as the case progresses. Completed items are history. Open items are the work in hand, and they are loaded as tasks with their due dates and owners. The checklist design is written up so it can be rebuilt as a workflow.
User-defined tabs
Firms add their own tabs and fields for whatever the standard screens lack, such as intake questions, vehicle details or mass tort criteria. Some hold data on every case and some were abandoned years ago. Each tab is profiled for how many cases use it before a decision is made to map it, note it or drop it.
One list of names
Clients, defendants, doctors, hospitals, insurers and lawyers are drawn from a shared list of names and attached to cases in different capacities. Decades of entry produce duplicates. Providers and insurers are merged where they can be identified, because the same hospital spelt four ways becomes four contacts in the new system.
Where it is going
Arriving in Server drives
Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.
Agree the tree and the names
A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.
Budget the path length
Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.
Dates have to be set deliberately
A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.
Emails become message files
Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.
Keep an index beside the files
A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Server drives on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Needles holds and how it is organised, then agree with you where each kind of record will sit in Server drives. 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 Server drives and checked against Needles: 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 Needles, a final pass over a weekend picks up what changed since the trial. Needles 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 Needles 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 Needles holds
What is in it, how its records link, and where each piece would sit in Server drives. 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
Structure, permissions and handover
Server drives are storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.
A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.
What is agreed and set up
- Share and top-level folders for clients, precedents and administration
- Security groups and folder permissions, with restricted matters separate
- Drive letter mapped for every user at sign-in
- Backup schedule and shadow copies for earlier versions
- Written naming rule for client, matter and document names
- Read-only area for closed matters and archived system exports
Questions
Needles to Server drives: what firms ask
Is Needles being discontinued?
Assembly Software has said publicly that it is not: Needles is supported and there is no sunset date. It also describes Needles as the predecessor of Neos, its cloud product, and says major new feature development is focused there. The timing of a move is therefore the firm’s own choice.
Do we have to go to Neos, or can Needles data go elsewhere?
It can go to any system that can hold an injury case. Assembly says Neos keeps the same case logic, so that mapping is the most direct. Another destination needs a place for value items, insurance, counsel and checklists, and each is confirmed in the analysis before the firm commits.
Our documents are on the server. Will the links survive?
The files move and are attached to the right case using the links held in the database. Links break where files were renamed or moved in Windows outside the program. Those orphans are found during the trial load by comparing the database’s list with the folder, and the firm is given the list.
Do trust balances in Needles have a place in Server drives?
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 Needles before the plan is fixed. If Server drives turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
What happens to records Server drives have no place for?
On this route that is matters, contacts, calendar entries, tasks, custom fields and intake records. They are exported from Needles in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.
What has to be decided before Needles data is loaded into Server drives?
Notes and templates are carried with mapping, so each mapping is agreed with you first. Emails, time entries, billing records, trust ledgers and the firm’s accounts 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 Needles and into Server drives
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.
Needles and Server drives are the names and marks of their owners, used here only to identify the two systems.
Moving from Needles to Server drives?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.