Legacy Data Access with Data Integration

July 21, 2021
legacy data access

It is safe to say 40 years, 30 years even 20 years ago, most organizations were not contemplating the omnichannel experience that exists today. Today’s consumers may not be old enough to remember life before ATM/Debit cards, but they were one of the first tools that began the automation of consumer experience with back-end data. Many computer systems that exist in large corporations may also predate ATM functionality and have not been built with consumer interaction in mind. The cost of rearchitecting or replacing these Legacy systems is often cost-prohibitive and, in many cases, the systems themselves are effective and do not need to be replaced, but we still need access to the data. That is where we find effective Data Integration. The ability to access and retrieve back-end system or Legacy data and make it available to multiple front-end systems and channels.


Challenges of Legacy Data Integration


For organizations that have conquered successful Legacy Data Integration, they will attest that it was not always straightforward. From identifying all uses and users of the data to defining new data access, availability and security requirements, there were many considerations to address. Legacy Data can exist in flat files, relational databases, non-relational databases, and within applications themselves. Creating a new set of services to access, read, write from/to your Legacy Data while maintaining optimal performance and efficiency takes time and planning. Collaboration with all impacted departments within an organization is essential. Taking time to consolidate repetitive and redundant data wherever possible will help an organization streamline its processes and reduce unnecessary complexity and system resources.


Accessing the data


There are several methods that can be used to Integrate your Data into disparate systems. You can choose a batch data transfer, a messaging-based approach, an enterprise service bus (ESB), or application programming interfaces (APIs). Organizations most often will select several approaches depending on the data need and type of architecture they have in place. When it comes to accessing the data, one size will not fit all and that is okay.


Different Channels, Different Data


Website, IVR, mobile app, chat, email, applications. There are many channels that will depend on the Data Integration services that an organization creates. Each channel may require different ways to access the data and varying levels of detail in the data that is returned. Ensuring your Data Integration strategy can accommodate the different needs of the disparate channels is crucial for success.


The Data Integration Process


There are several steps involved with data integration, and they can vary depending on the current state of your data, what processes are currently in place, how much time and maintenance is required, and what the proposed solution is, among other considerations. Each organization will have its own unique list of items to consider, and a good first step includes getting the right people on the same page.   Ensuring your business owners, data owners, and IT owners are aligned with the Data Integration Strategy will ensure the effort starts off right.


Optimizing Your Data


Properly understanding the organization's needs, goals, and uses of their legacy data allow for both a more focused integration and improved performance.  Once the organization's needs are clearly defined, it allows for the proper access methods, like APIs or batch data transfers, to be chosen to optimize the integration. From there the data needs to be properly mapped to the respective applications, systems, and data pages that will be utilizing the information to meet business goals and objectives. During this process, the question of optimization needs to be consistently brought up. The difference between data that is only updated daily versus every several minutes will affect how frequently calls need to be made for the integration to guarantee that users are viewing accurate and relevant information. 


Testing for Success


Testing of the integration is a continuous process that needs to be happening throughout the entire effort. Too frequently, organizations fail to properly plan for the integration QA testing and find themselves delaying projects as they wait for QA to catch up. Proper planning of data integration testing throughout the entire development and approval process will vastly improve the entire integration experience.  

Kona Kai: Optimizing Business Performance


The task of data integration to multiple applications is no small feat and tackling the task on your own may quickly overwhelm you, even with smaller projects. Therefore, it is critical to work with a data integration expert who has the time and resources needed for your project. Begin your data evolution with the experts at Kona Kai Corp.

INSIGHTS

By Paul Benvenuto August 19, 2026
AI is changing workforce training from a one-time project into a continuous business capability. For decades, enterprise technology transformations have followed a predictable pattern. A new system is implemented, then employees learn how to use it. Productivity dips for a while, then recovers as the organization adapts. Whether it was a CRM implementation, ERP modernization, a claims platform replacement, or a core banking upgrade, the skills gap eventually disappeared because the technology itself stopped changing. AI is different. Unlike traditional enterprise software, AI capabilities continue to evolve after implementation. New models are released, AI agents become more capable, and workflows change faster than most organizations can retrain employees. The result is a workforce that isn't simply learning a new system, but continuously adapting to one. That fundamentally changes how organizations should think about workforce readiness. Recent research from the World Economic Forum and Microsoft's Work Trend Index suggests many organizations already recognize the challenge. Are enterprises doing enough to prepare for a skills gap that may never close? AI Changes the Rules for Workforce Training Traditional enterprise software had a finish line. Once employees learned the new system, their knowledge remained valuable for years. Training programs could be planned, measured, completed, and archived because the technology itself remained relatively stable. AI doesn't offer that stability. Employees who learned effective prompting techniques six months ago may now be using AI agents. Teams that started with document generation may now be automating entire workflows. Capabilities continue to expand, changing what effective work looks like almost as quickly as organizations can document it. That means workforce readiness can no longer be viewed as a milestone that follows implementation, as it needs to become part of day-to-day operations. The AI Skills Gap Doesn't End After Go-Live The challenge isn't simply that AI is changing jobs. It's that AI itself keeps changing. Foundation models continue to improve. New copilots are released. AI agents take on increasingly sophisticated tasks. Features that didn't exist six months ago become standard workflow tomorrow. Employees aren’t learning one “system” because they need to continuously adapt to new capabilities. Someone who learned the most effective way to use AI six months ago may already be working differently today. Traditional training models weren't designed for that pace of change. AI Is Reshaping the Workforce Faster Than Organizations Can Respond The World Economic Forum's Future of Jobs Report 2025 highlights just how significant this challenge has become.
By Paul Benvenuto July 31, 2026
PwC's April 2026 AI Performance Study surveyed 1,217 senior executives across 25 sectors and found something that should reframe how every regulated organization talks about AI investment: nearly three quarters of AI's economic value is being captured by just one fifth of organizations. Not because that top fifth has better models. PwC is specific about the differentiator: those organizations are 1.7 times more likely to have a Responsible AI framework and 1.5 times more likely to have a cross functional AI governance board. Their employees trust AI outputs at twice the rate of everyone else's. The value gap is structural, not a matter of who bought the better tool. That finding lands differently once you connect it to where trust actually comes from. It doesn't come from a more sophisticated model. It comes from knowing where your data originated, who touched it along the way, and what controls sat around it the entire time.  McKinsey's June 2026 research on AI data readiness makes the case that most organizations manage data like a storage problem when they should be managing it like a supply chain. A single PDF can expand into extracted text, tables, images, metadata, sensitivity tags, and quality scores, each one an intermediate artifact that AI systems reuse and recombine downstream. A small error introduced upstream doesn't stay small. It propagates. This matters more in regulated industries than almost anywhere else, because the data causing the most exposure is usually the data getting the least attention. Structured fields get governed. Clinical notes, claim narratives, loan officer comments, and audit trails, the unstructured stuff, usually don't, even though AI systems depend on it heavily. Gartner and IDC both put the share of enterprise data that is unstructured at somewhere around 80 to 90 percent. McKinsey's own research doesn't cite that specific figure, but makes the same underlying point: unstructured content is where AI systems draw the most context, and where governance attention is thinnest. None of this is an argument for waiting until your data is perfect before you deploy anything. PwC's 2026 Digital Trends in Operations Survey argues directly against that instinct: AI can help bridge data gaps, particularly through agents that reason using whatever data is actually available. The real mandate isn't clean data as a prerequisite. It's disciplined governance and iterative improvement running in parallel with deployment, calibrated to how much risk a given use case actually carries. So what does that look like in practice for a CIO or CDO sitting inside a regulated organization right now? A few diagnostic questions worth asking before your next AI initiative launches: Where does data quality actually break down in your pipeline, and does anyone own fixing it? Is lineage visible for the data feeding your highest risk AI use cases, or is it assumed? Where do unstructured assets, like clinical notes, policy documents, and loan files, enter your systems without any governance attached? Have you defined what "good enough" data quality means for each use case, calibrated to its actual risk profile, rather than applying one standard everywhere? Answering those honestly is uncomfortable in most organizations, because the answer is usually "we don't fully know." That's the point. You cannot govern what you cannot see, and you cannot trust an AI output built on a data foundation nobody has actually traced. The organizations in PwC's top 20 percent didn't get there by waiting for perfect data or by buying a better model. They got there by treating governance as a financial performance variable, not a compliance checkbox, and by building the lineage and controls that make trust possible at scale. Kona Kai's data supply chain assessment is built to answer exactly these questions before tool selection, not after. If you're not certain where your organization would land on that list, that uncertainty is worth resolving now. Get in touch to talk through what the assessment covers. Sources: PwC 2026 AI Performance Study, April 13, 2026 (74%/20% figure and 1.7x/1.5x/2x multipliers confirmed directly at pwc.com); McKinsey, AI Data Readiness: The Key to Scaling Impact, June 2026; Gartner and IDC estimates for the 80-90% unstructured data share; PwC 2026 Digital Trends in Operations Survey.
By Paul Benvenuto July 29, 2026
Every governance and workflow framework most organizations are running today was built for AI that waits for a human to ask it something. Agentic AI doesn't wait. It initiates, executes, and chains actions across systems on its own, and the workflows built around human initiated, human reviewed steps simply don't have
By Paul Benvenuto July 27, 2026
Education was the number one way companies say they adjusted their talent strategy in response to AI. And yet most organizations still treat training as an event. A workshop. A certificate. A box that gets checked once and never revisited.
By Paul Benvenuto July 20, 2026
Most organizations think they have AI governance because someone in legal drafted a policy and got it signed off. They don't. A policy sitting in a shared drive doesn't know where your AI is actually running. It doesn't flag it when a model drifts. It doesn't do a single thing when an employee routes a client file thro
By Paul Benvenuto July 20, 2026
Governance, people, data, and process are not sequential steps. They are four load-bearing walls, and in regulated industries, a crack in any one of them shows up as risk somewhere else. Here is where each pillar actually breaks down today, and what the data says about the gap between where most organizations sit and w
By Carly Whitte July 1, 2026
AI success depends on more than technology. Governance, regulation, and operational oversight are helping organizations turn AI pilots into scalable business capabilities.
By Carly Whitte June 27, 2026
Healthcare AI adoption depends on more than technology. Governance, accountability, and AI readiness determine whether AI delivers measurable business value.
By Carly Whitte May 24, 2026
AI-powered “vibe coding” is accelerating enterprise software creation, but governance and security controls are struggling to keep pace. Learn the hidden risks of AI-generated applications and why responsible AI governance is critical for scalable enterprise adoption.
By Carly Whitte May 6, 2026
Why does AI adoption stall in healthcare? Discover how accountability, governance, and risk management influence success beyond change management.