One of our customer success stories recently made headlines in the Credit Union Journal. Randolph-Brooks Federal Credit Union used Centerprise to migrate its legacy data to a new Fiserv core banking system. With over 400,000 members and assets exceeding $5 billion, RBFCU serves more than 2000 membership groups and communities across the South Central Texas area and beyond, making the conversion project quite daunting.
Credit unions are increasingly investing in newer software and technologies. Embracing new technology is helping these businesses develop innovative new services that give them a competitive edge. Basing these services in the cloud is helping to lower their costs. Both of these trends mean considering new software systems, which is a challenge to IT departments. One of the biggest issues is mapping years of legacy data from old software systems into fields in the new system.
Data migration issues were blocking RBFCU’s move to a new banking system and keeping it from modernizing its services. Years ago, the credit union internally developed a core banking system to store and maintain member account information. As its membership and product offerings grew, the homegrown solution soon grew to hundreds of tables storing hundreds of gigabytes of data.
Because of the legacy system’s design, the credit union’s ability to develop modern, member-centric software applications was severely hindered. Fitting new products and services into the system took excessive amounts of time and the team was already burdened with completing many regulatory changes to keep the core system compliant, which prevented them from focusing on developing productive software applications.
RBFCU evaluated IBM, Talend, SSIS, and Centerprise and ultimately selected Centerprise because it met and exceeded all objectives. The learning curve was not too high as the team discovered the interface to be fairly straightforward; developers were able to drop and come back to the tool without having to relearn it. And, with the Centerprise SQL Source and Lookup components, they were able to leverage and translate their SQL skills right away. Additionally, the Name Parser component was an unexpected bonus, which saved them additional development time. What would have taken at least a week with an in-house solution was now getting done in half a day.