Update & Migration Problems

Why updates and migrations go wrong

Version upgrades touch nearly every part of an accounting program at once: the underlying data structure, report templates, add-on integrations, and sometimes licensing validation. A single interrupted download, an incompatible add-on, or a company file that was already carrying minor damage can turn a routine update into a multi-day headache.

Common symptoms

• An update download stalls at a fixed percentage or repeatedly restarts
• The software opens to a blank or unresponsive screen after updating
• Previously accurate reports show different totals after a patch
• Custom templates, logos, or formatting disappear after a migration
• An "incompatible version" message appears when opening a file from a colleague
• Add-ons or integrations stop connecting after an update

Step-by-step resolution sequence

Step 1 — Confirm your backup exists and is recent

Before doing anything else, verify you have a complete backup made within the last day, stored somewhere outside your main working folder.

Step 2 — Check your internet connection stability

Large update downloads are especially vulnerable to intermittent connections. If possible, connect via a wired connection rather than Wi-Fi for the duration of the update.

Step 3 — Close all related background processes

Some accounting programs run background services even when the main window is closed. Fully quit these processes (check your system's running-processes list) before restarting the update.

Step 4 — Restart the update from a clean state

If an update stalled, cancel it fully, restart your computer, and begin the update again rather than trying to resume a partially completed download — partial update files are frequently the root cause of a repeated stall.

Step 5 — Verify add-on and integration compatibility

Before updating, check whether any connected add-ons, bank feeds, or third-party integrations have a known compatibility note for the new version. Disable non-essential add-ons temporarily during the update.

Step 6 — Compare reports against a pre-update backup

If totals look different after an update, open your pre-update backup copy (in a separate, non-connected instance if possible) and compare specific figures. This tells you whether the discrepancy is a display issue, a rounding change, or an actual data problem.

Step 7 — Reapply lost formatting from a template backup

If custom templates or formatting vanished during a migration, check whether your software stores template files separately from the company data file — these often survive independently and can be reimported.

Preventing future update issues

Schedule updates for a low-activity period, never during an active payroll run or close-of-books week, always confirm a fresh backup exists first, and keep a written note of any custom add-ons or integrations so you can quickly verify their compatibility after each update.