To address a looming skill shortage and rising support costs, a global retail company made the strategic decision to retire its aging AS/400 system, built with RPG and COBOL. With a globally distributed user base, the key challenge wasn’t just technical — it was also minimizing user disruption during the transition.
Partnering with Bangalore Softsell Ltd, the company embarked on a 15-month modernization journey to migrate its legacy stack to a scalable, web-based Java system — without overhauling how users interacted with the platform.
The legacy AS/400 system was:
- Built over decades using RPG and COBOL
- Supported both batch and online functions (approx. 40–60% split)
- Dependent on a shrinking pool of experienced developers
- Operated by non-technical users across geographies, with language barriers
The challenge was two-fold: modernize the backend, and retain a familiar user experience.
- Proof of Concept:
- Application knowledge capture
- Architecture definition
- Prototype screen generation
- Functionality Audit:
- Removed obsolete features to reduce complexity
- Validated only essential functions were migrated
- Migration Pipeline (via LeMiT):
- Screen prototyping
- Database modeling → migrated to MySQL
- Data migration in two cycles (Test & Production)
- Code migration → Java-based, audit-compliant
- Code Audit Readiness:
- Java standards were enforced in translation
- Migrated code passed external consultant audits
- Training & Change Management:
- Minimal retraining, with familiar UI replicated on the web
- Users across geographies onboarded at Go-Live
The following diagram shows the full modernization workflow, including intermediate outputs and phased validation steps:
✅ UI Migration
✅ Database Migration → MySQL
✅ Data Migration (including 7-year history for critical tables)
✅ Code Migration → Java
✅ Testing (Web vs. AS/400 use cases)
❌ Test case definition
❌ User acceptance testing
Third-party interface planning is critical. Integration must be co-designed with the migration plan.
AS/400 error management doesn’t map one-to-one with web systems — custom error handling strategies were required.
Translation is action-based, not line-by-line — requiring functional validation during migration.
Architecture & functional criteria must be validated upfront and signed off as deliverables.
Successfully completed a 15-month modernization project, including full data and code migration
Delivered Java-based architecture built for long-term maintainability
Users worldwide were re-trained and transitioned smoothly at Go-Live
External Java code audit passed without rework — confirming code quality and compliance
Laid the groundwork for future enhancements, mobile readiness, and integration capabilities
AS/400, RPG, COBOL, LeMiT™, Java, MySQL, Web UI Frameworks
LeMiT is a proprietary modernization platform of Bangalore Softsell Ltd. This case study reflects one implementation scenario. Results may vary based on system complexity and business environment.
