What happened
BSNL, India's state-run telecom operator, sought to cancel the purchase order it had issued to Mumbai-based RedMango Analytics after the vendor failed to meet the contractual milestones for migrating the BSNL Selfcare app — the operator's unified dashboard for recharges, bill payments, plan purchases, service management, DND settings and complaints. Payment was explicitly linked to milestones: successful completion of Acceptance Testing first, then commissioning of the new system and migration of existing data from the legacy system.
The timing was unforgiving. Digitral, the incumbent Selfcare app provider, ceased services on September 30, 2026, putting nearly 6 million users due to move onto RedMango's new platform. RedMango ran no version update or forced update to carry existing users across; when the old app died, one-time passwords needed to log into the new app queued up, leaving subscribers high and dry. Sources cited by ETTelecom put the number actually migrated at about 500,000.
BSNL's letter to RedMango observed that invoices had been submitted without the requisite AT certificate or documentary evidence from BSNL confirming commissioning and successful data migration, and asked the vendor to cancel the invoices — to avoid GST accounting issues — and resubmit only after fulfilling the applicable milestones. BSNL had flagged the shutdown to users only through a soft banner recommending migration to the new application.
What it cost
Of ~6 million users due to migrate, only about 500,000 moved; subscribers queued for OTPs with no working app; BSNL moved to cancel the purchase order.
Why it happened
Invoices went out without the acceptance-testing certificate or evidence of commissioning and data migration the PO required.
No version update or forced update was run, so existing users had no path onto the new app.
The deadline was immovable — the old provider ceased service September 30 — so slippage stranded users immediately.
Only a soft banner preceded shutdown, leaving the hard migration work to a vendor that didn't do it.
The lesson
When a legacy system is dying on a fixed date, the migration vendor's job is a forced update in users' hands — not a platform waiting to be found.
Aftermath
BSNL asked RedMango to cancel its invoices and resubmit only after meeting milestones; by publication only about 500,000 of nearly 6 million users had moved. RedMango did not respond to queries, and BSNL is moving to a new Selfcare app vendor.
FOLLOW THE EVIDENCE
The sources
- BSNL seeks to cancel RedMango PO due to non-fulfillment of contractual milestones telecom.economictimes.indiatimes.com