FAQ- Sage 50 "already connected by someone else"

FAQ- Sage 50 "already connected by someone else"

Restoring your Sage 50 company data from a backup of an existing company has led to a conflict. It is likely that when your company was created in Sage 50, it was done using a database backup from another company, possibly by a consultant or accountant on your behalf. However, this method is not advised by Sage.

The backup contained a unique identifier, referred to as the Company Ref within Sage 50, which is already in use by another company. This duplication prevents you from utilising Sage's connected services including Satago. The root cause is the pre-existing Company Ref ID clash.

Sage's official solution is to create a completely new company file within Sage 50. Subsequently, you should migrate all your data from the problematic company file to this newly created, clean company file. This process ensures a unique Company Ref is assigned, resolving the conflict. If you require assistance with this data migration, Sage Support can provide guidance and support; contacting them to explain your specific situation is recommended. They are equipped to help you navigate this process effectively.

Please follow this FAQ guide from the Sage website-How to create a new company from an existing company. If you need to contact Sage support let them know you have the issue of a “Duplicate CompanyRef” above and you have been advised you “you need to create a new company in Sage 50 and transfer your records over, and starting with opening balances”. We advise going through it with Sage support if you are not confident in being able to do this yourself.

image-20250312-164046.png