ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Best Practices on Salesforce Release Management

Updated on May 10, 2019
profile image

Salesforce Consultant from 2 years, worked in different fields but I am pretty decent in Salesforce.

Challenges for Salesforce Release Management

Here are some of the challenges faced by Salesforce org:

Complex Salesforce Orgs

The Salesforce environments are mostly complex and large and have large custom objects, profiles and permission sets. Any typical deployments consist of a few thousand members.

Multiple Release Environments

The code usually moves across multiple environments say SIT, UAT, stage etc. Finally, it is deployed in the production. The challenge lies in the maintenance of these various environments – with many pre and post-migration activities that are involved at each sandbox level.

Multiple Parallel Releases

The development and the release environments sync with each other and this constitutes a major challenge. The types of releases are : minor releases, major releases and hotfix releases. The minor releases are on configuration changes, the major releases are those released once in any quarter and the hotfix releases are those concerning of any business-critical issues occurring simultaneously.

Version Control

Changes occur to shared metadata members say custom objects and profiles. This results in overwriting of code. The challenge lies in maintaining the versions of changes, track them and roll them back in the Salesforce environment.

Challenges with Refresh

If the developer adopts refreshes frequently, then they are liable to lose their work-in-progress and this leads to a lot of manual steps for development teams. Quite often the developer sandboxes, release environments and production orgs go out of sync. All this is due to the fact that changes happen directly in Salesforce environment during releases and in some cases BRs are rejected in the UAT/Stage, not going live to production.

Now, it is time to come to best practices on Salesforce Release Management best practices.

Best Practices on Salesforce Release Management

Here are some of the best practices on Salesforce Release Management:

Designing the Right Sandbox Combinations for the Release

The right Sandbox composition is required for the release as per the various release phases. Salesforce has various sandboxes such as Developer, Developer Pro, Partial Copy and Full Copy sandboxes. These cater to various needs in organization – development, testing and training and more.

Continuous Integration for Automated Deployments

The teams need to collaborate, roll-back, perform change analysis and maintain isolation of code across multiple releases. Version control branches are used for version control setup for large enterprises. It is imperative to have a continuous integration settings, so that there is an early warning system, in case of integration issues as the developers need to integrate their code. This way the issues are fixed at the development stage itself.

Use Feature Branching and Pull Requests

It is normal for developers to use feature branching and pull requests for working with Git. But, we see the teams continue to use shared branches and cherry picked commit for production. You need to revisit the processes to continue to use the cherry picking commits along with hotfixes.

The individual developers/admins must work on personal sandboxes and then commit changes in the feature branch. The feature branch here represents a business change. The feature branch is pulled into integration branches, before deployed in the targeted production org.

Perform Code Review

For a successful source control and release management teams must adopt a code review culture. Code review incorporates the right tools and helps to improve quality and collaboration among the team members. This enables the team to stay in sync with the changes in the production environment.

Empower Users with Right Skill Sets for Release Management Process

Salesforce empowers the admins/business analysts. Support must be provided to these non-technical users in the forms of tools, with no need to learn XML, Git and Command lines, which enables them to take part in the Release Management process without any failure.

Modelling the Deployments

You must have a strategic deployment/Code Migration plan across the release environments. There must be a blueprint on Release Automation which tell about the flow of code from development to the production stage. These educates you on the extent of version control and streamlines the Release Management process.

Pre and Post Deployment Operations Checklist

There are many manual tasks to be done related to Metadata/Changeset constraints in Salesforce. One the best practices is to maintain a checklist on migration and refresh. This is only to inform the Release Management team to be notified on any issues.


Salesforce can be used by even the most non-technical users, with no need to understand code. The developers generally face lot of challenges on Release Management and one of these challenges is the maintenance of multiple release environments and the activities at the sandbox level. Yet another challenge can be that of syncing the development and release environments. There are various best practices that are used Salesforce Release Management. One of these best practices is about designing the right sandboxes, catering to various needs in organization in areas of development, training, and testing. In case of integration issues, there must be a continuous integration settings and a warning system. The non-technical users such as the business analysts must have the support of tools for taking part in the Release Management process, with no reason to fail.


    0 of 8192 characters used
    Post Comment

    No comments yet.


    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

    Show Details
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
    ClickscoThis is a data management platform studying reader behavior (Privacy Policy)