In the final days of term, Samira opens a group project one more time. Her class spent months building a local-history exhibit: recorded memories from neighbours, scanned photographs, short captions and a map that changed after every discussion. The school is moving to a different digital platform over the summer. Samira can download the images, but she cannot tell whether the teachers' feedback, the earlier drafts or the permissions attached to the recordings will still make sense outside the old account. What she is trying to save is not simply a folder. She is trying to keep hold of a piece of school life that has been shaped by other people.
That distinction matters. Digital platforms make it easy to treat learning as a stream of items: uploads, comments, notifications and completed tasks. Yet a school project is more than its final file. It includes the questions that changed it, the explanations that helped a student persist and the agreements that made collaboration possible. When a platform is replaced, those relationships can become invisible even if some documents remain. A photograph without its caption, a piece of feedback without the draft it refers to, or a shared document stripped of its versions may be technically preserved while educationally diminished.
Schools have good reasons to change tools. A service may become unaffordable, inaccessible, poorly supported or unsuitable for the work a community wants to do. Treating every platform change as a failure would be unhelpful. The difficulty lies elsewhere: in assuming that a new login is the same thing as continuity. It is not. Continuity has to be planned around the people who learned, taught and communicated through the departing system. Before a school turns off an old platform, it should ask what students and families need in order to understand where their work has gone and how their relationships with the school will continue.
A download is not automatically a memory#
Samira might receive a compressed folder containing every image from the exhibit. That would be better than receiving nothing, but it could still leave her with a puzzle. Which recording did her group finally choose? Why did they remove a label that seemed important at first? Which version of the map reflects the discussion with a neighbour who corrected a street name? Learning is often carried by these connections. If the change process preserves only isolated outputs, it tells students that the visible product matters while the path towards it is disposable.
Samira might receive a compressed folder containing every image from the exhibit.
A more careful approach starts by asking students what they would want to recognise later. The answer will vary. One student may care about a teacher's annotated draft because it reveals a new way of writing. Another may value an audio recording that captures a family story. Someone else may only need a clear copy of their final work. There is no need to make every child create a perfect personal archive. The point is to recognise that the people who made the work can identify what gives it meaning. Their knowledge belongs in the planning of a transition.
Families need the same respect. School platforms often contain a mixture of routine notices, meeting notes, consent forms and messages that matter at very different moments. Asking every household to reconstruct that mixture after an account closes is neither efficient nor fair. A clear transition should say what will remain available, what will be sent directly, when access will end and where help can be requested. This is not merely a customer-service detail. It is part of a school's responsibility to make its communication understandable to people with different schedules, devices and confidence levels.
Care also requires limits. Preserving school life does not mean copying every conversation indefinitely. A student's portfolio, private professional notes and a sensitive exchange between adults cannot all be handled as though they belong in one export. The school needs to distinguish what a learner should take with them, what it must retain for institutional reasons, and what should be protected or removed according to its purpose. This distinction is not an obstacle to continuity. It is what makes continuity respectful rather than a form of indiscriminate accumulation.
Test the journey from an ordinary user's seat#
The most revealing migration test is rarely performed by the person who configured the system. That person knows where folders live, which labels are temporary and what an error message is supposed to mean. A student opening a file from a shared phone, a parent looking for a meeting agreement after work, or a teacher trying to recover a class project at the start of term sees a different system. Their experience should be invited into the process before the old platform disappears.
Samira's school could select a few real projects and ask volunteers to follow a simple path. Can they find the material they expect? Can they open it without a specialist application? Can they tell what has been lost or changed? Can they identify a person to contact when something is missing? These are not tests of whether participants are sufficiently skilled. They are tests of whether the transition has been explained and designed well enough. When several people stumble in the same place, the appropriate response is to repair the route, not to blame the walkers.
Such testing can uncover small but consequential problems. A folder name may make sense to administrators but not to a family. An interactive activity may need a readable alternative. The instructions may say how to sign in but not what to do when a student no longer has the same device. None of these issues is glamorous, and they can be easy to postpone while a project plan focuses on deadlines. Together, however, they determine whether the new platform expands participation or quietly creates a new group of people who must ask for help with every basic task.
Testing also creates room for honesty. Some features will not travel unchanged. A discussion thread may lose its layout; an embedded activity may no longer run; a version history may need to be represented in a simpler form. Naming these limits early gives people choices. They can decide what to save, request support or adjust their expectations. Pretending that the move will be seamless converts a foreseeable limitation into a personal disappointment. Trust grows more readily from a school that explains an imperfection and offers a route through it than from one that promises more than it can sustain.
Independence needs institutional support#
Digital dependence is not always obvious while a platform is working. It becomes visible when an account expires, a family changes schools, a device fails or a supplier changes its terms. If a student can no longer open work they created without maintaining access to a particular commercial space, the school has made part of their learning contingent on a door they do not control. This does not mean that schools should reject all online tools. It means they should treat the possibility of leaving as one of the conditions of using a tool responsibly.
Students should not be expected to solve that problem by themselves. It would be unfair to turn platform literacy into another hidden requirement for participation. The school has the main responsibility to choose workable formats, define a sensible process and offer help. It can still make autonomy a shared practice. At the end of a project, a class might choose one version to keep, write a sentence explaining how it can be opened, and ask another group to see whether the materials make sense. This is not training in system administration. It is an invitation to treat one's work as something worth carrying forward.
Teachers need time to support that work. A transition plan that simply adds file organisation, family questions and troubleshooting to existing workloads does not create resilience; it borrows it from staff goodwill. Schools should identify who is responsible for exports, who responds to access problems and who makes decisions when a particular type of information does not fit the general rule. They should also give those people time. Otherwise the burden tends to land on the most available teacher or on the family most able to persist, which deepens rather than reduces inequality.
The same principle should shape procurement. Before adopting a service, a school can ask how materials leave it, which file types are produced, what happens after a contract ends and what support is available during a transition. These are not hostile questions. They are signs that the school understands a platform as a tool rather than a destination. A service that helps people enter, use and leave it with clarity is more compatible with education than one that makes departure confusing or costly.
Sorting is a form of care#
Faced with the prospect of loss, it is tempting to keep everything. Yet an enormous archive with cryptic names and no structure can be as unusable as an empty one. The move to a new platform can be an opportunity to decide what deserves attention. Which materials help a student explain their development? Which records does the school need for its own responsibilities? Which temporary messages have already done their job? These questions take time because selection is an act of judgment, not a mechanical cleanup.
For Samira, a meaningful small archive might include the final map, an earlier draft with a teacher's comment that changed the project, and one recording whose contributor agreed that it could be kept. She might write a short note explaining the connection between them. That set would not preserve every second of the project, but it would preserve a route through it. The exercise could help her see that a finished exhibit did not simply appear; it emerged from revisions, choices and conversations. In that sense, archiving can itself become part of learning.
The school can make this possible with a short, practical guide rather than a maze of technical instructions. It should tell students what they will receive, tell families what they can request, state what the school will retain, and provide a clear contact route for missing material. It should also recognise different circumstances. Some people use shared devices, need language support, have limited connectivity or learn about the change later than others. A process that works only for households with spare time and technical confidence is not yet a fair process.
Where it is feasible and safe, a limited overlap between old and new systems offers a valuable safeguard. The point is not to maintain two platforms forever or to double every task. It is to create enough time to discover that an export lacks a crucial item, that a message was misunderstood or that a group cannot find its work. Administrative calendars often reward fast closure. Educational care sometimes requires a pause that prevents a temporary oversight from becoming a permanent loss.
A school should be able to leave well#
Years later, Samira may not remember the name of the platform that hosted the exhibit. She may remember the neighbour who challenged the class's version of a local story, the uncertainty of editing an interview, and the satisfaction of making the map clearer together. If she can open a few chosen materials and understand their place in that story, the technology will have served its purpose quietly. It will not have asked to be remembered. It will simply have avoided placing a barrier between a learner and her own work.
Changing platforms without losing school life means preparing that kind of departure. It means treating access, explanation and support as educational obligations rather than emergency fixes. It means being candid about limits, letting users reveal where the process is unclear, and refusing to make personal persistence the price of retrieving a school memory. None of this prevents innovation. It makes innovation answerable to the people whose time, attention and learning give a platform its value.
Before celebrating the next system, a school can ask one grounding question: when this one is eventually replaced, will the people who learned here be able to recognise and carry forward what matters? Asking early changes the criteria for success. It moves the focus from a platform's impressive first-day features to its capacity to support a community over time. That is how technology remains in its proper role: not the owner of school life, but one of the means through which school life can continue.
