The old ones either don't support the new deal, or the manufacturer doesn't defend it. But the worst thing about the replacement is that they are downline, they can't get online, and complaints are 10 times better than new functions. We have changed schools, Portal, with a core of words: it is a phased project, not a weekend move.
Why did you change your place?
The old system does not support new certification agreements, new terminals and access are out of reach; the manufacturer stops maintenance, there is no one to fill in the gaps; and performance is not keeping up with the current per capita multi-end. These are hard reasons, more convincing than simple systems. We write the commercial and technical arguments for replacements, and approval and collaboration are smoother.
Run in parallel, not one cut.
The surest thing is that the two old and new sets of systems coexist, gradually cut off, never switch to a single school. We usually let the new system run real traffic on the sidewalk for verification, confirming that transmission and authentication are correct and proportional. Any one side of the equation can quickly cut back the flow.
Data Migration Prior
Old accounts, bill balances, and strategy configurations are the most easy places to turn. We ask that data be moved to new systems without rushing into it, first using historical data for a round of checks: right account numbers, accurate balance, effective strategy. By then, the validation is done to avoid students finding smaller balances or misdirection on-line.
Greyscale Cutting
The test is no problem, and not the whole school pushes. We usually pick a building that has a grayness, runs for one week, then spreads to one and finally to the entire school. The greyness limits the unknown to a small extent. The real impact of the situation is a building rather than a full campus, with both processing and rolling around. This is an urgent step, taking two weeks to the ground, saving countless complaints.
The rollback plan is a necessity.
The new system is in trouble, so that you can return to the old system with one key and rollbacks without any sense on the part of the users. We must have practiced the scrolling script and steps before we get online, making sure it's cut back within a few minutes. No rollback options are replaced by a whole school Internet, and we don't do it.
Oscillation
The upgrades themselves are placed in the holidays or late nights, avoiding late peaks and school starts. We usually switch from a low-peak window like Friday night to Saturday morning, even if it is a little shaken, with the least of those affected. The wrong window of time is also abused.
Closing of reconciliations
After the new system has stabilized, it is necessary to perform a full reconciliation: balances when the old system was frozen, amounts transferred, receipts and disbursements during the operation of the new system, three pairs. We suggest that reconciliation reports be issued every day during the first week after the replacement, confirming that there are no missing students' balances and no duplicate bills. The reconciliation will take place before the replacement is actually closed.
User communication is inevitable.
We usually get a short notice from the school that students and teachers may have short fluctuations at some point, with the account number unchanged. Communication is done, even if there is a little Caton, and users understand; without communication, a little volatility is a complaint.
Shut up: Change is a project, not an action.
The old system doesn't have to get off the line.
Many people change the first thing about old systems, which is a big taboo. We suggest that the old system should have at least one costing cycle back-up and be able to match it in parallel with the new system, confirming that the new system accounts and data are stable.
The manufacturer must be fully connected.
The change is often accompanied by a change of firm, newer than the old environment and the failure to transfer. We want the old system architecture, account logic, historical pit points to be written into a handover document, signed by the new manufacturer. This file saves many more time from retortion and error than the exemption clause in the contract.
Give the teacher and student a feedback portal.
The first two weeks of the change, the problem is most likely to arise. We suggest that schools open a temporary feedback portal where students and teachers can report anomalies directly and network centres and manufacturers can watch together. Feedback channels are easy, minor problems are solved on the day, there will be no large complaints, and the replacement of slogans is better.
The rhythm of the replacement project is important, not to be carried by the company’s deadline. We advocate that schools should schedule their own school cycles so as to avoid the test months and start seasons and place them in the most idle window.
In conclusion: Portal changes are made in a way that is not disturbing, and relies on seven steps: parallel, migration verification, greyscale, rollback, faulty peaks, reconciliation, communication. It is managed as a phased, pre-planned project, rather than a weekend action, to make the transition smooth.