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

Data migration route

Alfresco to Centerbase migration

Alfresco is a document management system, and Centerbase is a cloud practice management system. Documents and email move out of a store organised by profile and onto the matters they belong to.

FromAlfrescoDocument management
  1. Documents: Carried across
  2. Custom fields: Carried with mapping
  3. Emails: Confirmed in the analysis
  4. Notes: Confirmed in the analysis
  5. Calendar: Confirmed in the analysis
  6. Tasks: Confirmed in the analysis
  7. Templates: Confirmed in the analysis
ToCenterbaseCloud
  • 1 carried
  • 1 mapped
  • 5 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Alfresco to Centerbase

Each row is a kind of record Alfresco holds, whether Centerbase has a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping and five kinds are confirmed in the analysis.

Records in Alfresco and their place in Centerbase
RecordIn AlfrescoIn CenterbaseWhat is planned
DocumentsFiles stored in or linked from the systemHeldFiles in repository folders and site document libraries, with typed properties.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 confirmedDepends on the modules and integrations installed.Has a place in partEmails saved to matters; mailboxes stay in Microsoft 365.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedWorkflow tasks exist where the process services are in use.Has a placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom types, aspects and properties defined in a content model.Has a placeCreated and placed on page layouts before records are loaded.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt to merge Centerbase client and matter data.Confirmed in the analysis

What the plans mean

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

Profiled documents become matter documents.

A document management system files by profile: client, matter, author, document type, version. A practice management system files by matter. The move from Alfresco to Centerbase is a translation from one to the other, and it depends on the client and matter numbers in Alfresco matching matters that exist in Centerbase. Where they do not match, documents have nowhere to land. So the matter list is settled first and the documents follow it.

Versions and security each need a decision. Some practice systems keep every version of a document, others keep the latest and treat the rest as separate files. A restricted workspace has to become a restricted matter, or the restriction is lost on the way. Filed email comes across as message files against the matter. A document store holds no ledgers, so this route has no financial cutover.

How Alfresco is run at the firm is settled at the start of the analysis, because its maker’s own material does not settle it. The usual arrangement is assumed here. Alfresco 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

No two Alfresco installations are alike, because the content model is written for each customer. A move off it begins by reading that model: which custom types and aspects exist, what properties they carry, and how the firm used sites and folders to stand for clients and matters. Only then can anyone say which properties are matter numbers and which are noise.

  1. Read the content model

    Document types, their properties and the aspects applied to them are defined in content models specific to the installation. A property might be called matterRef at one firm and caseNo at another. The model files and a sample of live documents are examined together to build the field list the mapping works from.

  2. Versioning is not always on

    Alfresco’s documentation notes that content created in the repository is not versioned by default: history is kept once versioning has been applied to the item. So some documents will have a full history and others a single state. The extraction records which is which instead of assuming every file has versions.

  3. Sites, libraries and plain folders

    Content can sit in a site’s document library or in ordinary repository folders outside any site. Firms often have both: sites created per client or project, and an older folder tree brought in from a file server. Each is walked separately, and an item filed in more than one place is counted once.

  4. Customisations hold business rules

    Folder rules, scripts and workflows are commonly added to file documents automatically, stamp metadata or route approvals. They are configuration, not data, and they do not move. The analysis lists the ones that still run, so the firm can decide which behaviours it needs the new system to reproduce.

  5. Community or supported edition

    Which edition and version is running affects how the repository is reached and what help is available with it. A self-hosted Community Edition is entirely in the firm’s hands. The edition, the version and any add-on modules installed are recorded at the start of the analysis.

More about moving off Alfresco

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.

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

  1. Analysis

    We read what Alfresco 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 Alfresco: 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 Alfresco, a final pass over a weekend picks up what changed since the trial. Alfresco 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 Alfresco 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 fromAlfresco
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 Alfresco 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

Alfresco to Centerbase: what firms ask

Alfresco is not a legal system. Can its documents still be loaded into one by matter?

Yes, if each document can be tied to a matter by something reliable: a property, the site it is in, or its folder path. The analysis tests that on the real data and reports how many documents fall outside the rule. Those are assigned by hand, loaded to a holding matter, or kept only in the old system.

Do metadata and versions come across?

Properties can be extracted for every item, and versions where versioning was applied. Where they land depends on the destination: a legal document system has a fixed set of profile fields plus some custom ones. Properties with no equivalent are written into a note or description, or left behind, and the firm sees the list first.

Do documents from Alfresco keep their folders and dates in Centerbase?

Centerbase stores documents. Into Document Storage, or left in a connected NetDocuments, iManage or SharePoint store. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.

Does everything in Alfresco have a place in Centerbase?

Most of it does on paper. Emails, notes, calendar entries, tasks and templates 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 Alfresco data is loaded into Centerbase?

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

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

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