Data migration route
Needles to Sync.com migration
Needles is a server-based case management system for personal injury work, and Sync.com is cloud file storage. 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
Sync.comCloud- 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 Sync.com
Each row is a kind of record Needles holds, whether Sync.com has 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 Sync.com 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 is a folder in Files or Vault. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldNames used across cases as parties, providers, insurers and counsel. | No place | 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 and folders within the path limit; some file types are skipped by the apps. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partMessage files such as .msg or .eml, filed in the matter’s folder. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | HeldCase notes. | Has a place in partOnly as a document written out to the matter’s folder. | 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 place | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | To be confirmed | No place | Confirmed in the analysis |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | No place | 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 load as ordinary files. | 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
- Sync.com has a place for this kind of record. It is loaded there and checked against Needles.
- Carried with mapping
- Sync.com 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
- Sync.com 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 Sync.com 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 Sync.com does 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.
Needles runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Sync.com is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
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 Sync.com
A firm that moves its files to Sync is usually doing so for confidentiality, and the load has to respect how the service is built to deliver it. Files are encrypted before they leave the computer. Nobody at Sync can look inside the account to confirm what arrived, so the checking is done from the firm’s side, against the list of what was sent.
Files or Vault
Open matters belong in Files, where they sync to the people working on them. Closed matters can go to Vault, which holds them in the cloud without putting a copy on every laptop. The firm supplies its open and closed matter lists so each folder is sent to the right side.
A 248 character path limit
Sync sets a maximum path length of 248 characters to stay compatible between Windows and Mac, and its apps skip anything longer. That is tighter than most systems a firm will be coming from. Folder names are shortened in the plan, and Sync’s own guidance favours a tree only a few levels deep.
What the apps leave out
The desktop apps do not upload shortcut files, temporary Office files or names containing a slash, and they warn against several other characters on Windows. A copy to Vault produces a transfer report listing what was skipped. That report is reconciled against the source file list after every load.
Permissions come from the top folder
Sharing is set on a folder and flows down to all of its contents. A matter that needs different access from the rest of a client’s work cannot simply sit one level down with tighter settings. It becomes its own shared folder, and those exceptions are identified before the tree is built.
Shared folders count against storage
A shared folder is added to each member’s account and normally counts towards their quota, and it syncs to their computer as a real folder. Sharing the whole client tree with every person can fill both. Shares are sized to teams, and the allowance needed per user is worked out from the document volumes.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Sync.com 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 Sync.com. 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 Sync.com 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 Sync.com. 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
Sync.com is 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 Sync set-up comes down to accounts and shares. A team plan gives an administrator control over users, two-factor authentication and password resets, which matters more than usual in a service the provider says it cannot see into. The shared folders are then created to match the firm’s teams and its restricted matters.
What is agreed and set up
- Administrator account and a user for each staff member
- Two-factor authentication enforced across the firm
- Team shared folders with view or edit permission per person
- Which matters live in Files and which in Vault
- Rules for client links: passwords, expiry dates, upload rights
- Desktop app installed, with a filing guide for new matters
Questions
Needles to Sync.com: 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 Sync.com?
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 Sync.com 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 Sync.com has 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 Sync.com?
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 Sync.com
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 Sync.com are the names and marks of their owners, used here only to identify the two systems.
Moving from Needles to Sync.com?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.