Ensuring CRM data quality – a three-step approach

Ensuring CRM data quality is a moving target. Opportunities and contacts are entered daily by many departments (e.g., sales, marketing, account management). This inevitably leads to duplicates and entry errors. On top of that, data becomes inaccurate over time (e.g., contacts change jobs and move to other companies).

This is not so much of an issue for a vanilla pre-sales CRM — as far as the sales funnel is accurate and quotas are met, managers are happy.

However, that changes radically when moving to post-sale world and adding more quote-to-cash functionality to the CRM such as CPQ, order processing, service management, billing etc.

Consider the following scenarios:

• Quote discounts depend on customer account tier, which is based on the number of active subscriptions and monthly recurring revenue
• Support case SLAs depend on total customer revenue
• Business requires reports on total opportunity potential per account, number of services per account and ARPU per account

All the above require a single account record per actual account.

Similar problems arise with contacts, leads and other types of CRM records and sooner or later data quality data becomes a challenge.

Three-step approach

Businesses grow over time: initially the sales teams are small and data is relatively clean. As more people are added to organizations, the quality of data naturally degrades (as mentioned earlier, time also plays its role).

Usually by the time organizations are ready to begin implementing quote-to-cash, a major data cleanup is required.

The cleanup method recommended by Nextian consists of three steps (in this specific order, as explained later):

Prevention

The first step is to make sure that no new bad data is entered and usually involves:

• Validating field syntax, e.g., phone numbers, email addresses, etc.
• Ensuring that unique fields (e.g., a FEIN #) have unique constraints
• Ensuring that required fields are identified and marked as required for entry
• Enforcing naming conventions and generate object names automatically wherever possible
• Adding validation rules (these may range from standard Salesforce validation rules to more complicated Apex code executed in triggers)
• Implementing duplicate prevention (e.g., Validity Dupe Blocker)
• Additional business-specific validations, for example, service providers or e-commerce companies that ship goods may require address validation

Initial cleanup

Unfortunately, there is no other method of cleaning the data other than going over it. Because of that, initial cleanup is usually pretty time-consuming. The good news is that it only has to be done once. Technically, the initial cleanup can be done in the following ways (from the least to the most effective):

• Using the CRM user interface and built-in merge function
• Creating a mirror database of the CRM (Skyvia or Heroku can be used for Salesforce), and then using database tools such as Excel or SQL queries for cleanup, followed up by a re-import of clean data to the CRM
• Using a specialized data cleanup tool such as Validity Demand Tools
• Creating custom data update scripts for complex problems

Maintenance

Even after the guardrails are in place, and the initial data cleanup has been completed, ongoing data maintenance will still be required.

The effort will depend on organization size and the amount of data. It may be a part time, a full time, or a team job. In any case, it is recommended to identify a person in the organization who owns data quality.

Conclusions

Ensuring data quality may require a lot of effort, however it does bring a lot of benefits:

• Improved decision-making (accurate data)
• Streamlined business processes (fewer errors)
• Increased employee productivity (trust in data)
• Improved customer experience

Nextian is a vendor of Quote-to-Cash (QTC) software for cloud and communications helping providers accelerate growth and increase customer lifetime value.

Contact us today to find out how we can help you!