Executive Summary
SBI Factors Limited, a subsidiary of State Bank of India and one of India’s leading factoring and receivables financing companies, was running its core financial operations on an on-premises Oracle 19c database environment. Over time, Oracle’s licensing costs, vendor lock-in, and operational overhead had become significant constraints on the business.
SBI Factors Limited partnered with Teleglobal to migrate its mission-critical databases from Oracle 19c to MySQL 8.x – entirely on-premises – without disrupting live financial operations or losing a single record.
The project was completed with zero data loss, 100% data integrity, and measurable improvements across cost, performance, and system availability.
| 60%+ TCO reduction | 33% Faster query response | 45% Less maintenance overhead | 99.95% System uptime | Zero Data loss |
- Oracle licensing costs eliminated entirely – MySQL 8.x Community Edition is open-source
- Query response time cut from 1.8 seconds to 1.2 seconds
- System uptime improved from 98.5% to 99.95%
About SBI Factors Limited
SBI Factors Limited is a leading provider of factoring, bill discounting, and receivables management services in India. As a subsidiary of State Bank of India, the country’s largest public sector bank – the company operates under strict regulatory, compliance, and data governance requirements.
Headquartered in Mumbai, SBI Factors serves corporate clients across India, processing large volumes of financial transactions and sensitive customer data on a daily basis. The reliability, security, and performance of its database infrastructure are directly tied to its ability to serve clients and meet regulatory obligations.
The Challenge
SBI Factors Limited had relied on Oracle 19c for its core financial operations for years. While Oracle is a capable enterprise database, the setup had created four problems that were increasingly difficult to justify as the business grew.
1. High and Growing Licensing Costs
Oracle’s licensing model was proving expensive at the scale SBI Factors was operating. Recurring annual licensing fees represented a significant and rising cost with limited flexibility to negotiate or reduce. With the business growing, these costs were only going to increase.
2. Vendor Lock-In
Oracle’s proprietary ecosystem limited SBI Factors’ ability to integrate with open-source tools, modern data platforms, and cloud-native services. Every architectural decision had to work around Oracle’s constraints, slowing down technology adoption.
3. Specialist Resource Requirements
Managing Oracle database instances requires dedicated, specialist DBAs with Oracle-specific expertise. This created a dependency on a narrow pool of talent and added to operational overhead that could be avoided with a more accessible technology stack.
4. Scalability Constraints
Business growth was bringing increased data volumes and transaction loads. The existing Oracle setup was not positioned to scale efficiently, and expanding it would have meant further licensing and infrastructure investment.
The Solution
Teleglobal International conducted a comprehensive assessment of the existing Oracle 19c environment before any migration work began. This covered schema complexity and dependencies, stored procedures, triggers and functions, application compatibility across ERP, CRM, and internal finance applications, data volume, and network and security configurations.
Based on the assessment, Teleglobal developed a six-stage migration roadmap and executed it without disrupting SBI Factors’ live financial operations.
Migration Roadmap
| Phase | Key Activities |
| 1. Assessment and Discovery | Full audit of Oracle environment: schema, dependencies, stored procedures, data volumes, application integrations |
| 2. Schema Conversion | Oracle PL/SQL objects converted to MySQL syntax using migration workbench tools and manual optimisation |
| 3. Data Migration and Validation | Batch migration using MySQL Shell dump utilities with checksum-based validation to ensure 100% accuracy |
| 4. Application Repointing | JDBC/ODBC connectors updated and queries optimised for MySQL execution plans across all connected applications |
| 5. Performance Tuning | Indexing optimised, caching mechanisms introduced, buffer pool adjustments applied |
| 6. UAT and Production Rollout | Regression, performance, and failover tests run under production-simulated load; final cutover in a planned maintenance window with rollback plan in place |
Architecture
- Source: Oracle Database 19c (on-premises)
- Target: MySQL 8.x Community Edition (on-premises)
- High availability: MySQL Replication with failover configuration
- Backup strategy: Percona XtraBackup with snapshot-based retention
Tools Used
- Oracle SQL Developer Migration Workbench: schema conversion
- MySQL Workbench and MySQL Shell: target environment configuration and data migration
- Custom Python and Bash scripts: ETL processing and validation automation
Key Challenges and How They Were Solved
| Challenge | How Teleglobal Resolved It |
| PL/SQL to MySQL syntax incompatibility | Complex stored procedures rewritten using MySQL-compatible functions and logic, validated against expected outputs |
| Data type mismatches (NUMBER, CLOB etc.) | Oracle data types mapped to MySQL equivalents using documented transformation rules, validated post-migration |
| Performance after migration | Optimised indexing introduced, caching mechanisms configured, buffer pool settings tuned for MySQL’s query execution model |
| Minimising downtime during cutover | Parallel migration strategy with incremental syncs kept cutover window as short as possible |
| Data integrity assurance | Automated checksum and row-count validation ran at every stage – 100% data integrity confirmed before go-live |
Results
The migration delivered measurable improvements across every metric that SBI Factors cared about — cost, performance, reliability, and operational simplicity.
| Metric | Before (Oracle 19c) | After (MySQL 8.x) |
| Database licensing cost | Annual Oracle licensing fees | Zero – open-source |
| Average query response time | 1.8 seconds | 1.2 seconds (33% faster) |
| Maintenance overhead | High — specialist DBAs required | Reduced by 45% |
| System uptime | 98.5% | 99.95% |
| Scalability | Limited, high cost to expand | Easily scalable |
| Total cost of ownership | Baseline | Reduced by over 60% |
Additional outcomes:
- Full operational flexibility with an open-source database stack – no vendor lock-in
- Seamless transition for end users – no disruption to financial workflows during or after migration
- Foundation in place for future cloud migration or horizontal scaling
“Through strategic planning and technical expertise, Teleglobal International successfully executed a complex migration from Oracle 19c to MySQL for SBI Factors Limited. The project delivered measurable improvements in performance, cost savings, and scalability while ensuring compliance, security, and business continuity.”
— Teleglobal International
What’s Next
With a modern MySQL infrastructure in place, SBI Factors Limited is well positioned for the next stage of its technology evolution:
- Cloud migration readiness: the MySQL-on-premises environment provides a clear path to cloud database services if and when required
- Open-source ecosystem integration: freedom to adopt modern data tools, analytics platforms, and DevOps practices without Oracle compatibility constraints
- Continued performance optimisation: ongoing tuning of MySQL configuration as data volumes and transaction patterns evolve
- Responsible AI and data governance: a stable, well-documented database foundation makes future AI and analytics initiatives significantly easier to build