I'm a new sysadmin at a small company with around 30 employees, and my boss wants us to move from Windows to Linux. Most employees mainly work in a web browser, but they also need email, shared files, and collaborative document editing similar to Microsoft 365. I'm considering Ubuntu for the desktops because it's the distribution I know best, along with FreeIPA and Ansible for identity and configuration management. I'm also looking at Nextcloud with Collabora for file sharing and online document collaboration. Does this sound like a sensible approach? What distributions, endpoint-management tools, and collaboration platforms would you recommend?
4 Answers
Nextcloud with Collabora can provide shared storage and browser-based document editing, but running it professionally means you own the backups, upgrades, authentication, storage, monitoring, failover, and troubleshooting. A hosted productivity suite may be a better fit if you do not want to run email and collaboration infrastructure yourself. Whichever route you choose, verify spreadsheet features, external sharing, permissions, retention requirements, and compatibility with files received from customers and suppliers.
FreeIPA and Ansible can work, but Ansible alone is not a complete laptop-management platform when devices leave the office or have changing network addresses. You’ll want something that can check in remotely, handle patching, run configuration tasks, report device status, and support remote troubleshooting. Test your identity provider, device enrollment, backups, recovery process, and security monitoring before deployment. For a small team, paying for an established management or support service may be cheaper than building and maintaining every component yourself.
If the users truly only need a browser, managed Chromebooks or ChromeOS Flex are worth comparing. They’re less flexible than a full Linux desktop, but centralized management and recovery are much simpler.
Ubuntu LTS is a reasonable choice, especially since you already know how to administer it. In a small organization, familiarity, long-term support, hardware compatibility, and commercial support matter more than finding the theoretically perfect distribution. Start by documenting every user workflow and application, then pilot the setup with a few people from different roles. Test printers, VPN access, video calls, authentication, peripherals, accounting tools, and document compatibility before committing to a full rollout.
I’d keep the desktop environment consistent too. KDE Plasma may feel more familiar to Windows users than a radically different layout, but the important thing is choosing one standard you can support.
The bigger question is whether the migration solves a real business problem. Avoid treating the operating system license as the whole cost: training, lost productivity, troubleshooting, endpoint management, security tooling, support contracts, and replacing incompatible software can easily exceed the savings. If the goal is data sovereignty or reducing dependence on a vendor, that can be a valid strategic decision, but it should be approved and budgeted as a major project rather than a quick cost-cutting exercise.
A good migration sequence is to change the applications and workflows first while everyone is still on Windows. Once browser-based services, file storage, collaboration, and remote support are proven, changing the operating system becomes much less disruptive.
Don’t make the desktop migration, email migration, file-platform migration, and identity redesign happen all at once. Break them into stages with a rollback plan and a small pilot group.