Export / Import Duplicate Check configuration

The new Export / Import feature in Duplicate Check allows you to transfer entire configuration sets between different Salesforce ORGs. For example, create an entire configuration in a sandbox and transfer it to production with just a few clicks. Or, create a regular backup for your DC configuration. Better be safe than sorry!
Export / Import Duplicate Check configuration is only available in our Premium Edition.

Step 1 Export a DC Configuration file


1. Navigate to DC Setup - Import / Export Configuration. 
2. At the "Export" tab, click "Export Configuration". 
3. The configuration file is now downloaded to your hard drive. 
What is part of the export file? 

- The export file will consist of the DC Setup configuration for all defined objects (scenarios, object settings, merge rules, direct processing, cross object mapping, predefined filters, record type configuration).

- All settings defined at General Setup - Settings

- Frequent words lists at General Setup - Frequent words

- Changes made in standard Salesforce will not transfer and have to be reconfigured.

Step 2 Import a DC configuration file


1. Navigate the DC Setup - Import / Export Configuration
2. At the "Import" tab, select a config file and click "Import Configuration". 
3. That's it! If all went well, your will receive a notification. If there are any errors, you will be notified as well.

Most common error & warning messages


Message Solution
Object not found [x] The import fails because you are trying to import a configuration for an object that does not exist in this ORG. 
Convert Status does not exist The import fails because the config file contains a defined convert status that is not found. Make sure the convert status is added to the Lead Status field. More info.
You are trying to import [x] scenarios in an object, where the license only allows for [y]  The import fails because you are trying to import more scenarios than allowed according to your Duplicate Check license. Find more information at DC Setup - License. Make sure your license is applied correctly or contact support
Field not found for object [x] in scenario [y] The scenario that you are trying to import has a defined field that does not exist in this ORG.
Field not found for object [x] in result fields The imported config file contains a result field that does not exist. 
Record type not found for object The config file contains a record type configuration for a record type that does not exist in this ORG. 
Field not found for object in cross object config The cross object mapping that you are trying to import has defined a field that does not exist in this ORG. 
Pick-list value in field does not exist There is a merge rule, object filter or pre-defined filter that is based on a pick-list value that does not exist in this ORG.  
Invalid configuration file The file that you are trying to import is invalid.  
The master record rule for [x] is configured using a reference field, but the ID can’t be found. This has to be reconfigured manually. At the Merge Rules tab, the master record rule is depending on a reference that can't be found in your current ORG. Therefore you have to reconfigure the master record rule.  
The object filter for [x] is configured using a reference field, but the ID can’t be found. This has to be reconfigured manually. The import file contains an object filter which is based on a reference that can't be found in your current ORG. Therefore you have to reconfigure the object filter. 
Predefined filter [x] is configured using a reference field, but the ID can’t be found. This has to be reconfigured manually. The import file contains a predefined filter which is based on a reference that can't be found in your current ORG. Therefore you have to reconfigure the predefined filter manually. 
 

Having trouble?

Our support agents are ready to help you !