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

Data migration route

Needles to Centerbase migration

Needles is a server-based case management system for personal injury work, and Centerbase is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in Centerbase, often from a separate accounts package.

FromNeedlesServer
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Notes: Carried across
  5. Calendar: Carried across
  6. Tasks: Carried across
  7. Intake: Carried across
  8. Custom fields: Carried with mapping
  9. Templates: Carried with mapping
  10. Emails: Confirmed in the analysis
  11. Time and expenses: Confirmed in the analysis
  12. Billing: Confirmed in the analysis
  13. Trust money: Confirmed in the analysis
  14. Firm accounts: Confirmed in the analysis
ToCenterbaseCloud
  • 7 carried
  • 2 mapped
  • 5 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Needles to Centerbase

Each row is a kind of record Needles holds, whether Centerbase has a place for it, and what is planned. On this route seven kinds of record carry across, two kinds need mapping and five kinds are confirmed in the analysis.

Records in Needles and their place in Centerbase
RecordIn NeedlesIn CenterbaseWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases with parties, insurance, counsel, value items and a checklist.Has a placeLoaded under their client, with practice-specific custom fields.Carried across
ContactsClients, other parties and referrersHeldNames used across cases as parties, providers, insurers and counsel.Has a placeClients, related parties and prospects.Carried across
DocumentsFiles stored in or linked from the systemHeldFiles in a document folder on the firm’s server, linked to the case.Has a placeInto Document Storage, or left in a connected NetDocuments, iManage or SharePoint store.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partEmails saved to matters; mailboxes stay in Microsoft 365.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeldCase notes.Has a placeCarried across
CalendarAppointments, court dates and deadlinesHeldCase calendar and statute tracking.Has a placeCarried across
TasksTo-dos and workflow steps assigned to peopleHeldChecklist items per case.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledTo be confirmedHas a placeConfirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedHas a placeThe vendor says billing history can be migrated; the depth is set in the analysis.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a placeMultiple trust and retainer accounts per matter or client.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedHas a placeGeneral ledger with chart of accounts; opening trial balance agreed with the accountant.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldUser-defined tabs and fields added by the firm.Has a placeCreated and placed on page layouts before records are loaded.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates merged from case data.Has a place in partTemplates are rebuilt to merge Centerbase client and matter data.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntake is part of the product.Has a placeEnquiries are held as Potential New Client records; loading open ones is confirmed in the analysis.Carried across

What the plans mean

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

Cases come across. The accounts are set up new.

A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to Centerbase brings those two sources together. The case records come from Needles. Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.

Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in Centerbase, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.

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

Centerbase takes practice, billing, trust and accounting data together, so loading a firm into it is a finance project as much as a matter load. Clients come first because matters inherit from them. The chart of accounts, bank accounts and accounting basis are fixed before balances go in. Because the product is configured per firm, the fields and layouts are designed before the trial load, not after.

  1. Clients carry the billing rules

    Billing arrangements, rates and accounting preferences are held on the client and passed to its matters. Source systems that create a fresh client for every matter leave duplicates behind. Those are merged during clean-up, so that each real client exists once and its terms are set in one place.

  2. The ledger comes too

    Centerbase has a full general ledger and runs on a cash or accrual basis. A firm arriving from a billing system with QuickBooks beside it is consolidating two sets of records. The accountant decides the basis and the opening date, and the trial balance loaded is agreed to the old books.

  3. Trust and retainers are separate

    A matter can hold multiple trust and retainer accounts. Source systems often blur the two, recording an advance on fees as trust or the reverse. Each balance is classified before loading, and client-level funds that were never tied to a matter are assigned to one or held at client level.

  4. Decide the document home

    Documents can go into built-in Document Storage, or stay in NetDocuments, iManage or SharePoint and be connected. Centerbase can create a standard folder structure when a matter is opened. That structure is agreed first, so migrated documents are filed into the same folders that new matters will get.

  5. Fields are designed, not assumed

    With unlimited custom fields, nearly every source field can have a home. That is a reason for restraint. Each one must be created and placed on a layout, and a page crowded with unused fields slows people down. The firm chooses which fields earn a place and which become a note.

More about moving into Centerbase

How NewLaw runs it

Four steps, in this order.

No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Centerbase, they get a rehearsed cutover of their own.

  1. Analysis

    We read what Needles holds and how it is organised, then agree with you where each kind of record will sit in Centerbase. 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 Centerbase 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

    After a short freeze on changes in Needles, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. 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 toCenterbase

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

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

Setting up Centerbase is largely configuration. Bill templates, rate tables and the pre-bill approval chain have to match how the firm bills today, or the first billing cycle exposes the gaps. The chart of accounts and bank accounts are built with the finance team. Workflows that open matters, create folders and assign first tasks are written last, once the fields they depend on are settled.

Set-up decisions in Centerbase

  • Bill templates and billing arrangements for each client type
  • Rate tables, timekeepers and the pre-bill approval chain
  • Chart of accounts, bank accounts and cash or accrual basis
  • Custom fields, page layouts and automated workflows by practice
  • Document storage choice and the standard matter folder structure
  • Outlook and Microsoft 365 connection for email and calendar

Questions

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

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 Centerbase turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

Does everything in Needles have a place in Centerbase?

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 Centerbase is kept as a readable archive, and you see which before the move.

What has to be decided before Needles data is loaded into Centerbase?

Custom fields 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.

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 Centerbase are the names and marks of their owners, used here only to identify the two systems.

Moving from Needles to Centerbase?

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

We reply within one business day.