Sage, Xero or QuickBooks Slow? A Corstorphine Guide

Almost every small-business call we get from Corstorphine that starts with "our accounting software is slow" ends up being something other than the accounting software. A solicitor's practice off St John's Road running Sage. An accountancy firm behind Corstorphine High Street on QuickBooks Desktop. A design consultancy near Ladywell using Xero with a big attachments folder. Different tools, same shape of problem — the software is the messenger; the plumbing behind it is what's really broken.

This post is what we actually check first, in the order we check it, when a Corstorphine business rings and says the ledger takes thirty seconds to open a client file that used to open instantly. If you're troubleshooting it yourself before booking a callout, work through in this order — the fix is nearly always upstream of the software.

1. It's Almost Never the Software Itself

Sage 50, QuickBooks Desktop, and every locally-installed variant of a small-business ledger share the same architecture: an application on each workstation, and a database file (or a small set of them) sitting somewhere the whole team can reach. Xero and QuickBooks Online swap the local database for a browser session, but they still depend on your local network and workstation being healthy.

When the software feels slow, one of four things is normally happening: the database file is somewhere it shouldn't be, something on the workstation is scanning it on every read, the machine holding the database is under-specified for the job, or the network between the two is dragging. Each of those looks like "the software is slow" from the desk. None of them get better by reinstalling.

2. The Cloud-Sync Trap

This is by a wide margin the most common one we find in Corstorphine offices, and the one that does the most damage. Somebody sensibly wanted a backup of the accounts folder, so they dragged it into OneDrive, Dropbox or Google Drive. Now every save from every desk triggers a cloud sync, and if two staff have the same client file open, the sync engine produces conflict copies — sometimes silently.

The visible symptom is that the software gets slower and slower through the day, especially at month-end when everyone's in the ledger at once. The invisible risk is much worse: conflict copies mean two versions of a client's records exist and neither is definitive. We had exactly this pattern at a Corstorphine practice earlier this year — three machines all pointed at a Sage database stored in a synced folder. The fix was to move the database file to a proper file share and remove that folder from cloud sync entirely. The cloud copy is still valuable as a nightly backup — just never as the live working location.

3. Antivirus Scanning Every Database Read

The second most common find. Windows Defender, and most third-party endpoint tools, will happily scan a multi-gigabyte accounting database file on every read and write unless you tell them not to. On a busy ledger that means every keystroke is triggering a full file scan in the background.

Sage, Intuit and Xero all publish specific exclusion lists — the exact folder paths, file extensions and processes that should be excluded from real-time scanning on both the workstation and the machine hosting the database. Applying those exclusions to a healthy endpoint tool is a fifteen-minute job and often takes a "everything is treacle" office back to normal on its own. It is worth doing this before assuming anything harder is wrong.

4. Using a Regular Desktop as an Ad-Hoc "Server"

The classic small-business setup: one machine is nominated as the one that holds the shared accounts folder, and everyone else maps a drive to it. That works fine for a few users on a wired network. It stops working when the machine is a consumer laptop with a cheap SSD, when its lid is closed on Wi-Fi under somebody's desk, or when it's the same PC the receptionist uses for everything else.

The give-away is that the ledger runs at full speed on the "server" machine and slowly on every other machine. If that's the pattern, the fix is a proper dedicated share — either a small business-grade NAS on the wired network, or moving to the cloud version of the same product if the business is heading that direction anyway. Either way, the ledger database should not be living on somebody's day-to-day working PC.

5. The Wi-Fi and Cabling Bottleneck

Even when the "server" and the workstations are all specified correctly, we regularly see accounting software slow to a crawl because the office network is doing the wrong things. Common causes we've fixed in and around Corstorphine include: workstations on Wi-Fi when a wired run would take an afternoon to install; an old unmanaged switch stuck at 100Mbps in a rack of gigabit kit; a router hosting the ledger database over its own Wi-Fi radio (yes, really); and long cable runs terminated so badly that packets are being retransmitted constantly.

For a small office where the ledger is the daily bread, wired Ethernet from every workstation to a decent gigabit switch is a one-off job that pays off for years. Full networking and Wi-Fi work — including proper cabling, patch panels and switching — is usually the last thing needed to make a stubborn ledger feel instant.

6. What Actually Fixes It (The Bench View)

On the bench and on-site, we work through the same checklist in the same order for every "accounting software slow" job: check where the database file actually lives; verify it isn't inside a synced cloud folder; apply the vendor's antivirus exclusions; measure whether the workstation SSD is saturated or the network link is the limit; move the database to a proper file share if it's on a workstation; and only then look at the software itself for a rebuild or reindex.

Because the checklist is boring and repeatable, most Corstorphine callouts for this issue turn into a two-hour visit rather than a two-day investigation. If you'd rather have someone on standing arrangement to catch these problems before they become month-end panic, that's exactly what our business IT support is for — regular health-checks of the workstations, the database host, the network and the backup, so nothing quietly degrades over a year until a client complains.

And if the ledger has gone from slow to unreachable and there's any concern about the database file itself, stop opening it and give us a ring first. Accounting database data recovery is much simpler done before somebody has tried to "just repair" the file five times.