Clean last season’s data
Gather the enquiry sheets, portal exports and registers you want to keep. Remove obvious duplicates, agree what each column means and decide what is too old to bring across.
Blog · Admissions
Education CRM implementation is the work of moving an admission team from registers, sheets and personal phones onto one shared system, with clean data, clear roles and a team that trusts it. Done well, it happens in a planned sequence before the season peaks, so live enquiries keep moving while the new system takes over.
Before You Start
Most rollouts that struggle do so because of decisions nobody made before the software arrived. The system will hold whatever you put into it and follow whatever rules you give it, so the preparation is mostly about agreeing those rules.
If you are still deciding whether you need a CRM at all, start with what an education CRM is. If you are choosing between options, our guide on how to choose the best education CRM in India covers the buying side. This article assumes the decision is made.
Gather the enquiry sheets, portal exports and registers you want to keep. Remove obvious duplicates, agree what each column means and decide what is too old to bring across.
Write down the stages an enquiry moves through, from new to enrolled, and what has to happen for it to move. Everyone should use the same words for the same step.
Decide who handles enquiries, who counsels, who approves concessions and who sees reports. Each role should see what it needs and nothing more.
Decide how a new enquiry finds its counsellor: by programme, campus, language or load. A rule written as a sentence is easier to set up and to explain.
Agree one name for each portal, campaign, event, walk-in and referral source, so reports are not split across several spellings of the same thing.
One person should own the rollout, make decisions quickly and be the first point of contact for the team. Without an owner, small questions stall the whole plan.
The Rollout Plan
The order matters more than the speed. Each step builds on the one before, and skipping ahead usually means coming back later.
Configure the stages, roles, assignment rules and source list you agreed. Test them with a handful of made-up enquiries before any real data goes in.
Bring in open enquiries with their source, owner, stage and history. Check a sample by hand against the old sheet before you trust the import.
Connect website forms, WhatsApp, portal leads and the phone line one by one, and confirm each creates a record with the right source.
Show counsellors their daily list, the front desk the enquiry form and heads the reports. Each person needs to know their own job in the system, not every screen.
For a short, fixed period, new enquiries go into the CRM while the old sheet stays available to read. Set an end date and keep it.
Switch over early in the week and away from a result day or a big event, so problems surface when there is time to fix them.
Check unassigned enquiries, duplicates and overdue follow-ups every day. Fix rules quickly while the team is still forming habits.
Once the team works from the CRM every day, archive the sheets and personal lists. Two sources of truth quietly become none.
Going Live
The risk in any rollout is the enquiry that falls between the old system and the new one. A few simple rules prevent it.
From the go-live date nobody adds new enquiries to the old sheet. It stays available to read, so history is never lost, but new work happens in one place.
Import enquiries that are still in progress before closed ones, with their next step and date, so no follow-up is missed on the first morning.
An enquiry should keep its counsellor through the switch. A family should never notice that the institution changed its software.
Common Mistakes
Most rollout problems are predictable. These are the ones admission teams run into most often.
Switching systems when enquiries are at their highest leaves no time to learn. Aim to be settled before the busy weeks begin.
Old, closed and duplicate records clutter the new system from day one. Bring across what the team will actually use.
People forget a long demo. Short, role-based sessions followed by a few days of support work far better.
If the sheet stays open for editing, half the team will keep using it and the reports will never agree.
Every extra field is something a busy counsellor has to fill in. Start lean and add only what someone will use.
Rules drift, new programmes appear and staff change. Someone has to keep the setup current after launch.
In CampusFlow
Every step above applies whichever system you choose. The difference a purpose-built tool makes is how much of the setup and import work is done for you. The points below describe what CampusFlow gives you to work with, and the full range is on our product pages.
How the same approach looks for a school, a college, a university or a coaching institute is on our solutions by institution type, and what each plan includes is on the pricing page.
Our onboarding team imports your existing leads, sources, counsellor assignments and follow-up history, de-duplicates them and trains your team, so you start the season with a clean, complete pipeline.
Calls, website forms, WhatsApp, walk-ins at the desk, education portals, referrals, paid campaigns, event QR codes and bulk imports all land in one inbox with the source preserved.
Assignment rules by programme, campus, city, language or counsellor load place every enquiry within seconds.
The Today list shows calls due, campus visits booked and overdue follow-ups, sorted by score and deadline. More on our counsellor workspace page.
When a counsellor is away, their due calls, visits and follow-ups move to a chosen colleague or the team pool with the full history attached, and move back when they return.
Access is role-based. Counsellors see their own numbers, heads see their teams, finance sees fees and the principal sees everything.
To see your own enquiry sheet imported, assigned and on a counsellor’s Today list, book a 30-minute demo.
FAQs
Prepare first, then roll out in a fixed order. Agree your stages, roles, assignment rules and source names, and clean the data you want to keep. Then configure the system, import open enquiries, connect your channels one at a time, train each role on its own tasks and go live on a quiet day. Review daily for the first weeks and retire the old sheets once the team works from the CRM.
It depends more on how much data you bring across, how many channels you connect and how quickly decisions get made than on the software itself. Agreeing stages, roles and rules is often the slowest part. Plan to finish well before the season peaks rather than to a fixed number of days, and allow time for a short settling-in period after go-live.
Train by role. Counsellors need their daily list, the enquiry record and how to log a call and set the next step. The front desk needs the enquiry form and the duplicate check. Heads need the reports. Keep sessions short, use your own enquiries rather than demo data and make one person available to answer questions for the first few days.
Start with the enquiries that are still open. Export them with their source, counsellor, stage, last contact and next step, remove duplicates and agree what each column maps to. Import a small sample first and check it against the old sheet by hand before importing the rest. Closed enquiries from past seasons can follow later or stay archived if nobody will use them.
Going live in the middle of the peak, importing every old record, training everyone in one long session, leaving the old sheet open for editing, adding too many fields and stages and having nobody own the setup after launch. Each one is avoidable with a little planning before the switch.
Only briefly, and only with the old system read-only. New enquiries should go into the CRM from day one while the old sheet stays available for reference. Running two live systems for long splits the team and the numbers.
One named person with the authority to make decisions, usually from the admission team rather than IT. They agree the rules, answer questions, check the data in the first weeks and keep the setup current as programmes, staff and sources change.
Bring last season’s enquiry sheet to the demo. We will show you how it is imported, how enquiries are assigned and what each counsellor sees on the first morning.