Moving off a system
Migrating from Alfresco
Open-source content management platform from Hyland, with a repository of folders, sites, typed content and configurable metadata. This page sets out what Alfresco holds, what moving off it involves and where its records can go.
Where it can go
Routes from Alfresco
Each route has a page of its own: what moves, what has no place in the destination and how the move is run.
Practice management systems
Actionstep2 of 7 kinds of record have a place
Centerbase2 of 7 kinds of record have a place
Clio Manage2 of 7 kinds of record have a place
MyCase2 of 7 kinds of record have a place
Rocket Matter2 of 7 kinds of record have a place
SimpleLaw2 of 7 kinds of record have a place
Smokeball2 of 7 kinds of record have a place
SurePoint Finance EnterpriseWhat has a place is confirmed in the analysis
Case management systems
Document management systems
Accounting and billing systems
CRM and intake systems
File storage
Box2 of 7 kinds of record have a place
Dropbox1 of 7 kinds of record has a place
Google Drive1 of 7 kinds of record has a place
OneDrive1 of 7 kinds of record has a place
Server drives1 of 7 kinds of record has a place
SharePoint2 of 7 kinds of record have a place
Sync.com1 of 7 kinds of record has a place
What it holds
The records Alfresco keeps
Fourteen kinds of record matter to a move. Alfresco keeps two of them, and five could not be confirmed from its maker’s own material.
- MattersNoNo matter record is built in. Firms model one as a site, a folder or a custom type.
- ContactsNoClients, other parties and referrers
- DocumentsYesFiles in repository folders and site document libraries, with typed properties.
- EmailsTo be confirmedDepends on the modules and integrations installed.
- NotesTo be confirmedFile notes, matter notes and contact notes
- CalendarTo be confirmedAppointments, court dates and deadlines
- TasksTo be confirmedWorkflow tasks exist where the process services are in use.
- Time and expensesNoTime and expense entries, billed and unbilled
- BillingNoInvoices, payments and debtor balances
- Trust moneyNoTrust or client account ledgers and balances
- Firm accountsNoGeneral ledger, office account and payables
- Custom fieldsYesCustom types, aspects and properties defined in a content model.
- TemplatesTo be confirmedPrecedents, document templates and automation
- IntakeNoLeads, enquiries, intake forms and pipelines
Moving off it
Leaving Alfresco
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.
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.
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.
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.
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.
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.
The system
What Alfresco is
Alfresco is a content management platform that now belongs to Hyland. It is general-purpose software, not a legal product, and comes as an open-source Community Edition and as the supported Alfresco Content Services. Law firms and legal departments that use it have usually had it configured for them, by an in-house team or an integrator, to hold matter files, contracts or records.
Content is held in a repository as folders and files, each with a type and a set of properties. A content model defines the types, and aspects add further groups of properties to individual items. Users generally work through the Share web client, in sites that each have a document library. Process automation and records governance are separate services built on the same repository.
- Kind
- Document management
- Runs as
- On the firm’s server or a hosted server (not confirmed from its maker’s material)
- Made by
- Hyland
- Mainly used in
- Worldwide
- Also known as
- Alfresco Content Services, Alfresco Community Edition, Alfresco Share, Hyland Alfresco
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in the new system on most routes, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Alfresco holds and how it is organised, then agree with you where each kind of record will sit in the new system. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into the new system 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.
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
Choose where the Alfresco data is going, or tell us you have not decided. The first step is the analysis, and the price is fixed once it is done.
Step 1 of 5
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Alfresco holds
What is in it, how its records link, and where each piece would sit in the new system. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- A fixed price in writing
Set after the analysis, so it reflects what is in your data. You have it before any work starts.
After the move
Setting up the system you move to
A migration ends with data in a new system. Whether people can work in it on the first day depends on how that system was set up: matter types, templates, billing, permissions. NewLaw does that work as well, and each destination’s page says what its set-up involves.
Set-up, by destination
- Actionstep
- Box
- Centerbase
- Clio Manage
- Dropbox
- Filevine
- Full data export
- Gladiate
- Google Drive
- iManage Cloud
- Lawmatics
- LexWorkplace
- Litify
- Microsoft SQL Server
- MyCase
- Neos
- NetDocuments
- OneDrive
- QuickBooks Online
- Rocket Matter
- Server drives
- SharePoint
- SimpleLaw
- SmartAdvocate
- Smokeball
- Soluno
- SQLite
- SurePoint Finance Enterprise
- Sync.com
Questions
Moving off Alfresco: 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.
Where to start
Still deciding where to move?
Choose the system before you plan the move, and see where AI fits once your data is in it.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Alfresco and the other product names and logos on this page belong to their owners and are used only to identify the systems.
Moving off Alfresco?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.