Salesforce is an essential part of your organization, a living team member. Your CRM has been developing and changing since you’ve implemented it, and it requires regular checkups to remain healthy and perform at the highest level.
Your reports are inaccurate and your data is a complete mess
Does it sound familiar? You’ve put a lot of efforts and time customizing your CRM, but messy data influences your system and makes it completely ineffective.
Your sales team is avoiding Salesforce
Do you struggle with user adoption despite all the training efforts? Do your team members treat Salesforce like a Rolodex? A recently conducted survey shows that 59% of CRM implementations are not facing success because of low user adoption.
You are unsure about data security within your organization
When a team member leaves an organization, it is definitely the time to think about the security of information. Are you sure that all the security requirements are met? Is the login process secure and accurate? If you are unsure about those questions, it is time to do a review of your system.
You are not up to speed with new Salesforce releases
Due to frequent Salesforce updates on new features, it’s recommended to have a system health check done at least once six months. Whether you started using your CRM three years ago or just a year back, a full check of the tool will keep you up-to-date with the latest changes.
To address the above-listed issues, you should first get a clear picture of what your current situation is. Once you’ve identified all the weak points, proceed with solving them one at a time.
As a business owner or a technical manager, you can conduct a Salesforce health check on your own. We recommend to do it at least twice a year as a best practice. If you’ve decided to go down that path, here is a checklist carefully prepared by our team to help you get started.
Salesforce Health Check Checklist
- Open Setup->System Overview and check custom object and data storage limits in Schema section.
- Go through your custom objects and make sure you are not approaching the limits listed in the table below.
|Feature||Personal Edition||Contact Manager||Group Edition||Professional Edition||Enterprise Edition||Unlimited and Performance Edition|
|Active lookup filters per object||5||55||5||5||5||5|
|Custom fields per object||5||25||100||100||500||800|
|Custom big objects||100||100||N/A||100||100||100|
Info for table taken from official Salesforce limits document for Winter’ 18 release. More limits can be checked there.
- Check limits for rules, Apex triggers, Apex classes, and a code used in Setup -> System Overview page Business Logic section.
- Make sure your integrations are using a reasonable amount of API calls in API Usage section on the same page.
- Check if you have documentation for your customizations.
- Make sure that you are using one trigger per object according to best practice.
- Check if you are using some pattern for handling trigger logic in classes.
- Check the percentage of unit-test coverage. We recommend having >85% coverage.
- Check how your unit-tests are using asserts.
- Check if your unit tests are not failing.
- Check if your code is annotated and has commented.
- Run static code analysis tools like Checkmarx, Sonarqube or PMD.
- Check the sizes of methods. Ideally should be less than 100 lines each.
- Check the size of the classes. Make sure that you don’t have multi-thousand line classes.
- Check if pages are structured well.
- Make sure that you don’t have too many JS written in just <script> tags.
- Check state size of the most complex pages.
- Check load times of the most important pages.
- Check for cross-site scripting and SOQL injection vulnerabilities.
- Check if your pages have unused libraries.
- Check if images and scripts are size-optimized.
Process builder and Workflow rules
- Make sure you have these documented.
- Make sure your team is aware that creating those directly in Production can potentially cause conflicts with other automation and affect real data.
- Make sure you have a ground rule to execute unit tests after the creation of the process builder or workflow.
Development flow and automation
- Make sure you have guidelines for any customizations.
- Make sure peer or manager review process is working.
- Make sure you are using git (recommended) or any other source control tool.
- Check if you have considered using static code analysis.
- Check if you have considered using automatic tests.
- Check if you are using Salesforce DX or have considered using it.
- Check if you have some automation for deployments.
- Check loading time of the components using browser developer tools.
- Check if your components use data caching where possible.
- Check if your components use Lightning Data Service where possible.
- Check if your components have unused libraries.
- Check if images and scripts are size-optimized.
- Check your org and fix issues with Salesforce security check (Setup->Security Controls->Health Check).
Get the step-by-step free checklist
Download the step-by-step PDF checklist created by our experts` team, which you can use to implement a Salesforce health check independently.
Don’t miss any important areas that are necessary to check!
Save Your Time
Get free Salesforce health check from our team to find and diagnose problem areas of CRM in your company. In addition, you’ll receive recommendations on how to innovate to improve data quality and user experience.
What will you get as a result?
We will provide you with a customized Action Plan with suggestions of actions you have to take to fix your current pain points.
Just fill out the form below and we will contact you!