&gt;<i>(yes, it&#x27;s an older system---again, it ain&#x27;t broke so I&#x27;m not fixing it and lose even more time and effort).</i><p>It seems like this &quot;if it ain&#x27;t broke not fix it&quot; strategy doesn&#x27;t work out that great for you.<p>It only postpones problems for the future, when inevitably something will be broke (software rots too, not just food, especially in 2016, where it depends on tons of staff that can change&#x2F;be deprecated&#x2F;obsolete&#x2F;hard to replace&#x2F;taken down etc over time, from the hardware to the network to web services).<p>&quot;If it ain&#x27;t broken don&#x27;t fix it&quot; is only short term advice. It doesn&#x27;t eliminate the need to keep software systems reasonably up to date (and a 5 years old OS is like a 20 year old car in IT years).