GDPR in Microsoft Dynamics 365 Customer Engagement, Why Data Quality?
Ensure your data is correct – this is broad but needs huge consideration.
Standardise records as much as possible, ensure the spelling is correct, dropdowns are used when possible.
Duplicates – deduplication and merging. Duplications of data can cause huge problems when it comes to GDPR as the consent may differ on both the personal records. These need to be captured and corrected as soon as possible. Merging records in CRM solutions can be achieved by clicking the wizard buttons but does need some input.
Identify and deactivate old records. Within the new GDPR law is the “right to be forgotten”. The ICO outlines 6 different scenarios but for this purpose, we can focus on “Where the personal data is no longer necessary in relation to the purpose for which it was originally collected/processed.” Please also see the timescales the ICO refers to of keeping hold of information.
Validation – ensures that data is correct by checking addresses and phone numbers. Again, a time-consuming job but valuable within the GDPR guidelines.
Enhance data – add missing information. For example, are the counties in the same format across your system? Can you use your data in the best way possible? Keep in mind that GDPR also says: that data should only be collected for specified, explicit and legitimate purposes and cannot be processed if it isn’t in-line with those purposes.
Suppression records – consent records have they given permission, what channels are these? Is your CRM system set up to capture the consent explicitly?
In writing this post l am looking to raise awareness for key GDPR Considerations and would like to also make you aware that l am not a GDPR lawyer/solicitor but looking to ensure we all take the necessary steps on your GDPR journey