Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Teams
, (opens new window)
Satago Customer Support
Results will update as you type.
  • Getting Started
  • Credit Control
  • Risk Insights
  • Invoice Finance
  • Accounting Software Connections
  • Sage 50 Connection Help
    • Connecting Sage 50 pre v29.2 to Satago
    • How to uninstall your Satago Sage 50 connector
    • Updating your Sage 50 connector
    • How can my IT team install the Satago Sage 50 connector?
    • How do i find my Sage 50 connector?
    • Complete a Full Re-Sync from the Sage 50 connector
    • How to ensure your Sage 50 data syncs to Satago automatically
    • Bulk client onboarding for accountants using Sage 50
    • How to complete a manual import from Sage 50
    • I have installed and synced my Sage 50 connector but i don't know what to do next?
    • Connecting Sage 50 to Satago
    • Connecting Sage50 v29.2 or later with Satago
    • My Data Directory in Sage 50 has changed. How can I update this on Satago so my data stays up to date?
    • Sage 50 Connector - Troubleshooting Steps
    • How to perform a full re-sync from Connected Services in Sage 50
    • Sage 50 “Already Connected by Someone Else”
  • Invoices & Payments
  • Managing your Account
  • Partnering with Satago
  • Privacy & Terms
  • About Satago
  • Modern Slavery Statement
    Calendars
You‘re viewing this with anonymous access, so some content might be blocked.
/
Sage 50 “Already Connected by Someone Else”
Updated Oct 16

    Sage 50 “Already Connected by Someone Else”

    This article explains why you may see the error “already connected by someone else” when restoring Sage 50 company data from a backup, and how to resolve it so you can use connected services like Satago.

    Why am I seeing this error?

    You are likely seeing this error because your Sage 50 company was created using a database backup from another company (often by a consultant or accountant). This method is not recommended by Sage.

    The backup contains a unique identifier (the Company Ref) that is already in use by another company. This duplication prevents you from using Sage’s connected services, including Satago.

    image-20250312-164046.png

     

    How do I resolve the Company Ref conflict?

    1. Create a new company file in Sage 50 and copy your data following Sage’s official guide: How to create a new company from an existing company.

    Who can I contact for help?

    If you need help with the data migration process, contact Sage Support and explain that you have a “Duplicate CompanyRef” issue. Let them know you have been advised to create a new company in Sage 50 and transfer your records over, starting with opening balances.

    Sage Support can guide you through the process and ensure your company is set up correctly.

     

    {"serverDuration": 9, "requestCorrelationId": "5a054f7f0571413a91a0ff87c1317966"}