--- title: "Mogli Upgrade Guide" slug: "upgrading" description: "Looking to upgrade Mogli SMS in Salesforce? Explore our complete guide covering upgrade steps, sandbox testing best practices, self-service vs. support-assisted" tags: ["Guidelines and Support"] updated: 2026-10-27T20:08:29Z published: 2026-10-27T20:08:29Z canonical: "guide.mogli.com/upgrading" --- > ## Documentation Index > Fetch the complete documentation index at: https://guide.mogli.com/llms.txt > Use this file to discover all available pages before exploring further. # Mogli Upgrade Guide Mogli regularly releases new package versions with bug fixes, security updates, and new features. Keeping your org on a current version ensures continued support and access to the latest functionality. Upgrades can be completed independently by a Salesforce Administrator or with Mogli's assistance, depending on your team's comfort level and available resources. ## How Upgrades Work A Mogli upgrade replaces your current package version with a newer one, applying any updated components, permissions, or configurations included in that release. The process generally follows four stages: #### **Review** Check the release notes for the new version to understand what's changing and whether any manual configuration steps are required. #### **Install** - Self Service: Use the installation link to upgrade yourself through the Salesforce AppExchange - Mogli-Assisted: Schedule with the Mogli Team to have the upgrade completed for you. #### **Test** Apply the upgrade in a sandbox first when possible, to confirm nothing breaks before upgrading production. #### **Confirm** Verify the new version number is reflected in your org and that key workflows (sending, receiving, automations) are still functioning as expected. --- ## Best Practices ### Stay Current Don't wait too long between updates. Falling multiple versions behind makes future upgrades more complex and risks missing crucial security fixes. Mogli releases new versions periodically for bug fixes, security updates, and new features. Since there is no fixed monthly or quarterly schedule, check the release notes regularly. ### Test in Sandbox Always upgrade in a sandbox environment first—especially if you have custom automations built on Mogli—to catch conflicts before production. ### Avoid Peak Hours Schedule updates during off-peak hours or outside active messaging campaigns to prevent any brief service disruptions during installation. --- ## Self-Service vs. Mogli Assisted Mogli upgrades can be completed independently by your Salesforce Administrator or guided by our support team. #### **Self-Service** **(via AppExchange)** **Best option if you:** - Have a Salesforce Administrator comfortable installing packages and reviewing release notes independently. - Want to control exact upgrade timing. - Are upgrading a straightforward configuration with no heavy customizations. #### **Mogli-Assisted** **Best option if you:** - Would rather have Mogli's team handle the installation process. - Have a highly customized org and want an extra check for compatibility. - Are unsure what a given release changes and want guidance before applying it. ## ### Mogli-Assisted Upgrades Most upgrades take effect immediately, but Mogli-assisted upgrades depend on support scheduling, so be sure to reach out ahead of your desired upgrade date to schedule with our team. [**Contact help@mogli.com**](https://portal.document360.io/aabde203-b6df-4543-b557-999d7d8b937a/document2) --- ## Upgrade Instructions ### Before The Upgrade - Review the release notes for the specific version you're upgrading to, so you know what's changing and whether it affects your configuration. - Schedule the upgrade and communicate the planned upgrade schedule to your team. - Be sure to schedule during off-peak hours to minimize disruption. - If you choose a Mogli-Assisted Upgrade, the Mogli team will collaborate with you to find the best time and date. - Back up your Salesforce data (optional, but recommended for larger or highly customized orgs). - Test the upgrade in a Salesforce sandbox. ### The Upgrade - The Salesforce Administrator clicks the installation link and follows the installation prompts. ### After The Upgrade - Confirm the new version number is reflected correctly in your org. - Review the release notes again for any required configuration adjustments — these may include updating page layouts, adjusting automation rules, or configuring new settings. - Make any required adjustments right away, rather than leaving them for later, since some new features or fixes may not work correctly until configuration is complete. - Reach out to help@mogli.com if anything looks off after the upgrade or you have questions about a change. ### FAQ #### Why do I need to upgrade my Mogli package? Upgrades deliver bug fixes, security updates, and new features, and keep your org eligible for continued support. #### How often does Mogli release new versions? There isn't a fixed schedule — Mogli releases new versions periodically for bug fixes, security updates, and new features. Check the release notes to see what's changed since your current version. #### Can upgrade myself, or do I need Mogli’s help? Either. Self-service upgrades via the Salesforce AppExchange work well if you have an Administrator comfortable installing packages independently. Mogli-assisted upgrades are better if your org is heavily customized or you want guidance before applying a release. #### How long does an upgrade take Most upgrades take effect immediately once installed. A Mogli-assisted upgrade's timing depends on support scheduling — contact help@mogli.com ahead of your target date. #### Should I test an upgrade before applying it to production? Yes, especially if your org has custom automations built on Mogli. Apply the upgrade in a sandbox first to catch any conflicts. #### What should I do after upgrading? Confirm the new version number appears in your org, review the release notes for any required configuration changes, and make those adjustments right away.