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

Data migration route

Centerbase to Actionstep migration

Centerbase and Actionstep are each a cloud practice management system. Both run a whole practice, so this is a full move, and the financial records set the timetable.

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

What moves

What moves from Centerbase to Actionstep

Each row is a kind of record Centerbase holds, whether Actionstep has a place for it, and what is planned. On this route eleven kinds of record carry across and three kinds need mapping.

Records in Centerbase and their place in Actionstep
RecordIn CenterbaseIn ActionstepWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters sit under clients and inherit client-level billing and accounting settings.Has a placeImported with a matter type, a status and the old number as File Reference.Carried across
ContactsClients, other parties and referrersHeldClients, parties and other contacts, with a saved conflict check history.Has a placeImported first, then linked to matters through a parties import.Carried across
DocumentsFiles stored in or linked from the systemHeldBuilt-in Document Storage, or NetDocuments, iManage or SharePoint connected to matters.Has a placeFiled in matter folders; not part of the spreadsheet import tool.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails and attachments filed to a matter through the Outlook integration.Has a placeSaved emails sit on the matter they were filed to.Carried across
NotesFile notes, matter notes and contact notesHeldHas a placeThe import tool has a file notes template.Carried across
CalendarAppointments, court dates and deadlinesHeldTwo-way sync with Outlook; court rules through LawToolBox.Has a placeAppointments have a place; the standard import templates do not cover them.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks can be created by automated workflows.Has a placeThe import tool has a tasks template.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldIncludes passive time capture from Outlook and Word.Has a placeTime entries and disbursements each have an import template.Carried across
BillingInvoices, payments and debtor balancesHeldElectronic pre-bill approval, multi-payor bills and LEDES formats.Has a place in partUnpaid invoices load as accounts receivable; older invoice history is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldSeveral trust and retainer accounts can be held under one matter or at client level.Has a placeTrust balances load per matter through the trust accounts import.Carried across
Firm accountsGeneral ledger, office account and payablesHeldFull general ledger on a cash or accrual basis, with online banking and payables.Has a placeOpening balances are entered against the general ledger, or the books stay in Xero.Carried across
Custom fieldsFields and record types the firm added itselfHeldUnlimited custom fields and configurable page layouts.Has a placeData collections are built per matter type before values are loaded.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates filled with client and matter data; bill templates.Has a placeRebuilt as Actionstep templates with its merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldWeb form enquiries arrive as Potential New Client records.Has a placeCarried across

What the plans mean

Carried across
Actionstep has a place for this kind of record. It is loaded there and checked against Centerbase.
Carried with mapping
Actionstep holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.

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 whole practice moves, accounts included.

A move between two practice management systems is the widest kind there is. Centerbase and Actionstep each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.

The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with Centerbase’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Centerbase 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 Centerbase is kept running until the checks on Actionstep are finished.

Where the data is now

No two Centerbase sites look alike, because the product is configured around each firm. A firm leaving it is moving its own design as much as its data: the fields it added, the workflows it automated, the way bills are approved. The analysis begins by documenting that configuration, since the meaning of many records depends on it, and then deals with the general ledger and trust accounts.

  1. Each site is configured

    Custom fields are unlimited and page layouts are designed per firm, so the same information may be stored in quite different places from one Centerbase site to the next. A field list is extracted with usage counts. Fields that were added and abandoned are common in a long-lived site, and the firm decides which are worth carrying.

  2. Settings inherited from clients

    Billing arrangements, rate tables and accounting preferences are set on the client and applied to its matters. A destination that holds these on the matter needs them copied down to every matter, and one that has no rate tables needs rates entered another way. Either route is tested on a client with unusual terms.

  3. Several trusts per matter

    One matter can have more than one trust or retainer account, and funds can also be tracked at client level. Many systems allow a single trust ledger per matter. Where that is so, the firm decides how the separate balances are shown, and each one is still reconciled to its Centerbase figure before cutover.

  4. Pre-bills in the approval chain

    Pre-bills move electronically through reviewers, collecting mark-ups as they go. A pre-bill caught mid-approval at cutover has edits that live nowhere else. It is simplest to finish the billing cycle before the freeze, so that what moves is either unbilled time or a finished invoice.

  5. Where documents really are

    Documents may be in Centerbase’s own Document Storage, or in NetDocuments, iManage or SharePoint with Centerbase supplying the matter link. Only the first set has to be extracted. For the others the files stay put and the work is re-attaching each workspace to its matter in the new system.

More about moving off Centerbase

Where it is going

Actionstep has its own import tool, which takes spreadsheets in a set order: contacts, then matters, then the parties that join them. Tasks, time entries, trust balances, disbursements, unpaid invoices and file notes follow once the matters exist. None of it can start until the matter types, participant types and data collections have been built, because every imported row refers to them.

  1. Matter types before any data

    A matter’s type decides its workflow steps, its document folders, which party roles are available and which custom data it carries. So the first job is deciding how the old system’s matter types map to Actionstep’s, and building any that are missing. An imported matter also needs a step to sit at, usually the one closest to its old status.

  2. Old numbers go to File Reference

    Actionstep assigns its own Matter ID to each imported matter. The number the firm has always used goes into the File Reference field, which the quick search reads from the start of the reference. Staff can keep finding matters by the number printed on old letters and file covers.

  3. Check before anyone edits

    The import tool can roll back a load, but only while the imported records are untouched. Once someone edits them, the rollback no longer works. Trial loads are therefore checked straight away against the old system, and nobody outside the project works in the new records until the counts and balances agree.

  4. Folders come from the matter type

    Default document folders are set per matter type. There is no single folder list that applies across all matters. Before documents are loaded, the old folder names are mapped to the folders each matter type will have, so a conveyancing file and a litigation file each open with the layout the firm designed for them.

  5. Opening balances can be locked

    Trust balances load against matters, unpaid invoices load as accounts receivable, and general ledger opening balances are entered on the accounts list. An opening balance that has been locked cannot be edited afterwards. The figures are rehearsed on a trial load and agreed with the firm’s accountant before the lock is applied in the live system.

More about moving into Actionstep

How NewLaw runs it

Four steps, in this order.

Trust money moves on this route, so the trust cutover gets a rehearsal of its own.

  1. Analysis

    We read what Centerbase holds and how its records link, then agree with you, field by field, where each piece will sit in Actionstep. 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 Centerbase, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

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

  4. Cutover

    Changes in Centerbase are frozen for an agreed window, the data is collected a final time and Actionstep goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. Centerbase 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 Centerbase 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 fromCenterbase
Moving toActionstep

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

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

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

Most of the work in an Actionstep set-up is design. The firm decides what its matter types are, what steps each one moves through and what happens at each step. Templates, billing and trust settings are then built around those matter types. People are trained on their own workflows, since a generic demonstration looks little like the firm’s finished system.

Set-up decisions in Actionstep

  • Matter types, with workflow steps and default document folders
  • Participant types and data collections for each matter type
  • Document and email templates rebuilt with Actionstep merge fields
  • Trust accounts, chart of accounts and the optional Xero link
  • System roles and data permissions for each group of staff
  • Outlook add-in, divisions and the firm’s billing preferences

Questions

Centerbase to Actionstep: what firms ask

We keep our accounts in Centerbase. Do we have to change accounting systems as well?

Only if the destination does not have a general ledger. Centerbase holds the firm’s books and its trust records together, so the two leave together. Where the new system is practice management only, an accounting package is chosen and opened first, and opening balances are taken at a closed period end.

Can our financial history be loaded into Centerbase, or just balances?

The vendor describes moving practice management, billing, trust and accounting data, with a test migration validated before go-live. How many years of transactions are worth loading is a separate question. It is settled in the analysis by looking at what the source can supply cleanly and what the firm really reports on.

Our documents are in iManage. Does anything change for them?

The documents do not move. Centerbase connects to iManage and to NetDocuments, so the files stay in the document system the firm already uses. The work is matching each workspace to the right client and matter number, which is why matter numbering is fixed before the trial load.

Do trust balances in Centerbase have a place in Actionstep?

Yes. Actionstep keeps trust ledgers. Trust balances load per matter through the trust accounts import. Balances are loaded by matter and agreed to the trust report from Centerbase as at the cutover date. That load cannot be re-run the way a document load can, so it is rehearsed on a full trial load first.

Does everything in Centerbase have a place in Actionstep?

On paper, yes: each kind of record Centerbase holds has a place in Actionstep. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.

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

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

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

Moving from Centerbase to Actionstep?

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

We reply within one business day.