A Methodology for Consolidating Decades-Old Enterprise Software Portfolios into a Unified Web Platform: Discovery, Data Model Unification, Architecture, and Migration Approach

Authors

  • Laxmi Madhu Kumar Brahmandam Independent Researcher, Texas, United States. Author

DOI:

https://doi.org/10.63282/3117-5481/AIJCST-V7I2P109

Keywords:

Legacy Modernization, System Consolidation, Data Model Unification, Microservices Architecture, Phased Migration, Enterprise Portfolio Management

Abstract

Large enterprises accumulate operational software over decades, ending with portfolios that overlap in capability, contradict in data definitions, and impose substantial cognitive load on users who must traverse them. This paper presents a methodology for consolidating such portfolios into a single unified web-based platform, synthesizing patterns observed across enterprise consolidation programs and validated through a reference deployment that retired more than forty legacy systems serving portfolio, project, and asset management workflows. The methodology comprises three components: a discovery framework that produces a system catalog, a capability map, and a data inventory; a data-model unification approach that resolves cross-system contradictions through user-authored canonical definitions; and a migration discipline that combines phased cutover, coexistence, and reconciliation. The reference deployment under study used containerized microservices distributed across two public clouds, an API-first surface, and a medallion data platform to support continued evolution after consolidation. We report observed values from the reference deployment that show a reduction from forty-three to one production system, a 71 percent decrease in monthly license and support cost, a defect density reduced from 4.8 to 1.2 defects per thousand lines of code, mean time to recovery improved from 6.4 to 1.8 hours, and a 58 percent reduction in user training hours. The findings inform research and practice on portfolio rationalization in long-lived enterprise environments.

References

[1] Brooks, F. P. The Mythical Man-Month: Essays on Software Engineering. Addison-Wesley, 1975, reprinted 1995. https://scholar.google.com/scholar?q=Brooks, F. P. The Mythical Man-Month: Essays on Software Engineering. Addison-Wesley, 1975, reprinted 1995.

[2] Hopkins, B. and Jenkins, K. Eating the IT Elephant: Moving from Greenfield Development to Brownfield. IBM Press, 2008. https://scholar.google.com/scholar?q=Hopkins, B. and Jenkins, K. Eating the IT Elephant: Moving from Greenfield Development to Brownfield. IBM Press, 2008.

[3] Newman, S. Building Microservices, Second Edition. O'Reilly Media, 2021. https://scholar.google.com/scholar?q=Newman, S. Building Microservices, Second Edition. O'Reilly Media, 2021.

[4] Newman, S. Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith. O'Reilly Media, 2019. https://scholar.google.com/scholar?q=Newman, S. Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith. O'Reilly Media, 2019.

[5] Richardson, C. Microservices Patterns. Manning Publications, 2018. https://scholar.google.com/scholar?q=Richardson, C. Microservices Patterns. Manning Publications, 2018.

[6] Evans, E. Domain-Driven Design: Tackling Complexity in the Heart of Software. Addison-Wesley, 2003. https://scholar.google.com/scholar?q=Evans, E. Domain-Driven Design: Tackling Complexity in the Heart of Software. Addison-Wesley, 2003.

[7] Vernon, V. Implementing Domain-Driven Design. Addison-Wesley, 2013. https://scholar.google.com/scholar?q=Vernon, V. Implementing Domain-Driven Design. Addison-Wesley, 2013.

[8] Fowler, M. Patterns of Enterprise Application Architecture. Addison-Wesley, 2002. https://scholar.google.com/scholar?q=Fowler, M. Patterns of Enterprise Application Architecture. Addison-Wesley, 2002.

[9] U.S. Government Accountability Office. Federal Agencies Need to Address Aging Legacy Systems. GAO-16-468, 2016. https://scholar.google.com/scholar?q=U.S. Government Accountability Office. Federal Agencies Need to Address Aging Legacy Systems. GAO-16-468, 2016.

[10] National Association of State Chief Information Officers. State CIO Top 10 Priorities, annual report, 2023. https://scholar.google.com/scholar?q=National Association of State Chief Information Officers. State CIO Top 10 Priorities, annual report, 2023.

[11] Doan, A., Halevy, A., and Ives, Z. Principles of Data Integration. Morgan Kaufmann, 2012. https://scholar.google.com/scholar?q=Doan, A., Halevy, A., and Ives, Z. Principles of Data Integration. Morgan Kaufmann, 2012.

[12] Bernstein, P. A. and Haas, L. M. Information integration in the enterprise. Communications of the ACM, 51(9), 72-79, 2008. https://scholar.google.com/scholar?q=Bernstein, P. A. and Haas, L. M. Information integration in the enterprise. Communications of the ACM, 51(9), 72-79, 2008. | https://doi.org/10.1145/1378727.1378745

[13] Kim, G., Humble, J., Debois, P., and Willis, J. The DevOps Handbook, Second Edition. IT Revolution Press, 2021. https://scholar.google.com/scholar?q=Kim, G., Humble, J., Debois, P., and Willis, J. The DevOps Handbook, Second Edition. IT Revolution Press, 2021.

[14] Amazon Web Services. AWS Well-Architected Framework. https://scholar.google.com/scholar?q=Amazon Web Services. AWS Well-Architected Framework. | https://aws.amazon.com/architecture/well-architected/

[15] Google Cloud. Google Cloud Architecture Framework. https://scholar.google.com/scholar?q=Google Cloud. Google Cloud Architecture Framework. | https://cloud.google.com/architecture/framework

[16] Cloud Native Computing Foundation. Kubernetes documentation. https://scholar.google.com/scholar?q=Cloud Native Computing Foundation. Kubernetes documentation. | https://kubernetes.io/docs/

[17] Lehman, M. M. Programs, life cycles, and laws of software evolution. Proceedings of the IEEE, 68(9), 1060-1076, 1980. https://scholar.google.com/scholar?q=Lehman, M. M. Programs, life cycles, and laws of software evolution. Proceedings of the IEEE, 68(9), 1060-1076, 1980.

[18] Khadka, R., Saeidi, A., Jansen, S., Hage, J., and Helms, R. How do professionals perceive legacy systems and software modernization? Proceedings of the 36th International Conference on Software Engineering (ICSE), 36-47, 2014. https://scholar.google.com/scholar?q=Khadka, R., Saeidi, A., Jansen, S., Hage, J., and Helms, R. How do professionals perceive legacy systems and software modernization? Proceedings of the 36th International Conference on Software Engine | https://doi.org/10.1145/2568225.2568318

[19] Stonebraker, M., Bruckner, D., Ilyas, I. F., et al. Data curation at scale: the Data Tamer system. Proceedings of the Conference on Innovative Data Systems Research (CIDR), 2013. https://scholar.google.com/scholar?q=Stonebraker, M., Bruckner, D., Ilyas, I. F., et al. Data curation at scale: the Data Tamer system. Proceedings of the Conference on Innovative Data Systems Research (CIDR), 2013.

[20] Bass, L., Weber, I., and Zhu, L. DevOps: A Software Architect's Perspective. Addison-Wesley Professional, 2015. https://scholar.google.com/scholar?q=Bass, L., Weber, I., and Zhu, L. DevOps: A Software Architect's Perspective. Addison-Wesley Professional, 2015.

[21] Burns, B., Beda, J., and Hightower, K. Kubernetes Up and Running, Third Edition. O'Reilly Media, 2022. https://scholar.google.com/scholar?q=Burns, B., Beda, J., and Hightower, K. Kubernetes Up and Running, Third Edition. O'Reilly Media, 2022.

[22] Fowler, M. and Lewis, J. Microservices: a definition of this new architectural term. martinfowler.com, 2014. https://scholar.google.com/scholar?q=Fowler, M. and Lewis, J. Microservices: a definition of this new architectural term. martinfowler.com, 2014. | https://martinfowler.com/articles/microservices.html

[23] Humble, J. and Farley, D. Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation. Addison-Wesley Professional, 2010. https://scholar.google.com/scholar?q=Humble, J. and Farley, D. Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation. Addison-Wesley Professional, 2010.

[24] Inmon, W. H. Building the Data Warehouse, Fourth Edition. Wiley, 2005. https://scholar.google.com/scholar?q=Inmon, W. H. Building the Data Warehouse, Fourth Edition. Wiley, 2005.

[25] Hohpe, G. and Woolf, B. Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions. Addison-Wesley Professional, 2003. https://scholar.google.com/scholar?q=Hohpe, G. and Woolf, B. Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions. Addison-Wesley Professional, 2003.

[26] World Wide Web Consortium. Web Content Accessibility Guidelines 2.2. W3C Recommendation, October 2023. https://scholar.google.com/scholar?q=World Wide Web Consortium. Web Content Accessibility Guidelines 2.2. W3C Recommendation, October 2023. | https://www.w3.org/TR/WCAG22/

Downloads

Published

2025-03-26

Issue

Section

Articles

How to Cite

[1]
L. M. K. Brahmandam, “A Methodology for Consolidating Decades-Old Enterprise Software Portfolios into a Unified Web Platform: Discovery, Data Model Unification, Architecture, and Migration Approach”, AIJCST, vol. 7, no. 2, pp. 112–121, Mar. 2025, doi: 10.63282/3117-5481/AIJCST-V7I2P109.

Similar Articles

101-110 of 203

You may also start an advanced similarity search for this article.