One of the reasons software decisions are more consequential than they first appear is that switching from one tool to another is rarely as simple as cancelling one subscription and starting another. Switching costs — the time, money, and disruption involved in moving from one piece of software to another — are an important consideration when evaluating any significant tool, and understanding them helps founders make more durable purchasing decisions.
Software switching costs include the time required to migrate data from one system to another, the effort involved in retraining staff on a new interface and workflow, the disruption to ongoing work during the transition period, the cost of any integration work needed to connect the new tool to existing systems, and the risk of data loss or corruption during migration. For tools that become deeply embedded in daily operations — accounting software, CRM, or project management platforms — switching costs can be substantial.
The existence of switching costs is an argument for taking software decisions more seriously. It also argues for assessing data portability before committing — understanding how easily data can be exported if you want to leave a tool is a reasonable part of the evaluation process. Our guide to evaluating software for UK businesses covers how to factor switching costs into a purchasing decision.