Navneet Tyagi, Senior Software Engineer at Finance of America and a Forbes Council Member, published some great tips for these industries on Forbes.com on how to modernize their legacy platforms without disrupting core operations or exposing themselves to risk.
Navneet recommends that companies not make their modernization efforts “too big” by ripping out their legacy infrastructure and replacing it with new systems. He urges IT teams to look granularly and determine what systems are mission critical or have too many dependencies and retention obligations. He advocates that the correct approach is to layer API capabilities onto these legacy systems, to bring them into the modern sphere.
In a nutshell: if it still works and it’s very important, build around the system instead of replacing it outright.
This is a prudent approach that introduces the least disruption, risk and costs in the short term; but how does Navneet suggest institutions handle system replacement when it becomes unavoidable?
Instead of purchasing an entirely new “does-it-all” system, Navneet advises taking the composable approach. Organizations should build an IT portfolio where all critical functions can operate independently but harmoniously.
This resolves several issues at once. Composable architecture can be built piece by piece, in parallel with legacy core systems. This not only breaks modernization down into manageable stages, it also allows for a testing phase for each function. Running core and composable architecture simultaneously enables nondisruptive modernization and ensures a smooth transition when the legacy switch is finally turned off.
The composable approach creates an agile, resilient enterprise that can pursue efficiencies on a modularized basis across their workflows. What Navneet may have overlooked is that building and testing the architecture is only half of the project.
When organizations are ready to switch over to their composable architecture, there is one major step remaining before retiring the old core system: migrating data history to a data retention platform. For regulatory compliance and customer continuity, modernization is not complete until this is done.
Migrating decades of data history is a massive project that will force organizations to extend the life of their legacy systems while they are already using their new architecture. Migrating all of the data history to the new systems is also not the most desirable option. However, this doesn’t have to wait until the last step.
Just as composability turns modernization into an incremental process, data history retention should be done incrementally as well. Transferring historic database access to a data retention platform preceding and over the course of modernization will have three key benefits:
DataNovata is an accessible archiving platform that integrates smoothly with live systems. The solution is platform agnostic and able to integrate multiple database types.
Data migrated to DataNovata maintains its original schema with all metadata and dependencies intact. The DataNovata team tests each data value to ensure that all the necessary data has been migrated before the legacy system is decommissioned. The interface is intuitive and simple searches quickly collate all the relevant data points.
DataNovata also has flexible and granular retention protocols so that each data set can be kept as long as needed and purged when required. Access is also highly customized, with different job roles able to see only permitted data and every access instance generating an automatic report.
DataNovata is not an all or nothing solution. Our clients can migrate as many tables or databases at a time as needed.
DataNovata is a modern, lower-cost platform that allows you to remove data history from the larger migration project, to lower license burdens and speed up modernization timelines.
Ultimately, even the composable approach to legacy modernization is a huge undertaking. Tools like DataNovata can help make that process easier, faster, safer, and more cost-effective.