Sage 50 "maximum number of locks" conversion error explained
Sage 50 has run out of internal locks mid-conversion, so the process stops; the file itself is usually fine but too busy or too large.
The message reads:
The program cannot complete the conversion because it has reached the maximum number of locks that it can place against the database.
Despite the alarming wording, this is not usually a corruption message. A “lock” is a temporary hold the software places on records while it works on them. During a conversion, Sage 50 holds locks on the data it is reading and writing. There is a fixed ceiling on how many locks it can hold at once. When the conversion is large or complex, it hits that ceiling and stops. The data is typically intact; the process simply could not finish.
Which conversions does this affect?
We most often see it when a Sage 50 file (sold as Peachtree in the US and Simply Accounting in Canada) is being converted to QuickBooks, or moved between Sage 50 editions or versions. It also appears during internal database upgrades. The common factor is volume: the more transactions, years of history, and list entries in the file, the more locks the conversion needs, and the sooner it runs out.
Retry on a quiet system
Locks are also consumed by other activity. If anyone is working in the company file, or a backup, sync, or third-party add-on is running against it, retry the conversion with all of those closed. Put the file on a local drive rather than a network share if you can, since network interruptions can leave stale locks behind. Rebooting the workstation before the retry clears anything left over from the failed attempt. This succeeds sometimes, and it costs nothing to try.
Reduce what has to be converted
If the file holds many years of history, converting only the periods you actually need can bring the lock count back under the ceiling. Whether and how you can limit the date range depends on the file and the conversion path, so treat this as an option to explore rather than a guaranteed fix. The trade-off is that anything outside the converted range will not be in the destination file.
Let the conversion run outside the software
When a retry still fails, the built-in converter is the wrong tool for that file. Our engineers run Sage 50 to QuickBooks conversions outside the normal lock mechanism, so the ceiling does not apply. If you are moving from Sage 50 US, see our Sage 50 to QuickBooks conversion service; for Simply Accounting files, see our Sage 50 Canada to QuickBooks conversion service.
Could the file itself be damaged?
Occasionally the real cause is not size but damage: broken internal links can make the converter lock far more records than it should. If the file is also slow, fails to open cleanly, or shows odd totals, the database may need repair before any conversion will hold together. Our Sage 50 database repair service covers that side of the problem.
A useful next step
Send us the file for a free evaluation before you spend more time on retries. We will tell you whether the limit is being hit because of size, damage, or the conversion path, and quote the work from there. Cost and turnaround depend on the file, so we give you both after looking at it, not before.