Data migration route
Alfresco to MyCase migration
Alfresco is a document management system, and MyCase is a cloud practice management system. Documents and email move out of a store organised by profile and onto the matters they belong to.
AlfrescoDocument management- Documents: Carried across
- Custom fields: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Templates: Confirmed in the analysis
MyCaseCloud- 1 carried
- 1 mapped
- 5 to confirm
What moves
What moves from Alfresco to MyCase
Each row is a kind of record Alfresco holds, whether MyCase 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.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldFiles in repository folders and site document libraries, with typed properties. | Has a placeFiled in folders under each case. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmedDepends on the modules and integrations installed. | Has a place in partSaved emails can be filed to a case; it does not hold mailboxes. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a place | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | To be confirmedWorkflow tasks exist where the process services are in use. | Has a place | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldCustom types, aspects and properties defined in a content model. | Has a placeFields are created on cases or contacts before records are loaded. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partTemplates are rebuilt as Word documents with MyCase merge fields. | Confirmed in the analysis |
What the plans mean
- Carried across
- MyCase has a place for this kind of record. It is loaded there and checked against Alfresco.
- Carried with mapping
- MyCase 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 MyCase is a translation from one to the other, and it depends on the client and matter numbers in Alfresco matching matters that exist in MyCase. 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. MyCase 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
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.
Where it is going
Arriving in MyCase
Loading a firm into MyCase means turning matters into cases and deciding what each case is called, numbered and filed under. The users, practice areas and custom fields have to exist first, because the records point at them. Money needs the most thought: an opening balance can be brought in simply, but how much invoice and trust history is rebuilt behind it is agreed in the analysis.
Every case name is unique
MyCase will not accept two cases with the same name. A firm with forty matters called Estate Planning, or two files for the same pair of litigants, needs a naming pattern before the trial load. Client surname plus the old matter number is one option, and it keeps the old number in view.
Old numbers fit as they are
The case number field takes letters, digits and punctuation, so a number such as 2019-0457/LIT can be kept without reformatting. It is worth keeping it tidy: the email tools match incoming mail to a case by finding the case number in the subject line.
Open or closed, nothing between
A case in MyCase is either open or closed, with a closed date. Source systems often have more states than that: pending, on hold, archived, awaiting payment. Each is mapped to open or closed during the analysis, and the original status can be kept in a custom field.
Practice areas build themselves
On import, MyCase creates a practice area for every distinct value it is given. Family, Family Law and Fam. Law would become three. The source list is reduced to one agreed set during clean-up, so the firm starts with a short list of practice areas it chose.
Lead attorney must exist
The lead attorney on a case has to be a user in the account. Departed fee earners who still own closed matters are a common snag. They are either mapped to a current user, or their name is recorded in a custom field on the case.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in MyCase on this route, 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 MyCase. 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 MyCase 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
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
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 MyCase. 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.
Beyond the data
Setting up MyCase
Loaded data is not yet a working system. This is what NewLaw sets up in MyCase, beyond the migration, so that people can work in it from the first day.
A loaded MyCase account is not yet a working one. The firm still has to decide how cases are classified, who can see what, how money is handled and what clients are shown in the portal. Document templates are rebuilt against MyCase’s own merge fields, since precedents written for another system’s field codes will not merge here. Staff are trained on their own cases once the trial load has been checked.
Set-up decisions in MyCase
- Practice areas and custom fields for cases and contacts
- Trust and operating bank accounts with opening balances per case
- Word document templates rebuilt with MyCase merge fields
- Intake forms and lead pipeline for each practice area
- User roles and who can open which cases
- QuickBooks sync or the MyCase Accounting add-on
Questions
Alfresco to MyCase: 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 MyCase?
MyCase stores documents. Filed in folders under each case. 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 MyCase?
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 MyCase is kept as a readable archive, and you see which before the move.
What has to be decided before Alfresco data is loaded into MyCase?
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.
Other routes
Other routes from Alfresco and into MyCase
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.
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 MyCase are the names and marks of their owners, used here only to identify the two systems.
Moving from Alfresco to MyCase?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.