Sage 50 · 3 min read · Updated August 24, 2026

Another user has it open in the previous release" Sage 50 conversion error

Sage 50 is refusing to convert your company file because someone, or a stuck session, still has it open in the older version.


You are trying to open or convert a company file after a Sage 50 update, and instead of progress you get:

“You cannot convert this company file because another user has it open in the previous release.”

In plain terms, Sage 50 believes the file is still open somewhere in the older version of the program. A conversion locks the file so that only one process can touch it at a time. Until every copy of the old release lets go, the new one will not start the conversion. Often there is no other person at all: a leftover session, a hung process, or a stale lock is holding the file.

Is someone actually in the file?

On a multi-user setup, ask around first. A colleague who still has the old release installed may have the company open right now, perhaps on a workstation that did not get updated. Have them close the company and exit Sage 50 completely. Then try again. This is the safest fix, and it works most of the time.

If the file sits on a server and workstations connect to it, check that every workstation has closed the old version, not just minimized it. A minimized window still holds the lock.

Could a stuck session be the culprit?

When nobody has the file open but the message persists, a hung session is the usual cause. This happens after a crash, a forced shutdown, or a remote desktop session that ended without closing the program. Restart the machine where the message appears, and if the file is shared, restart the machine hosting the file as well. That clears most stale locks.

Also check for background processes that did not shut down cleanly. If a Sage process is still listed after you close the program, end it, then try the conversion again. The exact steps depend on your setup, so if you are unsure, a full restart of both machines is the simpler route.

Does a backup copy convert instead?

If the lock will not clear, try converting a backup of the company rather than the live file. Restore the backup to a different folder, open it in the new release, and let the conversion run there. This sidesteps whatever is holding the original file. It does not fix the lock, but it gets you moving, and it confirms the file itself is fine.

Work from a copy of the backup, never the only backup you have.

What if the file still will not convert?

Occasionally the message is a symptom rather than the whole story. A company file with internal damage can fail conversion and report it as a locking problem. If restarts, closed sessions, and a backup copy all lead back to the same message, the file likely needs professional attention, and we would rather tell you that plainly than have you retry indefinitely.

Our engineers can examine the file, determine whether it is a lock, a permissions issue, or actual damage, and convert or repair it as needed. The diagnosis depends entirely on the file, so we start with a free evaluation and a no-obligation quote. If you were converting to QuickBooks rather than updating Sage 50, see our Sage 50 to QuickBooks conversion service for what carries over and how we handle it.

To get started, contact us about your file and we will take a look.