The General Data Protection Regulation came into force in May 2018! We have all heard about this, and hopefully, your GDPR project is in place.<\/p>\n
As stated in the previous blogs you have probably read on this subject, GDPR is all about<\/strong> putting individuals in control of their data<\/strong>. That is why the principles stated in Article 5 are so important and why the Lawfulness of Processing and the rules around Consent must be implemented and tested as soon as possible.<\/p>\n Most organizations will have policies already in place that cover at least part of these requirements, but they often fail without anyone realizing it, due to the common problem of having duplicate data in their CRM system.<\/p>\n Having only one record for each person simplifies everything. Even before data protection was a hot topic, duplicate records were an operational nuisance, but now that nuisance can pose additional challenges.<\/p>\n Let\u2019s look at a few scenarios where having a duplicate-free CRM system can help any organization comply with GDPR. We will use our favorite example, customer Robert Dixon<\/strong>, also known by some team members as Bob Dickson<\/strong>.<\/p>\n Below are four of Robert\u2019s rights regarding his personal data, all of which will be much easier to respect if his details are in the system only once.<\/p>\n 1) Know what information you hold on him and what for: 2) Keep his personal information updated and accurate:<\/strong> 3) Have his information deleted when no longer necessary: 4) Only send him emails if he has subscribed to them<\/strong> We strongly recommend all our customers audit their CRM data for duplicates, from time to time. The frequency of these audits depends on what data sources they have and the rate of change. But regardless of those factors, for GDPR purposes, you should do that right now and know where you stand. By the way, we have a free solution for that.<\/p>\n The free trial we offer on Paribus 365<\/a> will give you a report of how many duplicates you have. If you are not sure about the size of the problem, or even if you have one, install it today and run it on your system. It won\u2019t cost you a penny and you can use it on any database for reporting purposes.<\/p>\n This solution was originally developed to identify and merge data in CRM systems. Although you can use it on any database to learn how many duplicates you have, it will only merge those duplicates inside CRM systems, namely Microsoft Dynamics 365 CRM, Microsoft Dynamics CRM, and Infor CRM (Saleslogix). The free trial<\/a> version for Microsoft Dynamics 365 CRM will let you merge some of the results so you can see exactly how it works.<\/p>\n To learn more about this solution, please visit the\u00a0website<\/a> or get in touch<\/a>.<\/p>\n Disclaimer:<\/strong> the content of this blog does not constitute and cannot be seen as legal advice, and should not form the basis upon which any person or organization takes a decision or reaches a conclusion in regards to their rights or obligations.<\/p>\nWhy is duplicate data a problem for GDPR compliance?<\/h2>\n
\n<\/strong>You informed Robert Dixon of what data you hold, in compliance with the regulation; the problem is that part of that personal data is registered under Bob Dickson, and you didn\u2019t even know such person existed in your database. However, one of your employees calls Bob every now and then, and while doing so, he may be looking at a different set of data.<\/p>\n
\nYou have updated Robert\u2019s address as requested, but not Bob\u2019s. Remember, you never met Bob, but for some reason someone in your team created that contact and uses it regularly. If that person needs to send Bob a letter, it will be sent to the wrong address. Not to mention that the information on that letter may be confidential, and you\u2019re sending it to someone else\u2019s house.<\/p>\n
\n<\/strong>Whether you are doing this proactively as part of your data management policy, or because Robert asked you to, having more than one record means that you will still hold Bob\u2019s data, even after you deleted Robert\u2019s. The problem is that they are the same person.<\/p>\n
\nTwo months ago, Robert gave you consent to send him your newsletter, and you can prove it. But that subscription is logged against Robert\u2019s contact in CRM, not Bob\u2019s. They are the same person, but one of the demands of GDPR is that organizations must be able to prove that such consent was given, and you can\u2019t prove that Bob has given his consent. The same goes for William and Bill or William at QWARE and William at Q-Ware. He\u2019s probably not the only person registered several times under slightly different names or account names, is he?<\/p>\nFind out how many duplicates you have<\/h2>\n
Share this:<\/h3>