In larger Sage CRM implementations, where there is a high demand on the application server, Sage CRM can be deployed in a multi-server environment. This allows a single Sage CRM database to be accessed through multiple web/application servers. Performance can be enhanced through the load balancing provided by Sage CRM or by a dedicated load-balancing application.
This article is a round up of Community Hub articles and Help Center resources that may be useful when planning, installing, maintaining or upgrading a multi-server Sage CRM implementation.
The key principle to remember is that a multi-server Sage CRM environment is still one Sage CRM system. The web/application servers share a single database, and care must be taken with services, metadata, file-based customisations, the Document Library, Exchange integration, security, SQL Server connectivity and upgrade sequencing.
Core Help Center resources
The best place to start is the Sage CRM Help Center.
Sage CRM Help Center
https://help.sagecrm.com/
System Administrator Guide
https://help.sagecrm.com/pdf/2025R1%2B/SageCRM_SystemAdminGuide_EN.pdf
The System Administrator Guide contains the core section on Multi-server Sage CRM. This covers prerequisites, installation, configuration, load balancing, preparing for upgrade, upgrading, and installing Sage CRM on database and non-database servers.
Sage CRM 2026 R1 Hardware and Software Requirements
https://help.sagecrm.com/pdf/2026R1/SageCRM_2026R1_HardwareSoftwareRequirements_EN.pdf
The Hardware and Software Requirements guide should always be checked before designing a multi-server environment. It defines supported operating systems, database versions, browser support, TLS support, virtualisation support and limitations such as reverse proxy and Citrix/RDS considerations.
Sage CRM 2026 R1 Release Notes
https://help.sagecrm.com/pdf/2026R1/SageCRM_2026R1_ReleaseNotes_EN.pdf
The Release Notes are important when upgrading a multi-server environment because they explain the supported upgrade path, installation prerequisites, post-upgrade tasks and known issues for the release.
Multi-server Sage CRM
https://help.sagecrm.com/on_premise/en/2025R2/Administration/Content/InstallUpgrade/MC_FAQs.htm
This is the Help Center landing page for the multi-server Sage CRM topics.
Multi-server Sage CRM prerequisites
https://help.sagecrm.com/on_premise/en/2025R2/Administration/Content/InstallUpgrade/MC_MultiServerCRMPrerequisites.htm
This explains the need for a valid multi-server licence, the importance of identifying the web/application servers and database server, and the need to decide where services such as the Indexer, Escalation Service and Email Manager will run.
Installing multi-server Sage CRM
https://help.sagecrm.com/on_premise/en/2025R2/Administration/Content/InstallUpgrade/MC_InstallingMultiServerCRM.htm
This article explains the installation sequence. Sage CRM should be installed on the primary web server first, creating the database on the database server. The other web servers are then installed using the same installation name and database server name. The article also explains the need for a shared UNC path for the Document Library and the special handling needed for the Exchange Sync Engine.
Configuring multi-server Sage CRM
https://help.sagecrm.com/on_premise/en/2025R2/Administration/Content/InstallUpgrade/MC_MultiServerCRMConfigSettings.htm
This explains the configuration settings used by Sage CRM in a multi-server environment. It also notes that after an IIS reset or application pool recycle, each server in the cluster must be logged into manually so that load balancing operates normally.
Load balancing in a multi-server environment
https://help.sagecrm.com/on_premise/en/2025R2/Administration/Content/InstallUpgrade/MC_LoadBalancing.htm
This explains how Sage CRM load balancing works. Sage CRM obtains the list of available servers from the custom_sysparams table, calculates the number of users logged on to each server, and submits the login page to the server with the lowest number of logged-on users.
Database fields
https://help.sagecrm.com/on_premise/en/2025R2/Administration/Content/Administrator/SS_DBSettings.htm
This article explains the database settings used in a multi-server deployment, including Distributed CRM web server names, Distributed CRM web server IP addresses, Do load balancing, DTLS server name and Fully qualified CRM web server names.
Preparing for upgrading multi-server Sage CRM
https://help.sagecrm.com/on_premise/en/2025R2/Administration/Content/InstallUpgrade/UM_PrepUpgrMSCRM.htm
This is essential reading before upgrading. It explains that before beginning an upgrade, all servers except the database server should be disconnected from the database. It also notes that multiple Tomcat servers can point at one database if the database has enough connections to serve the multiple connection pools.
Upgrading multi-server Sage CRM
https://help.sagecrm.com/on_premise/en/2025R2/Administration/Content/InstallUpgrade/UM_UpgradeProcess.htm
This gives the overall upgrade approach: manually back up the database, program files and registry; set up a test environment that mirrors live as closely as possible; perform and test the upgrade; then perform the live upgrade on each Sage CRM server, starting with the database server.
Community Hub articles
Customizations within a multi-server installation of Sage CRM
This is the key Community Hub article on Sage CRM multi-server customisation. It explains that metadata customisations are stored in the database and are therefore shared between servers. It also explains that file-based customisations, including ASP pages, .NET assemblies, JavaScript files, icons and images, must be copied manually to every web/application server that may serve the affected screens.
The article also discusses the distribution of Sage CRM services. The important rule is that the Sage CRM services should only have one instance running in the server cluster. For example, one server may run Email Manager, another the Escalation Service, and another the Indexer/QuickFind service.
More thoughts on System Architecture and Security
This article is useful when considering DMZ or segmented network designs. It discusses the need for each Sage CRM/IIS instance to connect to the database server using TCP/IP and raises important questions about Sage CRM user permissions, database user permissions, Document Library authentication and whether IIS Auto Login or Active Directory features can be used in mixed network designs.
Some thoughts about Multi-threading in Sage CRM
This article explains how requests pass through Sage CRM, IIS, Tomcat and SQL Server. It is useful background when discussing performance, because a multi-server Sage CRM deployment scales the web/application tier, but performance still depends on the database server, network latency, IIS, Tomcat and customisations.
Deployment Options
This article discusses the flexibility of Sage CRM deployment models, including on-premise, private cloud, public cloud and hybrid deployment. It is useful context when deciding whether a multi-server architecture is required and where the web/application and database layers should be placed.
Optimizing Storage and Database Performance in Sage CRM
This article is relevant to multi-server systems because database and storage performance are critical in distributed deployments. It discusses database optimisation, index maintenance, storage management and moving the Sage CRM Library to a separate server using a network path.
Using the License Key Update Application
This article explains the Sage CRM licence key update application. It is relevant because the licence determines whether the key is valid for a multi-server environment. A valid multi-server licence is required and the same licence key can be used on all servers in the cluster.
Some thoughts about moving database servers
This article is useful when considering server moves, database moves or infrastructure refreshes. It reminds administrators to consider the Document Library, custom files, registry settings, database settings and the need for the new web server to match the live Sage CRM version.
Sage CRM 2026 R1: Planning your upgrade
This article is useful for multi-server upgrades because it stresses the importance of planning the Sage CRM and SQL Server upgrade path carefully. It recommends changing one major component at a time and avoiding unsupported shortcuts when moving older systems to current supported platforms.
Sage CRM 2026 R1: Implementation Improvements – Security Updates and Hardening Measures
This article explains the security and hardening focus of Sage CRM 2026 R1. It is useful background for multi-server environments, where secure configuration, supported platforms and resilience are especially important.
Sage CRM 2026 R1: Changes to Help and Available Resources
This article explains the current Help Center model and the move to a single-version documentation approach. It is useful because administrators should always check the current Help Center guidance before installing or upgrading a multi-server Sage CRM environment.
AES-256 Encryption and Sage CRM: Protecting Data at Rest and in Transit
This article is useful when planning security in larger or distributed environments. It discusses protecting data at rest and in transit, including SQL Server encryption options and the importance of transport security.
Sage CRM 2023 R2: Deep Layered Defence for Integrated Sage CRM
This article is useful for partners and administrators who need to think about integrated Sage CRM deployments from a security perspective. Multi-server environments should be designed with layered security controls across the web/application tier, database tier, network, integrations and user access model.
Sage CRM 2026 R1: Improvements in Microsoft Exchange Online
This article is relevant because Exchange integration needs special care in multi-server deployments. The Help Center guidance explains that only one Replication Engine instance should be installed on the primary server, and this article provides broader context on Exchange Online improvements in Sage CRM 2026 R1.
Suggested reading path
If you are new to multi-server Sage CRM, start with the Help Center section on Multi-server Sage CRM, then read “Customizations within a multi-server installation of Sage CRM”. These two resources explain the core architecture: one database, multiple web/application servers, shared metadata, carefully distributed services, and file-based customisations that must be deployed to every relevant server.
Next, read the articles on system architecture, security, multi-threading, storage and database performance. These help explain why multi-server Sage CRM should be treated as a full infrastructure design, not simply as “installing CRM twice”.
For upgrade projects, read the Help Center upgrade topics and the Sage CRM 2026 R1 upgrade planning article. A multi-server upgrade should be planned, tested and treated as a controlled outage. The database should be backed up, all servers should have program files and registry settings backed up, and the live upgrade should be performed on each Sage CRM server, starting with the database server.