Over the years I have read many accounts of migrations large and small. They big guys tend to be very cautious because any disruption is huge. This is what Canonical says about how to go about it:
- Plan effectively for maximum effect
- Target the users ripe for migration
- Identify the apps that save you money and fuss
- Create the right management flows
- Pilot your project to get it just right
That’s not too different from what
While a perfectly planned set-piece migration appears to work for large organizations, smaller organizations may simply experience delay and greater costs doing the detailed work. The GNU/Linux desktop has evolved to the point where for a large proportion of users it can do the job with little fuss. Just backup data, install the OS and restore the data. If any problems arise they are likely to be small and manageable. With a good backup, one can always revert particular machines if a show-stopper arises. In ten years of migrating small organizations I never encountered a show-stopper that could not be simply worked around. Migrations of simple computer labs may take only an hour or two. A whole school may be about as complicated as that. Where I last worked, I walked around replacing PCs with GNU/Linux PCs. I could have installed over the network to avoid the walking but there was a matter of locked doors after hours… That’s not a show-stopper associated with the OS, just constraints on the institution.