Tool Migration as Pedagogy
Moving a community from one digital platform to another is usually treated as an IT project. It's actually one of the best learning experiences you can design.
The reason: migration is authentic. It involves real documents, real communications, real decisions with real consequences. The friction people encounter — confusion about where files went, uncertainty about how encryption works, disagreement about who should administer the new system — isn't a problem to manage around. It's the curriculum.
What Migration Teaches That Workshops Don't
A workshop on privacy can explain zero-knowledge encryption. A migration makes someone experience the moment they realize that even the service provider can't read their documents. That experience lands differently.
The concepts that become real through migration:
Encryption and privacy — Zero-knowledge architecture stops being abstract when someone has to trust a system that, by design, can't read their files. Privacy by Design moves from principle to practice.
Decentralization and federation — Federated networks become tangible when learners understand why their Matrix account can communicate with accounts on other servers — and what control that gives them. This is Digital Sovereignty experienced, not described.
Cooperative economics — Shared infrastructure means shared governance. Who funds the server? Who decides what gets installed? These questions make civic participation concrete through a technical lens.
Authentic Assessment Built Into the Process
Migration projects generate real evidence of learning without requiring separate assessment design.
Portfolio documentation captures the decisions made along the way: What options did we consider? What problems did we hit? What did we choose and why? This is more revealing than any quiz.
Peer teaching emerges naturally. People who learn something first teach others — creating tutorials, leading small group sessions, troubleshooting alongside colleagues. That teaching deepens their own understanding.
Real-world application means the work has stakes. Moving actual documents, setting up actual secure communications for actual project work, participating in actual governance decisions — these are not simulations. The accountability is real.
The Productive Friction
Some friction in migration is inevitable. Some of it is also instructive.
When someone can't find a file they moved, that's an opportunity to talk about folder structures and naming conventions — and about what it means to own your own organizational system.
When a new tool feels unfamiliar, that's a moment to notice how quickly we confuse familiar with good — and how that confusion shapes our technology choices.
When a group disagrees about which tool to use or how to configure it, that's governance. Working through it together builds the same muscles that community organizations need for every other shared decision.
The goal isn't a frictionless migration. It's a migration where the friction is named and learned from.
Connections
- Teaching Digital Self-determination — The broader framework this practice serves
- Digital Tool Choice as Values Expression — Why the choice of what to migrate to is itself educational
- Tiered Technical Scaffolding Model — How to structure the migration so different skill levels can participate meaningfully
- Harm Reduction in Digital Literacy — Managing the difficulty and stress of transitions without abandoning the goal
- Teaching Philosophy — The pedagogical principles that make this approach coherent