When to repair, upgrade or replace business computers

1. Start with the work that needs doing

A computer does not need replacing simply because it is three years old. For a small business in Cranbrook or elsewhere in the East Kootenay, the useful question is whether it can keep doing its job reliably, securely and without holding people up.

Start with the friction staff can describe: waiting for accounting reports, dropped video calls, an unreliable charging port or a laptop that cannot last through a site visit. Ask when the problem happens and what work it interrupts. Investigate before buying. A slow internet connection or overloaded application is not necessarily a computer problem.

The goal is a refresh plan with a reason for each decision, not a shopping list built around age.

2. Build an inventory you can actually use

A spreadsheet is enough to start. Give each device an owner and record:

• Model, serial number, location and purchase information.
• Processor, memory, storage capacity and free space.
• Operating system edition and version, update coverage and warranty.
• Business applications, licences, printers, scanners and other dependencies.
• Battery condition, recurring faults, backup arrangements and encryption recovery information.

Keep recovery keys in an appropriately secured location, not in a general inventory sheet. Include shared machines and equipment in cupboards. Ask which device would stop invoicing, payroll or customer service if it failed tomorrow. That answer is more useful for setting priorities than the purchase order alone.

3. Separate support risk from physical age

An older computer that remains supported and performs its role is a different case from a newer one running unsupported software. Microsoft's Windows 10 Home and Pro lifecycle identifies the end of ordinary support; it also notes that existing Long-Term Servicing Channel releases have their own lifecycles. Check the actual edition rather than treating every Windows 10 installation alike.[4]

Windows 10 PCs do not automatically stop working. Microsoft's Extended Security Updates programme provides enrolled, eligible devices with critical and important security updates after ordinary support ends. Commercial organisations can obtain coverage for up to three years, but ESU does not restore general technical support, new features or customer-requested non-security updates.[1] Treat it as a budgeted transition option, not a reason to abandon migration planning.

For Windows 11, Microsoft lists requirements including TPM 2.0 and UEFI firmware with Secure Boot capability.[2] Verify full eligibility for each model before spending money on upgrades.

4. Compare repair, upgrade and replacement

Keep a machine when it meets the job's needs and has an acceptable support path. Consider repair for an isolated fault, such as a worn battery, when parts and labour make sense against its remaining useful life. Consider an upgrade when testing identifies a specific bottleneck and the model can accommodate the change.

Adding memory will not solve every slowdown, and a new drive will not establish Windows 11 eligibility. Replacement becomes more reasonable when faults recur, necessary software cannot be supported or the work consistently exceeds the machine's capabilities.

Compare complete costs over the same planning period: equipment, parts, labour, licences, temporary security coverage, accessories, setup, staff interruption and disposal. Include delivery and a workable fallback during repairs. Request itemised quotes rather than assuming the cheapest purchase price produces the cheapest working result.

5. Test one real workflow before ordering the batch

Microsoft's minimum Windows 11 requirements are an installation baseline.[2] Choose working specifications by testing the applications people actually use together, not by assuming that meeting the minimum guarantees a comfortable workday.

Consider this hypothetical office, not a StratIS client example: a Cranbrook business has a receptionist, a bookkeeper and a manager who travels. The receptionist's supported desktop handles scheduling well. The bookkeeper's computer struggles during reporting. The manager's laptop has a failing battery.

The sensible outcome might be to keep the desktop, test whether an upgrade resolves the reporting bottleneck and price a battery repair. Before standardising a replacement, pilot one device with accounting software, bank access, label printing, scanning, video meetings and the existing dock. Ask each user to complete a normal task and confirm the result.

6. Give the plan a rolling budget

Group the inventory into keep, investigate and schedule for replacement. For each planned change, record the reason, expected spending window, dependencies and person responsible. Prioritise unsupported configurations and unreliable equipment that carries essential work.

Set aside money for the whole project, including migration and an allowance for unexpected faults. Stagger purchases where practical, but do not spread a known security problem across several budget cycles simply to make spending look even. Review the plan when software requirements, staffing or business workloads change.

A forecast is not a mandatory replacement deadline. Extend useful life when the evidence supports it, and bring spending forward when the risk or disruption justifies it.

7. Plan the handover and the exit

Before migration, identify local files, application settings, licence access and required records. Make a backup and test that representative files can be restored. Schedule a quiet period, name the person checking the new setup and retain a controlled fallback until essential tasks work.

Do not confuse deleting files with secure disposal. The Canadian Cyber Centre warns that data can remain recoverable after deletion. Do not assume a reset is enough to sanitise business data.[3] Choose a sanitization method suited to the storage media and information involved, using manufacturer guidance or qualified assistance.

The Cyber Centre also advises backing up before erasure and disconnecting unwanted devices from online accounts.[3] Confirm retention needs first, record the sanitization outcome and recipient, and arrange appropriate reuse or recycling. Seek trusted destruction services where sensitive data warrants destruction.

8. Use this decision checklist

• Purpose: What work must this device support?
• Evidence: Have we identified the actual fault or bottleneck?
• Security: Is there a verified software support path?
• Value: Have we compared complete repair, upgrade and replacement costs?
• Fit: Has a user tested essential applications and peripherals?
• Handover: Are backups, restore checks and a fallback ready?
• Exit: Who will verify sanitization and record disposal?

If those answers are clear, the refresh has a business reason. If they are not, the next step is investigation, not necessarily new hardware.