Open-source software is software whose source code is public and which you can usually use without licence fees. Linux, LibreOffice, Firefox, Thunderbird, Nextcloud and Bitwarden are well-known examples. For many small businesses, schools and non-profits, it can cut costs and give more control over data. But "free" is not the whole story, and it isn't the right fit for every task.

These are the questions I go through with organisations before recommending a move.

1. What do you pay for today, and why?

List the software you pay for: office suites, email, file storage, design tools, accounting, remote access. Next to each, note what it costs per year, how many people use it, and which features you actually rely on.

You'll often find a mix: some tools are essential and hard to replace, and others are paid for out of habit and could be swapped easily.

2. Does it work with the people you exchange files with?

Compatibility is the most common practical problem. Check:

  • File formats you receive and send (for example complex Word or Excel files with macros)
  • Industry software that only runs on Windows or macOS
  • Systems required by customers, suppliers, authorities or your accountant

Open source doesn't have to be all or nothing. Many organisations keep one or two specialised tools and move everything else.

3. What does it really cost?

The licence may be free, but there are other costs:

  • Setup and migration work
  • Training and a period of getting used to new tools
  • Hosting, if you run services such as file sharing yourself
  • Ongoing maintenance: updates, backups and monitoring

Compare the total over three to five years, not just the first year. For many small organisations it still comes out cheaper, especially as subscription prices keep rising. But the decision should rest on numbers you have checked.

4. Who will support it?

Popular open-source projects have large communities, good documentation and regular security updates. Less well-known ones may depend on a handful of volunteers. Prefer tools that are:

  • actively maintained, with recent releases,
  • widely used, so help is easy to find, and
  • available with paid support if you need it.

You also need someone who looks after your setup, whether that's someone on your team or an external IT partner.

5. Who owns your data?

This is often the strongest argument for open source. With open formats and self-hosted or EU-hosted services:

  • your data isn't locked into one vendor's format,
  • you decide where it is stored, and
  • you can switch providers without losing access.

If data protection and where data lives matter to your organisation, this weighs a lot.

6. How do you move without disrupting work?

A careful migration goes step by step:

  1. Review what you use today and pick the first candidates.
  2. Pilot with a small group, on real work, for a few weeks.
  3. Keep a way back: the old system stays available until the new one has proven itself.
  4. Train and document: short guides for the tasks people do every day.
  5. Roll out to everyone, then retire the old tools.

Changing everything in one weekend is how migrations fail.

Quick self-check

Open source is probably a good fit if:

  • Licence and subscription costs are a noticeable part of your budget
  • Most of your work is documents, email, files, browsing and communication
  • You care about where your data lives and who controls it
  • You have, or can get, someone to look after the setup

Think twice, or keep some tools, if:

  • You depend on industry software that only runs on one platform
  • You exchange complex, macro-heavy files with partners every day
  • Nobody will be responsible for updates and maintenance

My background is in Linux system administration, and I run my own infrastructure on open-source tools. If you'd like an honest assessment of what could move and what should stay, the Linux & open-source migration package starts with exactly that review. An IT Health Check is also a good first step.