Module Loader

The Module Loader section includes topics covering working with and troubleshooting the installation of modules and customizations via Admin > Module Loader.


Sugar's Module Loader allows organizations to upload and install custom packages to their Sugar instances. If a package is no longer needed, administrators have the option of either disabling or uninstalling it. Before performing these actions, it is helpful to understand the difference between these two options and how they affect the installed package. For more information regarding Module Loader in Sugar, please refer to the Module Loader documentation. 

When an existing defect in Sugar is addressed and has a status of either "Closed" or "Pending-QA", a hotfix can be installed before the next release in order to resolve the bug on an instance running the previous release. On-site clients can request for the hotfix package, which is a module loadable package that can be installed in Sugar to fix the specific bug. Hotfixes cannot be installed in Sugar cloud instances. This article will go over how administrators can install a bug hotfix package to an on-site instance.

While uninstalling a package (e.g. Sugar Connector for Marketo) in Module Loader, you notice older versions of the same package display as installed. You can uninstall these packages from Sugar®, but may experience issues where the Uninstall button does not appear next to the package or the uninstall process fails to complete. This article will cover how to manually remove module loader packages from Sugar.    

Administrators in Sugar can make customizations to modules via Studio as well as create custom modules via Module Builder. Occasionally, Studio and Module Builder customizations developed in one instance may need to be migrated to another instance. This article will go over how to migrate both Studio and Module Builder customizations between different instances.

SugarCRM's hosting objective is to maintain the integrity of the standard Sugar functionality when we upgrade a customer instance and limit any negative impact our upgrade has on the customer's modifications. All instances hosted on Sugar's cloud service have package scanner enabled by default. This setting is not configurable, and all packages must pass the package scan for installation to the SugarCloud environment to proceed.

Reach out to us for help