Salesforce deployments, also known as ‘releases’, are one of the greatest challenges for admins, consultants, and those working in multiple other roles. As Salesforce orgs become increasingly complex, changes often have many ‘moving’ parts that can have far-reaching impacts on the Salesforce org. Once you are satisfied with the solution you’ve built (in a sandbox …
Here are highlights from article Salesforce Deployment Checklist: From Kick-off to Adoption | Salesforce Ben
1. Types of Salesforce Deployments:
– CPQ Deployments: Difficult to deploy changes between environments due to the number of data relationships between CPQ objects.
– Salesforce Industries: Configuration changes to Vlocity/Salesforce Industries solutions require careful deployment to ensure correctness.
2. Step 1: Project Kick-off:
– Conduct a kick-off meeting to involve all stakeholders and ensure their inclusion in the project.
– Engage with individuals from various levels of the organizational hierarchy, as they can provide valuable insights into Salesforce usage.
– Organize the kick-off session agenda to explain team roles, project overview, timeline, achievements, concerns, and action plans.
3. Step 2: Sandbox Creation and Configuration:
– Create a sandbox environment to develop and test changes before deploying them to production.
– Configure the sandbox to mirror the production environment as closely as possible.
– Use a version control system to track changes and ensure consistency across environments.
4. Step 3: Change Set or Metadata Deployment:
– Choose the appropriate deployment method based on the complexity and size of the changes.
– Use Change Sets for simple deployments involving fewer components.
– Use Metadata API or Salesforce CLI for complex deployments with a large number of components.
5. Step 4: Validation and Testing:
– Validate the deployment by reviewing the changes in the production environment.
– Perform thorough testing to ensure that the deployed changes function as expected.
– Include user acceptance testing (UAT) to involve end users and gather feedback before finalizing the deployment.
You can read it here: https://sfdc.blog/VkMzI
Source from salesforceben(dot)com