> For the complete documentation index, see [llms.txt](https://support.ordereazi.com/central/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.ordereazi.com/central/order-management/integrations/accounting-system/sage-evolution/setting-up-the-sage-evolution-connector.md).

# Setting Up the Sage Evolution Connector

Install the OrderEazi connector on your network, and link it to OrderEazi and your Sage Evolution company.

Your Sage Evolution databases sit on your own network, behind your firewall. The OrderEazi connector is a small program, installed on a Windows machine on that network, that connects out to OrderEazi. You don't need to open your firewall to OrderEazi.

### Before you start

The person installing the connector needs:

* **A Windows machine:** One that can reach your Sage Evolution SQL Server, with administrator rights. It doesn't need Sage Evolution installed. It needs the .NET Framework 4.8 and the .NET 10 Desktop Runtime, which the installer doesn't check for.
* **A Sage SDK licence:** The **SDK Serial Number** and **SDK Auth Key**, from Sage.
* **Your Evolution version:** The exact version, such as 11.0.0.10. Versions 6.82.2.70 to 12 are supported.
* **Database access:** Access to the Evolution common database and the company database you want to sync.

In OrderEazi, generating the setup code needs the **Accounting System** permission, in the **Integrations** permission group. If you don't have it, ask your OrderEazi administrator to add it to your role.

> **Note:** The connector's Windows service signs in to SQL Server as its own account, not yours. If you use Windows authentication, give that account access to both databases. **Test SQL** warns you about this.

### How to install and link the connector

1. In the main menu, go to **Integrations** > **Accounting System**, choose **Sage Evolution (SDK - on-premise connector)**, and select **Save**.
2. Under **Sage Evolution - SDK Connector**, select **Download Connector**, and run the installer on the Windows machine.
3. In OrderEazi, under **Connector setup code**, select **Generate**, then **Copy**.
4. On the Windows machine, open **OrderEazi Sage Evolution SDK Connector - Setup**. Paste the code under **Setup code (from OrderEazi settings page)**, and select **Apply**.
5. Choose the **Evolution Version**.
6. Select **Configure...** next to **Evolution common database** and **Evolution company database**, and choose each database.
7. Enter the **SDK Serial Number** and **SDK Auth Key**.
8. Select **Test SQL** and **Test Connection**, then **Save**.
9. In OrderEazi, select **Test connector**.

You see "Connector connected. Warehouses found:" and the number of Evolution warehouses.

The setup code works once, for 24 hours, and is only shown when it's generated. Generating a new code cancels the previous unused one.

**Example:** Your IT partner installs the connector on your Sage server on Monday morning. You generate a setup code and share it with them securely, as it works like a one-time password, and they apply it and choose your databases. When you select **Test connector**, OrderEazi shows "Connector connected. Warehouses found: 3", and you move on to mapping your warehouses.

### How to manage the connector

The **Registered connectors** list shows the machine, its status, and when it last signed in. Only one connector can be linked at a time.

* **Revoke:** Disconnects the connector and stops it connecting again. To link it again, generate a new setup code.
* **Remove:** Clears a line you no longer need, once its connector is revoked or its code was never used.
* **Company moved to a new server:** For the same Sage company on a new SQL Server or database name. Point the connector at the new location first. OrderEazi then matches your clients, suppliers, and products again by their codes on the next import, and holds documents until it has run.

To move the connector to another machine, revoke the old one, then generate a new setup code. Linking to a different Sage company isn't supported. Speak to your OrderEazi representative if you need it.

### When the connector doesn't connect

* **"No Sage Evolution SDK connector is currently connected to this instance.":** Check that the connector's Windows service is running on the machine.
* **"Sage Evolution rejected the SDK licence.":** Check the **SDK Serial Number** and **SDK Auth Key**, and that your Sage registration hasn't expired.
* **"That setup code is not valid.":** The code expired, was already used, or was replaced by a newer code. Generate a new one.
* **"A newer connector is available.":** Download the connector again, and install it over the old one.

### Related pages

* [Sage Evolution](/central/order-management/integrations/accounting-system/sage-evolution.md): what syncs, and the settings
* [Stock and Warehouses with Sage Evolution](/central/order-management/integrations/accounting-system/sage-evolution/stock-and-warehouses-with-sage-evolution.md): the next step, mapping warehouses