Home → Integrations / Bolt-Ons → Sage 50 → Pre-installation checklist
7.2. Pre-installation checklist
Before you can get started integrating your RubiCRM system with Sage 50, you need to complete the steps below.
1. Sage Version
Client must be using Sage 50 Accounts and hold a multiuser/multicompany professional license to enable full API functionality.
2. Sage Full Installation
Sage 50 Accounts full desktop client must be installed on the server or PC hosting the Sage Data, as the Hyperext API must be installed locally to the Sage Data.
Due to complications, we do not support the use of Remote Data Access (RDA) for Sage 50.
Existing clients who do use an RDA, if in the event RubiCRM shows that an invoice has been exported to your Sage 50 system and you are unable to see it, you MUST contact your Sage partner / IT Support.
3. Host Computer O/S
The target Server or PC must have a static internal IP address. Server O/S must be Windows Server 2012 or later. PC O/S must be Windows 10 or newer. The machine should always be powered on. Please note, we will not install the API on to a laptop.
4. Fixed External IP
For Secure External Access to API - the Internet router must have a static or fixed external IP address. We will configure DNS and SSL linked to this IP.
5. Firewall Port Forwarding Rules
Client IT support/network admin will need to configure port forwarding rules on TCP ports 40027 and 50027 from the external network interface to the target host. (This can be locked down to specific IP addresses if desired. Source IPs are 62.64.222.138, 217.194.210.113, 191.96.201.86, 87.117.229.200, 37.120.200.220, and 20.0.202.237)
6. Remote Control
For the installation, we normally connect remotely via TeamViewer, so the TeamViewer client will need to be downloaded and run on the target machine. When connected, we need to land in a user session with full admin permissions to correctly configure the various components of the API solution. Alternatively, we can install over RDP if preferred.
7. API Setup Time
The setup process typically takes around 2 hours. During the setup, it is possible to continue using Sage normally. Although there is a brief period of about 10 minutes that we will need MANAGER access to Sage. A server restart is not normally required during the setup, but if a restart is required, we will request permission before restarting.