Professional Documents
Culture Documents
Best Practice Data Quality
Best Practice Data Quality
Best Practice Data Quality
Agenda
Business Driver
Best Practices Overview
Importance of Data Quality
Data Quality Management
– Data Culture, Analyze, Plan, Standardize, Clean & Enrich,
Integrate & Automate, Maintain
Analysts rate bad data as one of the top 3 reasons for CRM failure
Importance of Data Quality
The Cost of Bad Data
75% of
respondents
“ 75% of commercial businesses
believe that they are losing as much
as 73% of revenue due to poor data
quality
”Experian - QAS
U.S. Business Losing Revenue Through
Poorly Managed Customer Data
Data Culture
Analyze
Plan
Standardize, Clean & Enrich
Integrate & Automate
Maintain
Installing a Culture of Data Quality
1 2 3
Introduction
Introduction Adaptation
Adaptation Standardization
Standardization
Anything
Anythinggoes,
goes,adoption
adoption Recognize
Recognizeusage
usagetrends,
trends, Train
Traintotocommon
common« best
« bestpractices »
practices »
before data integrity
before data integrity Adapt
Adapt standards toreality
standards to reality
6 5 4
Automation
Automation Integration
Integration Reward
Reward // Repression
Repression
Make
Makeeverybody’s
everybody’sjob
jobeasier,
easier, Build
Buildtools
toolstotohelp
helpmulti
multi Reinforce
Reinforcebest
bestpractices,
practices,
and
and make the companymore
make the company moreefficient
efficient department
department tasks/ /processes
tasks processes with
with a carrotAND
a carrot ANDaastick
stick
Analyze: Data Profiling
Not valid
Not complete
Not standardized
Plan: Data Quality Management Strategy
Create your Data Quality Plan
Identify and Prioritize Goals
Define Reports and Dashboards
Find Sponsors and Owners
Establish Budget
Select Tools (i.e. for De-Duplication)
Commit Resources
Create Communication Plan
Provide Rewards and Disincentives
Standardize, Clean & Enrich
1 2 3 4 5
Standardize
Standardize Cleanse
Cleanse Enrich
Enrich(Optional)
(Optional) De-dupe
De-dupe Validate
Validate
Names Find & Company Identify, Load to
Replace Name & Address Match & Score Sandbox
acme incorp.-> Acme Inc Hot High J. Smith, John Smith –
Cold Low 80%
Archiving &
Filtering
Standardize
Create naming conventions and data standards and train all users
Enforce standards with validation rules and pick-lists
Implement procedures to standardize data before mass-importing
Examples:
– Accounts names: Inc vs. Incorp., INC, incorporated; Ltd vs LTD, Limited
– Opportunity names: i.e. Name – Product: “Acme – 250 Tschotchkes”
– Country/State: use validation to standardize TX vs Texas, USA vs. U.S.
– Postal Code: use validation rules for proper format in US/CAN: xxxxx-xxxx
– Contact info: use pick lists for roles, titles, department: Marketing vd. Mktg
SFA
Internet
Data Enrichment
– Product Master
A comprehensive family of technologies built on top of the Force.com Web Services API
1 2 3 4 5
Native
Salesforce Native ERP Integration Developer
Desktop
AppExchange Connectors Partners Toolkits
Connectors
Automate
Salesforce.com partners can help!
– Leverage 3rd parties such as D&B, Hoovers and others to periodically import and
automatically update account records
– Inside Scoop or other partners to augment and cleanse information
Composite Apps
• Enterprise Mash-ups
• Rich user interface Scontrol
Application
Integration
• Real-time integration
•Multi-step integration
• Human workflow
Data Integration
• Data migration
• Data replication
• Bulk Data Transfers
Data Cleansing
• Data de-duplication
• Data assessment
Data Quality Management Best Practices
Native tools for managing data quality
Web-to-X Excel Connector Data Loader
Analyze and cleanse
data
Train
Train Enforce
Enforce Monitor
Monitor
“ Data quality decays rapidly & enterprises should follow a methodology that
includes regular measurement of data quality with goals for improvement &
deployment of process improvements & technology
”
Maintain Data Quality: Train and Communicate
Note – if you have not done this type of work before, it is challenging.
Data Considerations
– When importing the data into the master Account, map the Account Id to the OLD
ACCOUNT ID field
– You will then be able to export the new Account Id, OLD ACCOUNT ID and
Account Name to act as your mapping table
Data Considerations
Created Dates
– All records imported/migrated will have a Created Date = to when the import occurs
– To retain original dates, create a custom field to import into (i.e., Original Create Date)
– If you are updating via the API, the new 7.0 version will allow you to set the Created and
Last Modified Dates: http://www.sforce.com/resources/tn-17.jsp
Note: You must contact Salesforce support to enable this feature.
History Tables
– Stage History for Opportunities / Case History for Cases
– Data cannot be migrated into these tables, this information must be stored elsewhere if
you bring it over (“Note” field is not Reportable, so custom field is recommended)
– Merged
• There is no way to “un-merge” data
• Clean up/work with merged records, OR
• Delete and restore from back ups
– Imported incorrectly
• Mass transfer (if you can)
• Delete and re-import into proper area
• Consider tagging batches with a custom field indicating the load/batch
number in case you need to reverse
Advanced Data Quality