Sooner or later, many ISPs want to change their bandwidth management software. The current system may be too costly, missing features, poorly supported, or simply not keeping up with growth. But the switch is risky. Customer data, KYC records, plans, apps and billing are often tied to the old system, so changing it can mean weeks of rework and confused customers.
There is a better way to set things up: keep your customer-facing systems separate from the bandwidth software underneath. This guide explains how that works and how to plan a switch without disruption.
Why switching bandwidth software is hard
When billing, customer records and the subscriber app all live inside the bandwidth management software, changing it affects everything at once:
- Customer data has to be exported and re-imported, often in a different format
- KYC and CAF documents may need to be collected again
- The subscriber app changes, so customers must download and learn a new one
- Plans and prices have to be recreated, with a risk of errors
- Staff must learn new screens for billing, complaints and reports
- Renewals and payments can be missed during the changeover
For a growing ISP, that is a lot of risk for a change that should be technical.
The front-end and back-end approach
The way to reduce this risk is to split your systems into two layers:
| Layer | What it does | Changes when you switch bandwidth software? |
|---|---|---|
| Front end: CRM and billing platform | customer records, KYC, plans, invoices, payments, complaints, subscriber app, reports | No |
| Back end: bandwidth management / RADIUS | authentication, speed control, sessions, usage | Yes |
The front end talks to the back end through an API. When you replace the bandwidth software, you connect the same front end to the new system. Customers, staff and data stay where they are.
What stays the same when you switch
With ISPMate as the front end:
- KYC and CAF records stay in ISPMate, so there is no need to collect documents again
- The customer app and portal stay the same; subscribers keep recharging and raising tickets as before. See the ISP customer portal
- Plans, billing and payment history remain unchanged
- Complaint history and customer interactions are preserved
- Your team keeps working on the screens they already know
Only the connection between ISPMate and the network changes.
How to plan the switch
1. Audit your current setup
List every plan, speed profile, NAS/router and the number of active subscribers. Note which data currently lives only in the old bandwidth software.
2. Move customer-facing data to the front end first
If you aren’t already using a separate CRM and billing platform, move customer records, KYC, plans and billing there first, while the old bandwidth software is still running.
3. Map plans to the new system
Create the same speed profiles in the new bandwidth software and map each billing plan to its profile.
4. Connect the front end to the new system
Set up the API or RADIUS connection between your CRM/billing platform and the new bandwidth software.
5. Test with a few accounts
Move a handful of internal or test users first. Check login, speed, expiry, renewal and suspension.
6. Move subscribers in batches
Shift subscribers area by area or in small batches, and watch complaint volume after each batch.
7. Keep the old system for a short overlap
Don’t switch the old system off until every subscriber is confirmed working on the new one.
Switching checklist
- All plans and speed profiles recreated in the new system
- Front end connected to the new bandwidth software and tested
- Test accounts pass login, speed, expiry and renewal checks
- Subscribers moved in batches with complaints monitored
- Support team briefed on what customers might notice
- Old system kept running until the move is complete
Common mistakes
- Switching everything in one night with no test batch
- Recreating plans by hand without checking speeds and prices
- Asking customers to install a new app during the switch
- Re-collecting KYC because documents were stored only in the old system
- Turning off the old system before all users are confirmed online
Which bandwidth management systems work with ISPMate?
ISPMate integrates with popular bandwidth management and RADIUS systems used by Indian ISPs, including Jaze, IPACCT, Height8, DMA, XceedNet and 24online, as well as MikroTik routers. Read more about how RADIUS works for ISPs.
Frequently asked questions
Yes, if your KYC and customer records are stored in a separate CRM and billing platform such as ISPMate. Only the network connection changes; the documents stay where they are.
Not if the subscriber app belongs to your front-end platform. With ISPMate, customers keep using the same app and portal after the switch.
It depends on the number of subscribers and plans. Moving users in batches with a short overlap period usually keeps the switch safe and smooth.
ISPMate works with systems such as Jaze, IPACCT, Height8, DMA, XceedNet and 24online, and with MikroTik routers.
Plan your switch with our team
Our team can help you move customer data, KYC and billing into ISPMate and connect it to your new bandwidth management system, so your subscribers don’t notice the change. Book a free demo: call +91-9310313545 or write to sales@ispmate.com.
