Data migration route
Needles data to Full data export
Needles is a server-based case management system for personal injury work, and Full data export is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what Needles holds and keeps it readable and open to queries.
NeedlesServer- Matters: Exported in full
- Contacts: Exported in full
- Documents: Exported in full
- Notes: Exported in full
- Calendar: Exported in full
- Tasks: Exported in full
- Custom fields: Exported with mapping
- Templates: Exported with mapping
- Intake: Exported 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
Full data exportFiles- 6 carried
- 3 mapped
- 5 to confirm
What moves
What moves from Needles to Full data export
Each row is a kind of record Needles holds, whether Full data export has a place for it, and what is planned. On this route six kinds of record carry across, three kinds need mapping 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. | Has a placeA matters table keyed by the original matter number. | Exported in full |
| ContactsClients, other parties and referrers | HeldNames used across cases as parties, providers, insurers and counsel. | Has a placeA contacts table and a table of each contact’s role on each matter. | Exported in full |
| 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 under their original names, in client and matter folders. | Exported in full |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partFiled emails as message files in the matter’s folder, if the source exposes them. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | HeldCase notes. | Has a placeA notes table with matter, author and date for each note. | Exported in full |
| CalendarAppointments, court dates and deadlines | HeldCase calendar and statute tracking. | Has a placeA table of appointments and key dates; nothing shows it as a diary. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | HeldChecklist items per case. | Has a placeA table of tasks with assignee, due date and status. | Exported in full |
| Time and expensesTime and expense entries, billed and unbilled | To be confirmed | Has a placeA time entries table with fee earner, matter, units, rate and billed status. | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | To be confirmed | Has a placeInvoice, line and receipt tables; invoice PDFs can be kept beside them. | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a placeA trust transactions table; ledger reports can be kept as PDF beside it. | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | To be confirmed | Has a place in partJournals and account balances, where the source held a general ledger. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldUser-defined tabs and fields added by the firm. | Has a placeExtra columns under their original field names. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument templates merged from case data. | Has a place in partTemplate files only; the merge fields in them will not run. | Exported with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntake is part of the product. | Has a place in partAn enquiries table, where the source tracked leads. | Exported with mapping |
What the plans mean
- Exported in full
- Full data export has a place for this kind of record. It is loaded there and checked against Needles.
- Exported with mapping
- Full data export 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
Not a new system. A complete copy the firm can query.
Writing Needles out to Full data export is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.
What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Needles as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.
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 Full data export 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 Full data export
A full export is judged by whether a stranger can use it. In five years the question will be something like: what was the trust balance on this matter the day it closed, and where is the signed agreement. The export is planned backwards from questions of that kind, and it is checked against the live system while the live system can still be opened.
Tables that still join up
Each kind of record becomes its own table: matters, contacts, time entries, invoices, trust transactions. The identifiers that link them are kept in every table, so a time entry can still be traced to its matter and its fee earner. An export that keeps the rows and drops the keys cannot be rejoined later.
Documents with an index
Documents are written to folders by client and matter under their original names. On their own they can be found only by name. An index listing each file with its matter number, title, author, dates and path is what lets someone find the right version of a lease among forty thousand files without the old system’s search. What the index records is settled in the analysis.
Reports a person can read
Raw tables do not satisfy an auditor or a former client. The firm decides which reports are also printed to PDF from the old system as at the final date: trust ledgers, matter ledgers, debtor lists and issued invoices are the usual candidates. They cannot be regenerated once the licence ends.
What an export does not keep
Screens, workflows, document automation, saved searches and user permissions belong to the software and stay with it. Figures the system calculated on the fly, such as a matter’s unbilled total, exist in an export only if they were captured as a report. The firm is told which of these are being let go.
Checked while the source is open
Record counts and financial totals in the export are reconciled to the live system: number of matters, sum of trust balances, total debtors, document count per matter on a sample. This is done before the subscription lapses or the server is turned off, because afterwards there is nothing left to compare against.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what Needles holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything Needles holds is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to Full data export as a trial and checked against Needles: record counts, totals where Needles holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in Needles, the export is run a final time and checked again. There is nothing to go live. Needles is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
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 Full data export. 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
Full data export is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
With no product to configure, the set-up is custody, and the decisions are the firm’s. Someone there owns the export, knows where it is kept and can open it. Access needs restricting, because it contains every client’s affairs in one place with none of the old system’s security. The firm sets a destruction date from its retention obligations and decides how the next custodian will learn to use it.
What is agreed and set up
- Folder layout for tables, documents and reports
- What the key to tables, columns and identifiers records
- Where the copies are stored and who is custodian
- Who may open it, as approved by a partner
- Which look-ups staff must be able to do unaided
- Retention period and the date it is next reviewed
Questions
Needles to Full data export: 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.
Does the copy in Full data export hold trust ledgers from Needles?
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.
Does everything in Needles have a place in Full data export?
Most of it does on paper. Emails, time entries, billing records, trust ledgers and the firm’s accounts 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 Full data export is kept as a readable archive, and you see which before the move.
What has to be decided before Needles is written out to Full data export?
Custom fields, templates and intake records are exported 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 who may open the archive and how long it is kept.
Other routes
Other routes from Needles and into Full data export
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 Full data export are the names and marks of their owners, used here only to identify the two systems.
Moving from Needles to Full data export?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.