Data2CRM, an automated CRM migration service introduces a new feature - record deduplication, allowing users to choose one of the three dedupe approaches.
Online PR News – 16-November-2015 – Ternopil, Ukraine – CRM systems are widely used to help businesses optimize the workflow and gain a comprehensive view of their customers and prospects. However, these platforms may fail to perform as expected and even do harm, if the data residing in them is poorly organized and duplicated.
Bad data may come from various sources, including integrated third party applications, systems with bugs and even CRM users themselves. Therefore, some level of duplicate records is present in virtually every CRM system.
To help businesses avoid the headache of dealing with duplicated entities after the CRM switch and turn the migration into a real chance to put the data back into an optimized state, Data2CRM has launched a new deduplication feature. The option includes three possible strategies to choose from, and allows to either replace, merge or leave all clone records on the user’s CRM system during the process of data transfer.
Peculiarities of Data Deduplication with Data2CRM
Here are a few points necessary to know about Data2CRM deduplication procedure:
- The feature is optional and can be selected during the full migration only;
- Entities available for deduplication are accounts, leads and contacts;
- The tool will check for duplicated records both on source and target CRM platforms;
- There are two criteria for detecting duplicated records in the system - ‘email’ and ‘name’;
- During the migration users can choose only one duplication criteria (‘email’ or ‘name’) for each selected entity (account, lead, contact). For example, it is possible to dedupe accounts and contacts by name, while leads by email or vice versa.
Such a flexible feature architecture enables users to fully tailor it to their needs. Moreover, multiple deduplication approaches allow to receive an optimal migration outcome. Let’s examine them more carefully as well.
There are three deduplication strategies to choose from:
Replace. In case the user has identical entities on the source and target platforms, choosing this strategy trigger the service to substitute the entity on target CRM with it’s clone from the source system.
Example: Both target and source systems have accounts with the name John Doe. During the migration with “replace” deduplication strategy the service will overwrite the the information about the John Doe account on the target with the data on this account from the source.
Merge. As the name of the approach suggests, it allows to merge the identical records form the source and target, keeping the additional fields from both.
Example: An account John Doe has the field email email@example.com on the source and the field website www.johndoe.com on the target. After the migration an account John Doe will have both fields - email and website.
Note, the source records are prioritized, so if both source and target have the field email, the system will keep the data from the source CRM.
Leave. This strategy prioritizes the data from the target platform and migrates only those records that don’t already have duplicates on the target.
Example: Both target and source systems have accounts with the name John Doe. The system will leave the account on target unchanged and won’t migrate the John Doe account form source.
To transfer CRM data with the new deduplication feature, go to Data2CRM website and start setting up you fast and reliable migration right now!