Many schools have WiFi billing systems that are not new, but replace old ones that have been used for years. The old system may still run, but the manufacturers do not maintain it, keep up with new needs or with new unified identity certifications. Moving is more difficult than building them, because thousands of students' bills and numbers are running on them, and a wrong move is an educational accident.
Checking the real assets of old systems first
What is most appropriate before the move is to get a clear picture of what's in the old system: how many accounts, which are still in use, how billing rules are matched, whether there are historical bills to keep, interfaces and authentication. We have seen schools go directly into the new system, and we find that there is a special exemption account in the old system that has not been moved and that students are suddenly charged for their troubles. It is recommended that all data from the old system be first exported for inventory purposes, and that the studyer and financial check determine which ones should move, which should sell, and which rules should be retained.
The old one is parallel, not a single cut.
The most dangerous way to move is to turn off the old one night and open it. If there are problems with the new system, the entire school will not be able to access the net, and the fire will not come back in the middle of the night. The surest thing is a new and old parallel period: the new system will be connected first, a small number will be used, the account numbers, billings, reconciliations will be normal and expanded gradually. We suggest that the campus or dormitory will be changed by batches, each block for several days.
Account migration is for map and weighting.
The old system’s account and new systems often fail to match the fields. School numbers, names, rates, equipment bindings are all map sheets. More trouble is that duplicate accounts and zombie accounts have been stored for several years in the old system, which has become a risk when it moves. We suggest that one clean-up be done: double check-ups, deactivated school check-ups, unbundling unusual devices. Cleaning rules and learner confirmation.
History bills and logs to be checked.
Students may check the deductions six months ago, and the financials may be turned over last year. The historical bills cannot be lost when the old system is down. We suggest that the old system ' s billings and logs should be archived before moving, kept in searchable format, preferably to the query entrance of the new system or to an independent archive.
Toggle window selection
Even when a batch of shifts is cut, the time is chosen for each batch. Avoiding peak periods such as starting school, exams, and classes, we choose to do it on holiday or weekend nights. We suggest that students be informed before switching, indicating which period may be short-lived and lower expectations. The first days after switching are monitored by vendors and schools, confirming success rates and reconciliations. Half of the secret to smooth migration is prepared and half is right in timing.
Moving from old systems is essentially an engine with running operations. Taking stock of assets, new and old parallels, cleaning maps, slotting history, and selecting pairs of windows, these five steps allow the school WiFi to replace its online billing system without a sound, and teachers and students can hardly feel change. The highest point of migration is that no one sees you moving.
Give the students a clear message for the transition.
We suggest that you send a notice to the students before and after the transfer."System upgrades. Please report back to a certain entry point if you have access problems."And with the barrier. This is more secure than being bored, and students asking questions everywhere. No longer to inform."It could be a short-term anomaly. Where to?"Just be clear. Transparency can significantly reduce anxiety during migration and make the transport team less stressful.
The old system doesn't have to be out of line.
The old system suggests that it should be kept for some time, even if the new user is no longer in contact with them, and that data and configurations be retained. We have seen the old library cut after a week, so students can't check their bills for school hours, but they must collect their copies and make their hands at work. The old system retains a read-only filing period, for example three months, to prevent withdrawals and search.
I'll do one training and a baton after the migration.
The system is not cut to the school. We suggest that when the migration ends, the manufacturer provides a practical training to the information sector and dormitory managers: how to check accounts, how to handle common barriers, how to direct bills, how to configure rules. It would be better to leave a copy of the school's operating manual than the one used by the manufacturer."Success"The problem in the next few months is that no school actually operates a new system.