How to tell when it's time to change your coaching app
Move when the problem is structural: test-day crashes, leaks you can't trace, an app in the vendor's name, rising per-student costs or data you can't export. Fix the rest first, and time any move to admissions.
On this page 8 sections
- Fixable annoyances and real reasons to move
- A test that crashes when everyone logs in
- A leaked course you can't trace to an account
- Support that answers in days
- Whose name is on the app, and what data comes out
- Costs that grow faster than your institute
- Timing the move around admissions and exams
- Frequently asked questions
Change your coaching app when the problem is built into the platform or the contract. Crashes on test day, leaks you can't trace, an app in the vendor's name, climbing per-student fees and data you can't export all qualify. A slow support desk or a clumsy admin panel deserves a firm conversation first. Time any move to your admission cycle, not to the day you lose patience.
Fixable annoyances and real reasons to move
Most owners who call us about switching have two or three complaints mixed together. A vendor can fix some of them in a month if you push. Others come from how the platform is built or how the contract is written, and pushing won't change them. Sort yours first.
| What you're seeing | Try this first | It becomes a reason to move when |
|---|---|---|
| Tests or live classes crash at peak | Ask for a written incident report and a fix before the next test | It happens twice in a season, or the vendor blames students' internet |
| Lectures leak and you can't tell from whose account | Ask whether the platform can identify the account behind a leaked copy | It can't, and it won't accept protection added from outside |
| Support replies in days | Escalate to a named account manager and agree response times in writing | Login and payment failures still sit in a ticket queue after you escalate |
| The app is in the vendor's developer account | Ask for a written commitment to transfer the store listings if you leave | The vendor refuses, or ties the transfer to staying longer |
| Per-student or revenue-share costs keep rising | Renegotiate before renewal, with last year's numbers in hand | The terms won't move and a fixed fee would cost clearly less |
| You can't export your own data | Ask for a full export now, as a test | It arrives without payments, test attempts or original video files |
| The admin panel is clumsy or a feature is missing | Ask for a date, and train the staff who use it daily | Rarely, on its own |
Take that last row seriously. A move costs your operations team a term of attention, and some goodwill with students who have to learn a new app. Don't pay that for a missing report format.
A test that crashes when everyone logs in
Say you run an all-India JEE mock at 10 on a Sunday morning for 3,000 students. Nearly all of them open the paper in the same five minutes and submit just before 1 pm. That peak sits on your calendar weeks ahead, which makes it the most predictable load your platform will ever face.
So when a platform falls over at a scheduled peak, treat it as a design problem, not bad luck. Ask one question first: did students lose answers, or only time? If answers are saved as students go, a crash costs minutes and an extended window. If they aren't, it costs whole attempts, a delayed rank list and a lot of angry parents.
When 3,000 students in different cities fail in the same minute, the fault is on the server side, whatever the support team says about Wi-Fi. A vendor who sends a written account of what failed and what changed has earned another chance. A second crash in the same season settles it. Our note on scaling for exam-day traffic covers what a platform should do beforehand.
A leaked course you can't trace to an account
Suppose your full NEET crash course turns up on a Telegram channel a week after the batch started, sold for a fraction of your fee. You file takedown requests and the channel reappears under a new name. You still don't know which login the videos came from, so you can't block the account, warn the student or send a legal notice to anyone.
An anonymous leak repeats, because the account behind it is still active when the next course goes up. Section 65A of the Copyright Act, 1957 makes it an offence to circumvent an effective technological measure with the intention of infringing copyright. That is general information, not legal advice, and a complaint needs someone to name. Without the account, you have nobody.
Leaks alone don't always justify a migration. If your tests, payments and app work well, look at adding video protection to the platform you already have before you move. Move when the leaks come bundled with other problems on this list, or when your vendor won't allow protection from outside.
Support that answers in days
Judge support by its worst week, not its average. In the middle of admissions, a student pays but isn't added to his batch. He messages every hour and his father calls the front desk. A vendor reply in three days loses that admission.
Before you decide, keep a log for a month. Note the date, the problem, how many students it hit, the time to the first human reply and the time to a fix. Take it to the vendor's management and ask for written response times, faster for login and payment failures than for feature requests. Support often improves once someone senior sees the log. If it doesn't, the log is your evidence when you give notice.
Whose name is on the app, and what data comes out
Open your app's App Store page and look at the developer name, and at the Provider line in the Information section. Apple says it displays the enrolled organisation's name as the seller. On Google Play, check the developer name under the app's title. If either shows your vendor's company, the listing, its ratings and its reviews sit in their account, not yours.
Apple's App Review Guidelines (4.2.6) say apps made from a commercial template or app-generation service will be rejected unless the content provider submits them directly. That is one reason a branded coaching app belongs in the institute's own developer account. Both stores allow transfers, and the current account holder has to start one. On Google Play, users, ratings and reviews move with the app. On the App Store, the app keeps its ratings and reviews, and users keep receiving updates. If your vendor won't start the transfer, you publish a new app and every student installs it again.
Get a transfer commitment in writing while you are still paying. Then start on your own developer accounts, because they take time. Organisation accounts on both stores need a D-U-N-S number. A new personal Google Play account must also run a closed test with at least 12 testers for 14 days in a row before it can publish.
Next, ask for a full export today, as if you were leaving. You need students with phone numbers, enrolments with expiry dates, payments with gateway transaction IDs, test attempts at question level and your original video files. Open the files and check that Hindi text survived and every expiry date is there. If the answer is that you'll get everything when you leave, treat it as a no.
Original videos go missing most often, because some platforms keep only the copies prepared for streaming. Keep your own lecture files on drives. The guide to migrating courses, videos and student data covers what to do if you didn't.
Costs that grow faster than your institute
Revenue share looks harmless in the first year, when sales are small. Take an institute selling ₹2 crore of courses a year on terms that keep 10 per cent. That is ₹20 lakh a year before gateway charges. It rises every time you add a batch, or raise fees to pay a new physics faculty. (These figures are an example, not anyone's actual terms.)
Per-student pricing has its own trap. If you pay for every active student, a two-year JEE course counts against you for two years. So does every past student you leave with access to revision material. Cut that access to save money and you annoy exactly the students most likely to send you referrals.
Renegotiate before you think about moving. Vendors rarely change terms mid-contract, but renewal is a different conversation, especially with another quote on the table. Read your notice period now so the renewal date doesn't pass in silence. Our guide to an LMS without revenue sharing shows how to compare a fixed fee with a share on your own numbers.
Timing the move around admissions and exams
Move with a new batch, never with one close to its exam. A JEE or NEET institute should leave its Class 12 and dropper batches alone from December until the exams are over. Moving 2,000 students to a new app three weeks before JEE Main costs more than any saving it brings.
Leave slack, too, because exam dates move. In 2026 NEET UG was held on 3 May, and NTA then held a re-examination on 21 June. An institute that had booked late May for its switch would have switched apps in the middle of an unplanned revision month.
The cleaner route is to put new admissions on the new platform from their first day and let outgoing batches finish where they started. You pay for two platforms for a few months, and no student in an exam year has to change apps. A UPSC institute can do the same with foundation batches that start after Prelims, keeping its Mains test series on the old platform until it ends.
Counting back from your next batch's start date, we would go in this order.
- Four months out, read the notice period, request the full export and get the app transfer answer in writing.
- Three months out, open developer accounts and a payment gateway in your institute's own name.
- Two months out, run a pilot with one small batch, such as a crash course or a scholarship test.
- Six weeks out, move the admissions page and payment links, and test a real payment and a refund.
- On the start date, launch the new batch on the new app and leave older batches where they are.
- After the last old batch sits its exam, take a final export, archive the records and close the old account.
The guide to migrating a coaching institute to a new LMS covers each of these steps in more detail.
Before you sign with anyone, settle the two hardest signs on this list: whose name the app is in, and whether a leak can be traced. On Upclass, your app is a branded app in your institute's own name on Android, iOS, Windows and Mac. VidSafe adds visible and invisible watermarks that are extremely hard to remove, even after heavy re-encoding, so a leaked copy can be traced back to the account it came from. Book a demo, and bring your support log and last export.
Frequently asked questions
Will students lose the app when we change platforms?
Not if the app sits in your own developer accounts, or your old vendor transfers it there. The new platform then updates the same listing. If the vendor keeps the listing, everyone installs a new app, so switch at the start of a batch.
Can I change coaching apps in the middle of a batch?
Yes, but not for a batch within a few months of its exam, where one login problem during a mock series costs more than the move saves. Start new admissions on the new platform and let current batches finish.
What should I ask for before telling my vendor I'm leaving?
A full data export, your original video files and a written answer on transferring the app listings. Ask while you are still a paying customer and the relationship is friendly, and check your notice period too.
Is revenue share cheaper than a fixed fee for a small institute?
Only while sales are small, which suits a teacher testing a first course. Once sales are steady, work out last year's share in rupees and compare it with a fixed fee plus your own gateway charges.
