The Paribus 365™ Data Cleansing process

The Paribus 365™ Data Cleansing process is achieved in three simple steps.

1.  Set Matching Criteria

The first of which is to easily define the matching criteria by which to identify duplicates within Dynamics 365 CRM.

Paribus 365™ Duplicate Data Matching

• Search for mass duplicates within Dynamics
• Match duplicates using multiple fuzzy match criteria
• Set each match criteria to a given match score threshold
• Match upon any entity data items including custom data
• Filter the Paribus matching process to only match upon sub-sets of data
• Match upon both one-to-one and one-to-many data item

2. Review Paribus 365™ Matching Results

Once Paribus has identified duplicates within Dynamics 365, the Paribus 365™ Data Cleansing process provides the ability to review the results before merging.

This important element of the process confirms your approval and always ensures you remain in total control of your data.

Paribus 365™ Duplicate Data Review

• Review duplicates side-by-side to ensure they are valid duplicates
• View multiple data items (including custom data) to assist side-by-side comparison
• Allows for mass review and approval of duplicates
• Include/exclude duplicates from results and merge processing
• Promote selective entities to become the surviving master entity (post the merge)

3. Merge and Consolidate Duplicates

Once the identified duplicates have been reviewed and approved, the Paribus 365 duplicate merge process can be used to merge and consolidate Dynamics entities.

This automated merge process removes the need for tedious, user intervention and likely possible human error.

Paribus 365™ Data Merging Capabilities

• Merge duplicate Dynamics 365 entities
• Consolidate all associated data
• Achieve a single surviving master golden record (Single Customer View)
• Remove or hide (deactivate) duplicate entities
• Save precious time automatically merging duplicates on-mass
• Support for custom data merge processing and analysis
• Merge processing achieved using Dynamics non-interactive user (higher daily transaction/API limits)