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

Data migration route

Alfresco to SmartAdvocate migration

Alfresco is a document management system, and SmartAdvocate is a cloud case management system for personal injury work. The move is matching each file in Alfresco to its case in SmartAdvocate.

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
ToSmartAdvocateCloud
  • 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 SmartAdvocate

Each row is a kind of record Alfresco holds, whether SmartAdvocate 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 SmartAdvocate
RecordIn AlfrescoIn SmartAdvocateWhat is planned
DocumentsFiles stored in or linked from the systemHeldFiles in repository folders and site document libraries, with typed properties.Has a placeDocuments page, by category and subcategory.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedDepends on the modules and integrations installed.Has a placeEmails are attached to cases.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 placeAppointments and critical deadlines.Confirmed 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 place in partConfirmed in the analysis for each field with no standard home.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt with SmartAdvocate merge codes.Confirmed in the analysis

What the plans mean

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

Every document goes to the case it belongs to.

A case management system expects each document to sit on a case, usually in a category such as correspondence, medical records or court documents. Alfresco organises files its own way, by profile or by folder. So the move needs two rules: which case a file belongs to, and which category it goes in. The first comes from client and matter references or folder names. The second comes from a document type or a subfolder, and where neither exists the files arrive uncategorised and are marked as such.

Cases must exist in SmartAdvocate before documents can be attached to them. If the system is already live, files are matched to its case list and the unmatched ones are reported. If it is new, the case list is created first. Dates, authors and file names are kept. Email comes across as message files. Where several versions of a document exist, the firm chooses between loading the latest and loading them all.

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

SmartAdvocate keeps injury detail in structured fields and screens, so mapping counts for more than usual: the more precisely the old data is placed, the more of those screens are filled on the first day. Parties, incidents, insurers, providers and bills are loaded to their own screens, and the vendor’s implementation team runs conversions into it.

  1. Map to fields, not notes

    The case summary, dashboards and settlement screen read from structured fields. Injury details, insurance limits and provider bills dumped into a note leave those screens empty. The mapping takes each old field to its SmartAdvocate counterpart, and only what truly has no counterpart is loaded as a note.

  2. Case types and statuses

    Cases are loaded against case types and statuses that drive WorkPlans and reports. These are agreed with the firm before the trial load, and old statuses are translated to the new list. A status with no match is not guessed at. It is listed, and someone who knows the files decides.

  3. Document categories

    Documents are searched by category, subcategory, sender, recipient and date as well as by folder. The old system’s folders are translated into categories on the way in. Files that arrive uncategorised can still be found by description, but they fall outside the category views staff are trained to use.

  4. Working with the vendor’s conversion

    SmartAdvocate’s implementation team converts client data into the system and trains staff through its own classes. The firm’s side of that is supplying a clean source, checking the converted cases against the old system, and deciding what to do with the exceptions. Independent help is used on those tasks.

  5. Choosing Server or Cloud

    The firm decides before loading whether it will run the Server edition on its own Windows server or use the hosted Cloud edition. Either way the data load is the same. What differs is who looks after backups, updates and remote access afterwards, and that is settled with the firm’s IT provider.

More about moving into SmartAdvocate

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in SmartAdvocate on this route, which makes it repeatable: a load can be run again until it is right. The maker of SmartAdvocate says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Alfresco and checking each trial against Alfresco.

  1. Analysis

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

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

Loaded data is not yet a working system. The maker of SmartAdvocate runs or arranges the set-up of its product, so this is what has to be decided and put in place in SmartAdvocate, whoever does the work, before people rely on it from the first day.

Setting up SmartAdvocate is a matter of deciding how much of its detail the firm will use from the start. Case types, statuses and WorkPlans come first because they drive everything else. Templates follow. The vendor trains staff through its own classes, and the decisions below are best made before the first of those.

Set-up decisions in SmartAdvocate

  • Choose the Server or Cloud edition with IT
  • Define case types, statuses and staff roles
  • Build WorkPlans and Automated Procedures for each case type
  • Convert letters and forms into templates with merge codes
  • Install the Outlook plugin and agree email filing habits
  • Set up intake screens, lead sources and dashboards

Questions

Alfresco to SmartAdvocate: 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 SmartAdvocate?

SmartAdvocate stores documents. Documents page, by category and subcategory. 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 SmartAdvocate?

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

What has to be decided before Alfresco data is loaded into SmartAdvocate?

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

Moving from Alfresco to SmartAdvocate?

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

We reply within one business day.