Case study / Enterprise modernization
COOPEBANACIO R.L.ERP-WEB
Modernize a critical ERP without stopping the business.
A custom ERP platform built to evolve gradually from a legacy system, while both technology generations coexist.
Modernization in progress
- Custom software
- Legacy modernization
- Enterprise systems
- Client
- COOPEBANACIO R.L.
- Engagement
- Enterprise modernization
- Strategy
- Progressive coexistence
- Platform
- Custom ERP
- Status
- Modernization in progress
01 / Problem
A critical ERP cannot stop in order to change.
COOPEBANACIO runs institutional processes on CODEAS, an ERP that holds years of rules, data and day-to-day operation.
Replacing it in a single cutover creates operational risk: too many dependencies have to be resolved at once, and the business is forced to wait on one break.
The project addresses that problem with a progressive move to a new web platform, so operations can continue while capabilities are transferred.
02 / Intervention
A new platform, designed to coexist.
BRILER designed an ERP architecture around COOPEBANACIO. The platform is meant to coexist with CODEAS while capabilities move across gradually.
Necessary dependencies on the legacy system are encapsulated. New functions can therefore evolve on a modern foundation without requiring a massive initial migration.
Legacy system
CODEAS
- Existing operations
- Business rules
- Existing data
Capability by capability
Coexistence
- Encapsulated integration
- Progressive migration
- Continuity
Modern platform
ERP-WEB
- Modern web platform
- Modular architecture
- New capabilities
A modern platform is already in place. Among other foundations, it includes a web application, an enterprise backend, controlled integration with CODEAS, its own ERP identity, Microsoft Entra ID, SMS campaign capability, and a modular architecture ready to take on new areas over time.
03 / Current outcome
Modernization in progress
A new foundation.Replacement is not the result.
Evolve without conditioning the entire transformation on a single abrupt replacement.
The publishable result is not that CODEAS has been replaced. The result is that a new technology foundation for the ERP now exists.
Modernization can advance by capability. The legacy system can keep supporting functions that have not yet moved. New capabilities are built on a modern architecture.
Engineering approach
Enough depth for the people who run the system.
Technology supports the story. It does not replace it. These are the traits of the platform, not an internal inventory.
- FrontendReact
- ApplicationASP.NET Core
- DataSQL Server
- IdentityMicrosoft Entra ID
- Legacy integrationCODEAS
- OperationsDurable processing
- ArchitectureModular evolution
Modern web application. A React interface for the capabilities that already live on the new platform.
Enterprise backend. Services in ASP.NET Core on a SQL Server database.
Identity and operations. Integration with Microsoft Entra ID, and SMS campaigns as an operational capability.
Encapsulated integration. The connection to CODEAS stays controlled so legacy and the new platform can coexist.
Modular architecture. Prepared to take on new areas progressively, without a full redesign at every step.
Durable processing. Operational capabilities that must complete reliably, not as short-lived one-off tasks.
Capabilities demonstrated
What this work makes visible.
The kinds of intervention this case makes visible.
- 01Custom software
- 02Enterprise systems
- 03Legacy modernization
- 04Systems integration
- 05Technology architecture
Next conversation
Does your organization also need to modernize a critical system?
Tell us the problem. We start with what cannot stop.