What is a data migration?
Data migration (also known as data conversion or data transfer) is the process of retrieving a firm’s data from their previous legal software package and importing it successfully into a new legal case or practice management system. When it comes to data migration the needs of one law firm can differ significantly from another in terms of scope and complexity, so it is important to have a detailed and robust plan in place.
Access Legal, having over 40,000 users across 3,800 law firms has experience and best practice processes in place to convert financial, case, matter data and documents over from a variety of other systems.
This article offers guidance for law firms considering a data conversion from one legal system to another in terms of the process and what they should expect from their ‘old’ software supplier as well as their ‘new’ software supplier.
1. Include Data Migration Experience On Your New System Check-List
Data migration skills should be one of your criteria when finding a suitable new software supplier. The Data Conversion is the foundation upon which everything to do with your new system will be built. Make sure yours is solid.
Of course some law firms make better use of their data than others, however, even though the legal profession was built on talent, tradition and tomes of case law, the firms trailblazing in terms of how they use their data are embracing technologies to support them with better decision making based on the insights from their data analytics to give the law firm a competitive advantage.
In our data-driven world even the firms that aren’t yet getting the most out of their data, but have aspirations to do so, still rely on it heavily for compliance and the day to day running of their businesses.
So as part of your search for a suitable new legal case and practice management software for your business make sure you include data migration experience on your list of criteria – beyond just looking at the capabilities of the software itself.
When choosing a new legal software partner – a law firm should also check the new software supplier’s data privacy policy, review the supplier’s information security credentials and ask the new supplier to sign a non-disclosure agreement due to the sensitive nature of the data they are being trusted with.
The best legal software suppliers are ISO 27001 Security Certified Software Supplier at both company and data centre level, are fully committed to General Data Protection Regulation (GDPR) compliance, and should be members of the LSSA which has a code of conduct covering data migration amongst many other things.
2. Remember It’s Your Data
Although some software suppliers may act as though the data in the old system you have decided to leave behind is their data, it does of course belong to the law firm. The law firm owners are entitled to a complete copy of their data in its entirety.
Any reputable legal software provider will have no problem providing you with your data and often use a single standard database making the retrieval of your data straight forward. If a law firm discovers their data is not held in a single industry standard database and their old supplier has trouble, or is unwilling, to provide the data in its native format then the firm is quite within its rights to have the supplier make a complete copy of their data available in an alternative format (e.g. Microsoft SQL, XML with a DTD – document type definition, Microsoft Access, CSV, Excel, documents in logical folders with index information showing which documents are related to which cases etc.).
Before you sign on the dotted line, there are a few direct questions you should ask your new supplier about data retrieval should you ever decide to leave them in the future:
- Will you auto-generate a copy of our data in SQL database (or other database) format for data migration purposes if we move onto an alternative practice management system supplier?
- Please list the types of data that would be available for data conversion, and how will you provide relevant paths and structural information that indicates how our data records relate to each other?
- How will you supply all of our case related documents and how will how will you ensure it is clear which matter/files they relate to?
- What kind of fees should we expect from you for facilitating the retrieval of our data in a usable format?
Starting life with a new case and practice management system without your data is less than ideal for any law firm. Make sure you have in writing, before you sign the contract, that your data will be completely retrievable should you ever need it, in a usable format, auto-generated, with no manual intervention required by yourselves. It’s a disappointing reality, that not all suppliers provide this.
3. Consider The Scope Of Your Data Migration – What Do You Need?
Up front a law firm must decide the level of complexity it requires for its data migration. For example, at one end of the scale the law firm may decide it only wants the very basic static client and matter data taking over to the new system. However, at the other end of the scale a full transfer could include all historical and transactional data.
The choice would be:
STATIC DATA ONLY
- Client data
- Contact data
- Matter data
- No balances
- No transactions
STATIC DATA & BALANCES
- Client data
- Contact data
- Matter data
- Top level balances
- No transactions
STATIC DATA, BALANCES & TRANSACTIONS
- Client data
- Contact data
- Matter data
- Balances
- Transactions
FULL TRANSFER
(Although not many firms ask for this or need it in reality these days)
- Client data
- Contact data
- Matter data
- Balances
- Transactions
- Case management data
- Documents
- Peripheral data
4. Set Your Expectations Regarding Timescales and Fees
A law firm should expect to receive their data from the current supplier in a reasonable timeframe (e.g. within one working week from the date it is requested would not be unreasonable), and you should not expect to be charged for the data itself, although it is quite reasonable to expect to pay for the supplier’s time for extracting your data, especially if your data retrieval needs are all encompassing or complex.
Charges from the supplier you are leaving should reflect the work required to retrieve your data, and care must be taken not to accept a punitive fee as ‘sour grapes’ due to the fact the supplier is losing your firm as a client.
You may be expected to settle any outstanding invoices owed to your current supplier before they hand over your data, which again is quite reasonable and often outlined within a software supplier’s terms of business or contract.
Your new supplier of course has the most work to do when it comes to your data migration project and again, a law firm should be prepared to pay for the supplier’s time.
5. Organise Dual Running If You Can
Reputable legal software providers will be professional and help you as much as they can with the smooth transition from one system to another.
The dual running of both the old and the new system for a short while is often the ideal scenario for reporting and enquiry purposes to make the transition efficient and painless.
If dual running is not possible reports should be generated at the point of closing the old system which will meet the requirements of external auditors and the SRA (e.g. aged creditor, aged debtor, matter balance, nominal ledger, WIP, purchase ledger, trial balance, balance sheet reports etc.). These reports must match the reports from the new system exactly, and you need to retain them for your records for the long term.
6. Firms Must Acknowledge That Rubbish In Means Rubbish Out
It sounds so obvious, but it’s easy for people to bury their heads in the sand when it comes to facing up to the quality, or lack of quality, when it comes to their data. We recommend a focused data cleansing exercise before starting the data migration process. A data transfer at transaction level of course will transfer all data including records that don’t balance. If you’re expecting the data migration to magically eliminate long-term data irregularities then you would be kidding yourselves.
It really should go without saying, but every effort must be made by the law firm to provide clean data for the new software supplier to work with.
7. Communicate, Communicate, Communicate
Teething problems are inevitable when implementing a new system, but if you plan properly and work in partnership with your new legal technology provider there is no reason why your data migration shouldn’t run smoothly and painlessly, especially when working with experts who have years of experience migrating law firm data from a wide variety of systems.
Prevention is always better than cure – so the best advice to any law firm considering a data conversion is to discuss any data concerns with your new supplier early, and work together to iron out any challenges.
The way data is held in your old system could be entirely different to how it is going to be held in your new system (for example, your new system may store address details in multiple fields compared to storing it in one address field in your old system). These are the kind of questions your new legal software supplier should be asking you as part of the data migration planning process and the law firm must take these questions seriously - so in this instance the one address field coming from the old system can be broken down into relevant street, town, county, post code fields for the new system.
It is likely the system you are moving to will be more sophisticated than the system you are leaving behind. E.g. Access software has a link between a bill record and the time transactions included on the bill. If your old system doesn’t go this far this will affect the data transfer. It shouldn’t be a problem for a good data migration expert as long as these differences are flagged up during the planning process.
A good supplier will know the right questions to ask and will guide the law firm to ensure they take the time to provide the relevant level of detail in their answers.
It is always in the best interests of the law firm to highlight as early as possible any data concerns they may have.
8. Expect Some Manual Transformation
Prior to the data migration, it is prudent to expect to have to do some manual data translation (or transformation) to prepare your data to be imported cleanly into your new system. E.g. simple things like matching the old system formats to the new, such as changing fee earner references to fee earner initials. Some manual data transformation may be more complex than this though, but it is worth bearing in mind that most data conversions that involve legal accounts and practice management software will require some level of manual data transformation before the data migration can take place. A good software supplier will make the transformation steps clear before you start, and will work with you to ensure the data structure is correct.
In some cases a law firm’s data may be too complex to match over to the new system, even with manual data transformation. If the system you are leaving differs massively from the new system you are adopting detailed discussions need to be had with your new software supplier. A good technology partner will help you work out the best way of tackling any format matching difficulties.
9. Always Do A Trial Run
In preparation for a successful data migration it is advisable to have at least one trial run of the conversion prior to the live data migration. The trial run is the law firm’s chance to check that all expected data is available in the new system, stored where and how expected, and that it operates as it should.
Corrections can sometimes be very difficult to manage after a ‘live’ conversion once the system is being actively used. A trial run enables the law firm to check data has converted correctly and provides the opportunity to carry out any corrections to the data migration plan before going live. A trial run will reduce the pressure and allow the firm more time to check the integrity of their data, making the live conversion far safer.
A good legal software supplier will help you prepare a check-list plan so you can produce a set of reports for conversion checking purposes as part of the trial run. E.g. matters with financial balances allow the firm to check overall totals as well as spot check individual clients and matters.
Your new software partner should recommend a list of reports for you to run off, as a good starting point for data checking purposes, following a data migration. It is essential the recommended reports include totals and are run off at the same time as the data back-up for conversion and that no changes are made to the system between the reports being generated and the data being taken. Timing is key and your new software supplier should discuss and plan this with you as part of the project. The Data Migration experts can provide a list of screen-shots to be pulled off as part of the trial run, also for data checking purposes.
Some firms store very large volumes of documents, so it may be practical to migrate only a subset of these for the trial run. This will allow you to test that the document migration works effectively whilst cutting download time before you migrate the whole lot. It is advisable to take document creation and modification dates and times for these files as part of your data set to be converted over.
Why not hear from our customers themselves explaining not just the benefits of the software and working with the Access Legal team, but they also talk about their data conversion experience.
10. Plan Adequate and Timely Resources For Acceptance Testing
After the trial run, it is the law firm’s responsibility to allow sufficient time and resources to thoroughly testing the converted trial run data before moving onto the live environment. This process is known as ‘acceptance testing’ and it should be carried out as soon as practically possible after the trial run, because the sooner issues are identified, often the easier they are to resolve. Access provides new customers with advice and guidance on how best to achieve this.
Shortly after the trial run is completed, the law firm needs to confirm the following to the software supplier:
- Do the balances agree?
- Was the data converted according to the agreed rules?
- Were any fields overlooked during the trial run?
- Do you have the correct number of records expected from the trial run in the new system?
- Reports required?
- Further data cleansing required prior to live migration?
- Were any data problems picked up?
- Agreed actions?
(This is not an exhaustive list – but for firms moving over to new software, your new supplier’s data migration experts should help you establish what’s important for your firm.)
It is quite likely that the law firm will discover some items that have not converted over as expected during the trial run. This is exactly what the trial run is for. During acceptance testing the law firm and the software supplier will be able to assess the success of the trial run and agree whether another trial run is required once data correction actions have been completed, or whether the firm is ready to move to the live data migration. The law firm testing team should document in detail any inconsistencies or problems and summarise their findings in a standardised format and send to the software supplier for correction, prior to the live data migration.
At the end of the Acceptance Testing process, the law firm will be asked to approve and sign off the results before moving on to next steps.
11. Accept There Needs To Be Some Contingency Planning
A good legal software supplier will provide hand-holding for ‘go live’ as your users begin to start using your new system in earnest in those early days. Detailed acceptance testing will have been carried out by this point so chances are a large percentage of your data will be intact. However, even with the most prudent planning and checking it is still possible users may discover unforeseen problems after go live. Anything like this should be reported to your software supplier immediately and logged. Once aware a good software partner will establish if the issue can be easily resolved or if it will require more significant corrective work. Corrections to conversions can range from simple manipulation of converted data that may have been incorrectly transformed, through to a more significant flaw that would require a complete re-run of the whole conversion. Although unlikely, an entire re-run should be built into contingency plans just in case.
At the end of the day a data migration is a team effort between law firm and software supplier and it is in everyone’s best interests to get it right first time.
The three legal software companies that make up Access Legal have been delivering first class legal practice management software for many years, and during this time we have converted data from most of the software packages available in the legal IT marketplace today, including the following (as well as converting data over from a few bespoke systems):
- AIM
- Advanced
- ALB
- Alpha Law
- Axxia
- Clio
- Cognito
- Cubetek
- Denovo
- Elite
- Evolution
- Filestream
- FWBS/3E Mattersphere
- iLaw
- Indigo
- Insight Legal
- Intelliworks
- LawByte
- LawPro
- Lawsoft
- Leap
- LegalOffice
- Legis
- Linetime
- Meridian
- Millennium
- Moutain
- Mylegaloffice
- Norwel
- OfficeCase
- Opsis
- Osprey
- Paragon
- PC Law
- Peapod
- Peppermint
- Perfect Books
- Professional Technologies
- Quaestor
- QuickBooks
- Quill
- Redbrick
- Sage
- Solcase
- Solidus
- Sol Ledger
- SOS
- StrongBox
- TFB
- Timeslice
- TPS
- Videss
- Visualfiles
- Xero
Our top tips for law firms for a successful data migration is not an exhaustive list, but it is a good starting point for firms looking for new legal software and are planning a data conversion.