By Martin Webster, Chief Revenue Officer, FIntegrate Technology
A community bank we’ve worked with for years recently went through a core conversion. Smart team, capable leadership, well-planned project. They had the new core selected, the contracts negotiated, and a realistic timeline set. What they didn’t have was an answer to a question that surfaced halfway through the contract negotiated (way later than it should have been discussed), “What are we going to do with the old checks, statements and reports; the archive data?
It’s not surprising that the archive data takes the back seat in these conversion (or acquisition) projects. Out of sight; out of mind, I guess. Years of check images, signature cards, loan files, statements, and corporate resolutions sit on a legacy imaging system that nobody plans to keep, but nobody is quite ready to decide about either. Compliance still requires the records. The new core included the legacy data conversion in their agreement, but the price tag for just that conversion. The old vendor keeps invoicing for hosting. The archive becomes a project no one wants, and a decision that gets pushed to a phase two that quietly never arrives.
In my experience, the archive question almost always surfaces through one of three triggers:
- A merger or acquisition, where the acquiring institution is focused on account migration and branch consolidation, and the acquired bank’s archive sits on the side until someone realizes staff still need to research a five-year-old check image post-close.
- A core or imaging conversion, where the archive is treated as a problem for later, until the legacy vendor’s extract fee and the new vendor’s ingestion fee combine into a number that wasn’t in the budget.
- No triggering event at all — the archive simply runs on a server that nobody wants to touch, costing ten thousand dollars or more a month in hosting fees paid quietly out of a department budget no one questions.
In every case, the institution ends up paying for data it rarely accesses but is legally required to keep.
That’s the part that makes “we’ll deal with it later” a genuinely risky posture. The regulators don’t wait. The Bank Secrecy Act requires most banking records to be retained and accessible for at least five years. NCUA’s record retention guidelines require credit unions to maintain records in a format that is accurate, reproducible, and accessible to an examiner, regardless of whether the underlying system has been replaced. FDIC, OCC, and state examiners can request historical documentation during exams, audits, subpoenas, or litigation discovery on their schedule, not the institution’s. If the archive is locked inside a system no one can access, “we meant to address that” isn’t a defense.
The financial cost of waiting compounds quietly. The longer the institution delays, the more leverage the legacy vendor has on extract fees. Institutional knowledge of how the old system was configured walks out the door as people retire. Storage invoices keep running. Ten thousand dollars a month over three years is three hundred and sixty thousand dollars in fees for data the institution rarely touches.
The better path starts with being honest about how the archive is actually used. Once an institution understands that, there are three real options:
- Browser-based access. For data that’s rarely needed but must remain available, the archive is loaded into a secure, browser-based research system that resides on the institution’s own infrastructure. Staff can search, view, print, or email legacy records as needed, and the legacy vendor’s monthly invoice goes away. Typically the fastest and lowest-cost path.
- Hybrid conversion. When some archive data is still actively used (recent check images, commercial loan files, signature cards), the high-value subset gets converted into the go-forward system while the rest moves into a secure searchable archive. In our experience, this reduces conversion cost and timeline by roughly fifty to seventy percent versus a full migration.
- Traditional full conversion. When end users genuinely need historical data to appear in the new system as though it had always been there, a full conversion is the right call, provided it’s run by a team that has done thousands of them rather than internal staff doing data archaeology on top of their day jobs.
FIntegrate has been doing this work for more than twenty-five years. We pioneered legacy data conversion for financial institutions, supported nearly five thousand banks and credit unions, and completed conversions across more than six hundred different imaging and data systems. In our busiest years we’ve delivered as many as three hundred conversions in twelve months. The average institution converts a core system roughly once every eight and a half years. We do it every day. If your institution is facing a conversion, a pending merger, or a legacy invoice you’ve grown tired of paying, the most important question isn’t whether to address the archive. It’s who you bring to the table to help you answer it.
FIntegrate Technology, sales@fintegratetech.com, 1-833-346-8478, fintegratetech.com
