Unifying CRM Data For a Single Version of Truth
In episode 49 of the “Inside Dynamics Communities” podcast, Ryan Gonzales, Senior Sales Director of Dynamics Communities and Summit NA, and Pam Misialek, Community Director of Dynamics Communities and Summit NA, are joined by Conor Doyle, Head of Sales, DQ Global, to discuss the importance of unifying data, especially in a CRM system, to get a single version of truth.
This episode is sponsored by Community Summit North America, the largest independent gathering of the Microsoft Business Applications ecosystem, taking place Oct. 13-17, 2024, in San Antonio, Texas. Register today to connect with thousands of users across the Microsoft business applications ecosystem at the for user, by user event.
Key Takeaways
- Overview of DQ Global: DQ Global assists organizations in managing and maintaining data within their business applications, ensuring it is fit for use and reducing manual data manipulation frustrations, ultimately saving time and resources.
- Challenge of data overlap: Conor shares details of a customer DQ Global assisted with unifying its data. The company faced challenges with data overlap and trust issues due to acquisitions and segmented business units, which led to multiple entries for the same entity in their CRM systems. The solution involved unifying data in Dynamics 365 Sales, emphasizing the importance of data trust and a single version of truth, while acknowledging that perfect data is an unattainable ideal due to economic constraints.
- Data quality: Improving data quality is an incremental journey, not a straight climb to perfection; it involves a series of steps that collectively enhance data over time, despite its inherent messiness, risk, and complexity, explains Conor.
- System migration: Conor shares a few tips for companies who are considering migrating – or consolidating – their ERP systems. First, understanding your current position and destination is crucial for mapping the journey of data migration, as it involves aligning tables and fields to the target system’s requirements, which may differ in data types. Second, ensuring a clear target to aim for and prevent the process from falling apart.
