The Problem
When iWorks came on board, VSOSJ was relying on two separate legacy databases — Microsoft Access and FoxPro. The two systems had grown side by side over time, with different structures and no proper integration between them. The original developer had long since moved on, and nobody in the organisation fully understood how either system had been built or how the data was organised. By that stage, the situation had become serious. The only way to access the databases over the network was through a virtual machine running Windows 98, an operating system that has been unsupported since 2006, with no security updates and no realistic long-term future. The organisation’s IT team had put this in place as a workaround, but it was never a real solution. If the hardware failed or the virtual machine became corrupted, the organisation could have lost its core operational data for good, member records, student profiles, and years of grant allocation history.
Key Challenges
- Two separate legacy databases (Access and FoxPro), each with a different structure and both needing to be replaced.
- Access is limited to a Windows 98 virtual machine, leaving the organisation one failure away from total data loss.
- The original developer was no longer available, and there was no internal understanding of how the systems worked.
- Grant and fee tracking across 60 branches and 300 students was being managed manually across multiple sources.
- There was no reporting capability and no public-facing digital presence.
The Migration Process
One of the biggest technical challenges in the project was extracting clean data from two structurally different legacy databases, Access and FoxPro. Because the systems had been maintained separately and did not communicate effectively, duplicates, inconsistencies, and missing information were unavoidable. Before any new development started, iWorks spent time understanding the existing data, mapping the relationships between the two systems, and defining what a clean, unified dataset should look like. Member records, branch associations, student profiles, and historical grant allocations were all extracted, reconciled, and imported into the new MySQL database. The work was carried out methodically: data was reviewed category by category, discrepancies were flagged, and the organisation’s office team worked closely with iWorks to resolve any ambiguities before cutover. By the time the new platform went live, the data was cleaner and more reliable than it had ever been in the old setup. The Windows 98 virtual machine was retired on go-live day. There was no phased handover, because the risks of leaving the old system running in parallel were simply too high. The migration had been planned carefully enough that a clean cutover was the right decision.
Technical Summary
- Legacy systems: Microsoft Access and FoxPro (two separate databases), replaced by CI4 / MySQL.
- Framework: CodeIgniter 4 (PHP).
- Hosting: Amazon Web Services (AWS).
- Public website: WordPress with full content management capability.
- Payment types: First Fee, Second Fee, General Expenses, Theology, and Special Grant.
- Scale: approximately 60 branches, around 300 students, with five payment types per student.
If your organisation is still relying on ageing database technology and needs a clear path forward, iWorks would be happy to have an initial conversation. Contact us hereor call 01