As your business grows, so will your Org. And while a highly customized Salesforce Org reflects a booming business, there’s a critical difference between necessary complexity and technical debt.
In the spirit of spring cleaning, we wanted to share a few best practices for deep cleaning your Salesforce Org — not just the data, but customizations and metadata supporting it, too. Both go hand-in-hand in improving usability and adoption.
For the first part of this post, we’re drawing from an excellent entry in the Salesforce 360 Blog on ‘dirty data’ in CRM records. Then, we’ll look at metadata, and share some tips for deprecating unused customizations that may be complicating your quest for cleaner data.
What Is ‘Dirty Data’?
“Dirty” CRM data is, effectively, anything that prevents your team from using the system efficiently. This can mean data that is:
- Out-of-date or irrelevant, often due to an acquisition, staffing change or any other type of broad business change
- Incomplete or missing key fields, usually due to a user omitting critical information
- Duplicated in multiple places — what the Salesforce team calls “confetti data”
- Inaccurate, like a contact record from a web form where someone has inputted a fake email
These types of things are common in any CRM. But over time, they build up and cause problems ranging from minor nuisances — a sales exec has to hunt to find the correct contact info for a prospect — to more significant problems around reporting. For example, if you have an opportunity pipeline with duplicates or inaccuracies, that can affect close rates, attribution, and other critical metrics for your teams.
Eventually, enough complexity can actually slow down the performance of your Org — something that affects all users and can impact adoption of the system.
The Road Map to Clean CRM Data
Salesforce proposes a three-step ‘road map’ to cleaning up CRM data:
- First, map out your current data processes. This involves looking at the fields in your system, and identifying what they mean and whether they’re being filled out consistently.
- Then, complete an assessment to determine which fields are actually meaningful to your processes and reporting, and which can be archived. The fewer fields you have, while still capturing the information you need to work efficiently, the easier it will be to keep your data clean.
- Finally, share recommendations with leadership and team members. Make sure you can get buy-in from both users and management — when everyone’s on the same page, it will be easier to make the changes you need to make.
Tip: If you're looking to clean your data from the ground up, consider implementing Salesforce data classification — as a tool, data classification helps organize and facilitate proper security protocols on sensitive information. Learn more about data classification in Salesforce here.
What About Metadata?
Clean data is critical. But getting it requires making sure the system is customized properly. That’s where metadata comes in.
Salesforce Ben has a useful primer on the distinction between data and metadata. Basically, data is the individual records your business relies on — users, accounts, contacts, etc — and metadata is the encoded structure of your Org that controls what you can see and enter into the system.
Why Is Metadata Important?
When you can control how things go into the system, you can shape the quality of what goes into it. Eliminating an unnecessary field on the contact object can give your sales team more effective, actionable information to work with.
The caveat is that cleaning up metadata is more complicated than cleaning up data — seemingly simple changes can have unintended consequences. That field may not look like it’s being used, but it could connect to an important report or automation.
So there’s more risk involved in streamlining your metadata. But the good news is that doing it safely boils down to a few core principles.
Think Before You Build
You can avoid the need for metadata clean-up altogether by taking a more thoughtful approach to development. Before creating a new customization, think if there’s something already existing in the system already that can be modified instead. Salesforce’s ‘low-code’ platform makes it quick and easy to build new customizations, but the downside is that it can easily lead to over-engineering and technical debt.
While this will help ensure your Org stays streamlined as you move forward, it doesn’t solve the problem of existing complexity. So before you start on a major cleanup project, there are two things you’ll need to have in place.
Before deleting any customizations, it’s critical that you check what dependencies are sitting on them. You never know what fields, picklists, or records might be affected.
Strongpoint’s Dependency Relationship Diagram tool is great for doing just this. You’ll find the DRD in our free Flashlight app, or in our enterprise-level Documentation and Optimization product, where it comes with a wide range of tools for automating the cleanup process.
It makes sense to monitor who is building what and who can make changes in your Org before starting a cleanup project. Creating a system for tracking user activity and access controls will help add a layer of governance to your change process.
If you have a lot of development activity in your Org, setting up a formal change management system — alongside or in lieu of a ticketing system like Jira or ServiceNow — is the best way to maintain accountability and transparency when cleaning up, deprecating or altering any customizations.
Want more resources on streamlining your Salesforce Org? Watch a webinar covering some of the topics we discuss in this post, or better yet, get in touch to book a consultation and see if there’s a place for Strongpoint in your project:
Want to keep reading?
Click here to find out why data governance in Salesforce matters — or download your free eBook to learn more about SOX compliance in business-critical applications.
We've partnered with Moss Adams for this quick guide to determining what's in scope and what type of control environment your auditors will expect to see.