On a very entertaining fireside chat webinar (hence the animated GIF) with Salesforce MVPs, Steve Molis and Michael Farrington, we learned that bad data not only has a lasting effect on Salesforce, but it also impacts the daily job of Salesforce admins.

7 Funny Yet True Sayings About Bad Data from Salesforce MVP SteveMo
Steve Molis, aka SteveMo, is also a long-standing Salesforce admin, and to be cordial, let’s just say he despises bad data.

Hang on to your Duraflames because here are some of the hilarious dirty data sayings from SteveMo from this fireside chat.

“Bad data is the fruitcake nobody eats.”

Fruitcake gets put in the corner. Nobody serves it. Everybody hates fruitcake and everybody hates dirty data. As SteveMo shares, “At least fruitcake is good for re-gifting. You can’t re-gift dirty data.”

“Duplicate data is like the cholera of sh$!ty data.”

Letting duplicates in the virtual front door is bad on so many levels. It doesn’t’t matter what your model is or who you’re selling to, you can’t let it enter your system.

“Once you let the duplicates in, you are forever playing duplicate whack-a-mole.”

Let’s say you let duplicates into your database because sometimes, the duplicate doesn’t announce itself as a duplicate. Sometimes the differences are more subtle, such as a regional address instead of an office address, therefore, nobody notices and the duplicate sits around. With all of these opportunities for duplicates to come in, you’ve got to put up that firewall.

“What’s worse than a duplicate? A triplicate.”

Duplicates don’t just affect the admin, they affect every user of the CRM. And it affects every role within the organization. It affects sales. It affects client services. It affects marketing. It touches so many users.

As an admin, duplicates make your job so much more difficult. Whether it’s a file to load, updates on contact data, or new account data, if you’ve got five instances of every account, your duplicate data is affecting everyone touching that account.

“Don’t do the dreaded ‘Stare and Compare’.”

Dump all of your Salesforce accounts, contacts, and leads into a spreadsheet. Then, sort that spreadsheet by name. When you go through and mark the potential duplicates, you’ll run into messy, unorganized issues. That’s the time-wasting activity of “stare and compare.”

Your data is not going to be lined up all nice and neat in that spreadsheet. There could be hundreds of rows, and unless you’ve got a photographic memory, you might not remember all the non-standardized information.

“I don’t know what circle of hell bad data may be, perhaps it’s the third or fourth, but no matter what, who wants to live like that? No one.”

With crappy data in your database, it’s hell on earth. What is a Salesforce admin’s real role? They’re not running the Salesforce org for themselves. It’s all for the users. And happy users make a happy admin. If your users are trudging through because there are duplicate contacts, duplicate leads, etc., it won’t be a good day…or month…or year.

The users are impacted by dirty data on a day-to-day basis. The users are logging in to Salesforce and experiencing it everyday. The users are working off a contact list or a lead list and making calls. Depending on your org-wide default sharing settings, users across your organization might be impacted by duplicates and not even know it because they don’t see that duplicate in front of them. Think about that.

“You’ve got to nip that sh$%t in the bud.”

You’ve got to attack duplicate data on two fronts. First, if you let the crappy data in, merge it. Second, shut off the flow of that duplicate data. You stop it as soon as you possibly can and you do that at the lead contact level. You do it as soon as they’re ready to add a new record in Salesforce. Stop it at the entry of a new lead, new account, and new contact. According to SteveMo, “That’s where you’ve got to nip that sh#%t in the bud.”

Watch the full webinar here:

Get more tips to stop those pesky duplicates with the free ebook below.

7 Funny Yet True Sayings About Bad Data from Salesforce MVP SteveMo

Leave a Reply