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

Data migration route

Needles to NetDocuments migration

Needles is a server-based case management system for personal injury work, and NetDocuments is a cloud document management system. Documents and email move, filed under the matters they came from. Time, billing and trust have no place in a document system.

FromNeedlesServer
  1. Documents: Carried across
  2. Matters: Carried with mapping
  3. Custom fields: Carried with mapping
  4. Templates: Carried with mapping
  5. Emails: Confirmed in the analysis
  6. Tasks: Confirmed in the analysis
  7. Time and expenses: Confirmed in the analysis
  8. Billing: Confirmed in the analysis
  9. Trust money: Confirmed in the analysis
  10. Firm accounts: Confirmed in the analysis
ToNetDocumentsCloud
  1. Contacts: Kept as a readable archive
  2. Notes: Kept as a readable archive
  3. Calendar: Kept as a readable archive
  4. Intake: Kept as a readable archive
Readable archiveNo place in NetDocuments
  • 1 carried
  • 3 mapped
  • 6 to confirm
  • 4 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Needles to NetDocuments

Each row is a kind of record Needles holds, whether NetDocuments has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping, four kinds have no place in NetDocuments and are archived and six kinds are confirmed in the analysis.

Records in Needles and their place in NetDocuments
RecordIn NeedlesIn NetDocumentsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases with parties, insurance, counsel, value items and a checklist.Has a place in partAs a client and matter value with its workspace. Other matter details stay in practice management.Carried with mapping
ContactsClients, other parties and referrersHeldNames used across cases as parties, providers, insurers and counsel.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldFiles in a document folder on the firm’s server, linked to the case.Has a placeImported with profile values, folder, dates and access set per document.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeLoaded as email items profiled to the matter.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeldCase notes.No placeFile notes are loaded as documents in the matter workspace.Kept as a readable archive
CalendarAppointments, court dates and deadlinesHeldCase calendar and statute tracking.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeldChecklist items per case.To be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledTo be confirmedNo placeConfirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedNo placeConfirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedNo placeConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldUser-defined tabs and fields added by the firm.Has a placeAs custom profile attributes, created in the repository before the load.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates merged from case data.Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntake is part of the product.No placeKept as a readable archive

What the plans mean

Carried across
NetDocuments has a place for this kind of record. It is loaded there and checked against Needles.
Carried with mapping
NetDocuments 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
NetDocuments 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

The documents move. The accounts do not.

Moving from a matter system into a document management system is a documents job. NetDocuments has no place for time, invoices or trust, so there is no financial cutover on this route. What it does want is structure. Every document from Needles is filed into a workspace or folder for its client and matter, with a profile that says what it is. The client and matter list becomes that structure, which is why it is cleaned before any file is copied.

A document’s own details count for more here than anywhere. Created and modified dates, author, document type and version become searchable profile fields, and a wrong date on a few thousand files is hard to undo. Email filed to matters is carried as messages. Document copies can be run again, so the trial is repeated until counts and dates agree. Matter data that NetDocuments cannot hold goes to whatever replaces Needles for matters and billing, or into an archive.

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

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.

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

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

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

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

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

More about moving off Needles

Where it is going

Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.

  1. Lookup tables before documents

    Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.

  2. Workspaces come from the profile

    A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.

  3. Import files are unforgiving

    The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.

  4. Folder limits and depth

    A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.

  5. Security at the right level

    Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.

More about moving into NetDocuments

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in NetDocuments on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Needles holds and how it is organised, then agree with you where each kind of record will sit in NetDocuments. Anything with no place there stays behind or is archived, and you see which before the move.

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

  3. Trial load

    A trial is loaded into NetDocuments 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.

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

Step 1 of 5: Start with the route

Moving fromNeedles
Moving toNetDocuments

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 Needles holds

    What is in it, how its records link, and where each piece would sit in NetDocuments. 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 NetDocuments

Loaded data is not yet a working system. This is what NewLaw sets up in NetDocuments, beyond the migration, so that people can work in it from the first day.

Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.

Set-up decisions in NetDocuments

  • Cabinet design: one for the firm, or several by purpose
  • Profile attributes, lookup tables and the client and matter hierarchy
  • Workspace layout with default folders, filters and saved searches
  • User groups, cabinet membership and security for restricted matters
  • A feed of new clients and matters from practice management
  • ndOffice, ndMail and Outlook filing on every desk, with training

Questions

Needles to NetDocuments: 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 NetDocuments?

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 NetDocuments 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 NetDocuments has no place for?

On this route that is contacts, notes, calendar entries 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 NetDocuments?

Matters, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails, tasks, 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.

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

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

Moving from Needles to NetDocuments?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.