If you are looking forward to enabling best practices in your new Salesforce Org or have a jumbled Org that you would want to improve, we’ve got you covered.  I have analyzed the parameters where the health of a Salesforce Org starts going wrong and have consolidated a list of actions that a Salesforce admin can make to ensure Org stability and performance are never compromised. 

  1. Keep a Track of the Object Model:

    Admins should have regular checks on the objects created within your Salesforce Org by running reports at quarterly/monthly basis. You should analyze the objects with maximum and minimum utilization. As a standard, objects with repetitive utilization of below 30% over a long time can be considered for a deep dive, where the impact of removing the objects can be made and the objects identified less useful, can be removed

  2. Deep dive into data points:

    Most commonly used objects like Account, Opportunities, Leads and Case generally have the maximum number of custom fields created. It’s not a scenario to see these objects reach maximum field cap within a few years of operation. Hence, it’s all the more important for an admin to keep track of reports on custom fields and picklist created on objects and identify alternative routes to record data instead of creating custom field every time

  3. Check the configurations:

    Your Org might have workflows, process builder flows and rules set up for purpose that does not apply anymore or maybe leading to dead ends/rework.  To know the health check score of your Org, go to Setup and run Health Check.  

Once the pain points mentioned have been identified, the recommended approach would be to start with removing the objects/fields and configurations in Sandbox.  After a successful correction in a sandbox instance, the optimizations can be accommodated in production. 

Manish T.
Latest posts by Manish T. (see all)