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

Data migration route

SmartAdvocate to Centerbase migration

SmartAdvocate is a cloud 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.

FromSmartAdvocateCloud
  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. Time and expenses: Carried across
  8. Billing: Carried across
  9. Intake: Carried across
  10. Emails: Carried with mapping
  11. Custom fields: Carried with mapping
  12. Templates: Carried with mapping
  13. Trust money: Confirmed in the analysis
  14. Firm accounts: Confirmed in the analysis
ToCenterbaseCloud
  • 9 carried
  • 3 mapped
  • 2 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from SmartAdvocate to Centerbase

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

Records in SmartAdvocate and their place in Centerbase
RecordIn SmartAdvocateIn CenterbaseWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCases, with master and member cases for mass tort and class action work.Has a placeLoaded under their client, with practice-specific custom fields.Carried across
ContactsClients, other parties and referrersHeldHas a placeClients, related parties and prospects.Carried across
DocumentsFiles stored in or linked from the systemHeldDocuments page with categories, subcategories and custom folder views.Has a placeInto Document Storage, or left in a connected NetDocuments, iManage or SharePoint store.Carried across
EmailsEmails saved to matters or to the storeHeldThe Outlook plugin attaches emails and their attachments to cases.Has a place in partEmails saved to matters; mailboxes stay in Microsoft 365.Carried with mapping
NotesFile notes, matter notes and contact notesHeldCase notes.Has a placeCarried across
CalendarAppointments, court dates and deadlinesHeldA Case Calendar and an Office Calendar. Critical deadlines sync to Outlook.Has a placeCarried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks created by WorkPlans and Automated Procedures.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldTime tracking, including from the mobile apps.Has a placeCarried across
BillingInvoices, payments and debtor balancesHeld in partBuilt-in invoicing for hourly matters, from expenses and time entries.Has a placeThe vendor says billing history can be migrated; the depth is set in the analysis.Carried across
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 itselfHeldDescribed as fully customisable, with custom merge codes and plaintiff fact sheets.Has a placeCreated and placed on page layouts before records are loaded.Carried with mapping
TemplatesPrecedents, document templates and automationHeldWord, Excel and PDF templates filled from thousands of merge codes.Has a place in partTemplates are rebuilt to merge Centerbase client and matter data.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldBuilt-in intake and lead management.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 SmartAdvocate.
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 SmartAdvocate. 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.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of SmartAdvocate depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to SmartAdvocate is kept running until the checks on Centerbase are finished.

Where the data is now

SmartAdvocate holds a great deal of structured detail on each case, and leaving it is mostly a question of what the destination can receive. The edition matters for the mechanics. A Server firm has the database and document store on its own equipment. A Cloud firm arranges a copy through its hosted service. The content is the same either way.

  1. Server or Cloud edition

    With the Server edition the firm owns the installation, so a backup of the database and of the document and image storage can be taken on site. On the Cloud edition the vendor hosts both. Which edition the firm has is the first thing established, since it decides how the copy for the trial load is obtained.

  2. Master and member cases

    Mass tort and class action work is held as a master case with member cases related to it, and plaintiff fact sheets record the criteria for each litigation. Member cases are loaded as individual matters. The relationship and the fact sheet answers need an agreed home, or the firm loses the ability to report across a litigation.

  3. WorkPlans in progress

    A WorkPlan is a checklist that also automates steps, and Automated Procedures send reminders, texts, emails and generated documents. On an open case some items are done and some are pending. Pending items are loaded as tasks with due dates. The automation is rebuilt in the destination’s workflow tool from the WorkPlan definitions.

  4. Merge codes in templates

    Templates are Word, Excel or PDF files containing merge codes, including table codes that pull in lists of providers, bills, liens and expenses. The codes mean nothing outside SmartAdvocate. Template wording is kept and coded again for the new system, and list-style merges are tested early because not every system can produce them.

  5. Emails filed through Outlook

    The Outlook plugin files emails to the case and saves attachments to the documents page. Email is therefore part of the case record, and usually a large part. It is extracted with sender, recipients and date, and attachments already saved as documents are not loaded a second time.

More about moving off SmartAdvocate

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.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  1. Analysis

    We read what SmartAdvocate holds and how its records link, then agree with you, field by field, where each piece will sit in Centerbase. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in SmartAdvocate, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Centerbase as a trial and checked against SmartAdvocate: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in SmartAdvocate are frozen for an agreed window, the data is collected a final time and Centerbase goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in SmartAdvocate as at the cutover date. SmartAdvocate 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 SmartAdvocate 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 fromSmartAdvocate
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 SmartAdvocate 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

SmartAdvocate to Centerbase: what firms ask

Is SmartAdvocate cloud or on-premise?

Both exist. The Cloud edition is hosted by the vendor, and the Server edition is installed on the firm’s own server and maintained by the firm’s IT. Either way staff use it in a browser, and there are phone and tablet apps. A firm can tell which it has by who takes the backups.

Can our WorkPlans be migrated?

Yes for the open items, which load as tasks. The WorkPlan itself is SmartAdvocate automation and has to be recreated in the destination’s own workflow tool. Its definitions are documented step by step for that purpose, and the firm is asked which plans are still followed, because some will not have been touched in years.

We are moving to SmartAdvocate. What should we clean first?

Contacts and statuses. Duplicate providers and insurers multiply once they are attached to cases, and vague statuses cannot be translated to case stages. Merging the obvious duplicates and closing cases that are really finished, in the old system before extraction, costs far less than correcting them after the load.

Do trust balances in SmartAdvocate 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 SmartAdvocate 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 SmartAdvocate have a place in Centerbase?

Most of it does on paper. 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 SmartAdvocate data is loaded into Centerbase?

Emails, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Trust ledgers and the firm’s accounts are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.

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

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

Moving from SmartAdvocate 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.