Rules (Convert): Selecting Values for Convert

Overview

When converting records, Cloudingo uses the native conversion process in Salesforce. Converts will behave the same way they do when initiated on the Salesforce side. However, Cloudingo’s convert rules allow for configuring logic to choose values to override the existing Contact or Account data during the conversion process. With a normal Salesforce convert, overrides are not possible. Exception rules can also be configured to skip automatic conversions on certain records.

Navigation

1. Open the Manage Rules window: Choose the ‘Tools’ → ‘Convert’ → ‘Rules’ option in the left-hand-side navigation window.

   

   1. Choose ‘Create Rule’ to build a new custom rule.

   2. Choose ‘Edit’ next to a specific rule to edit an existing rule under the ‘Actions’ column.

      

2. Access a rule setting from within the Merge Preview page for easy and quick editing while viewing results for accuracy.

   1. Choose 'Edit Rule Settings' option from within the Merge Preview page.

      

Step 1: The Basics

1. Source Object: Choose the Lead object (this is not editable if editing an existing rule).

2. Target Object: Choose either Contact or Account for the object. Choosing Contact will work with Lead to Contact filters while Account will work with Lead to Account filters.

3. Rule Name: Give the rule a descriptive name.

4. Description (optional): Give a brief description of the rule.

5. Apply owner mapping during convert: Choose this option to apply Owner Mapping to reassign record ownership from inactive or queue owners to new owners during merge/convert.

Step 2 (optional): Group Fields

1. Set up any field groupings to group/link field values together. This works similarly to the merge rule field grouping. 

   1. The exception is the Lead fields must be mapped using the 'Map Grouped Fields' option (the button is the last option in the field grouping rule). 

      1. The fields initially configured in the drop boxes will be Contact fields.
         

         

         
         
         

2. Choose the 'Add Field Group' option to add a field grouping. Multiple groupings can be configured.
   

   

Step 3: How do you want to merge records?

Lead to Contact or Person Account

Account Creation

Tell Cloudingo how to create Accounts if converting Leads into a Contact record that does not have an Account assigned.

1. ‘Do not create an account automatically’:
   
   

   

   
   
   

   1. This is the native way Salesforce handles conversions therefore the default setting.

   2. Convert process will fail when a Lead attempts to convert into a Contact without an associated Account.
      
      

2. ‘Create an account automatically using the name’: The convert process will create a new Account and convert all Leads into the user-defined Account Name.
   
   

   1. Type in the desired Account name.
      
      

      

      
      
      

   2.  Or use the Lead Company name to create new Accounts.
      
      

      1. Choose the ‘Add Field’ option to choose the ‘Lead’ object and choose ‘Company’ then choose ‘Add’.
         
         

         

         
         
         

3. ‘Assign Contact to existing Account’: Convert process will convert all Leads into an existing Account if one exists and create a new Account if one does not exist.
   
   

   1. Type in the desired Account name to convert into a specific existing Account.
      
      

      

      
      
      

   2. Or use the Lead Company name to search for existing Accounts with the same name.
      
      

      1. Choose the ‘Add Field’ option to choose the ‘Lead’ object and choose ‘Company’ then choose ‘Add’. 

         1. If a matched Account Name is identified, Contacts will be created under the identified Account.
            
            

            

            
            
            

      2. ‘If Account name not found’: When using the 'Assign Contact to existing Account', an option must be configured for scenarios where a matched Account cannot be found.
         
         

         

         
         
         

         1. ‘Do not create an account automatically’: Convert process will fail when a Lead attempts to convert into a Contact without an associated Account and when the Lead Company name does not find a matching Account Name.

         2. ‘Create account automatically using the above name’: Convert process will create a new Account using the Lead Company name if an existing Account with the same name is not identified.
            
            

Update Contact Field Values

The Contact record is always the master record. Set up rules to define how to pull specific field values during conversion. Rules can potentially override existing Contact Field Values.

To create field rules:

1. Choose the ‘Map same fields automatically using default rule’ to add a list of pre-set field mappings. 

   1. Rules will be created based on the rule chosen for all fields that contain the same name in both objects. Check the box again to remove the added rules.

2. Click the ‘Add’ button in the middle section.

3. Choose a field in the ‘Target Field’ drop-down (standard or custom field). Target fields will populate from the Contact object. 

   1. This drop box is searchable if typing in a full or partial field name.

4. Choose a field in the ‘Source Field’ drop-down (standard or custom field). Source fields will populate from the Lead object. 

   1. Fields must be mapped between the Contact & Lead so that Cloudingo knows which data to compare to identify matches.

5. Choose a rule to determine how the value gets chosen during convert. See more details on Rule options in the Creating & Managing Merge Rules article.

6. Choose an override to determine how the value will be handled during convert. See more details on override options in the Creating & Managing Merge Rules article.
   Convert specific details are provided below.

   1. ‘And always override master with a value’:

      1. Cloudingo evaluates all records in both objects (Lead & Contact) to determine which value gets set.

      2. This option does not always take the lead value and override the Contact value.

   2. ‘And always override master even with a blank’:

      1. Cloudingo evaluates all records in both objects (Lead & Contact) to determine which value gets set.

      2. This option does not always take the Lead value and override the Contact value.

   3. ‘And override master when blank’:

      1. Cloudingo overrides the Contact with the Lead data only if the Contact value is blank.

      2. Salesforce Lead Mappings (on the Salesforce side) are still honored during the Cloudingo conversion. This option is only necessary if a field mapping in Salesforce does not already exist, and if filters identify multiple Leads to convert with a Contact and a rule is necessary to determine which Lead value to pull from.

   4. ‘And never override master’:

      1. Cloudingo will always retain the Contact value.

      2. By default, Cloudingo will never override the Contact value even without a rule. This option is not necessary for retaining Contact values, but can be used if needed to set up a rule to perform an Action without impacting the Contact field value.

      3. Salesforce field mappings cannot be bypassed. Blank values may still get overwritten if mappings are configured on the Salesforce side.

   5. ‘Ignore master value’:

      1. Cloudingo will choose the Lead value and always override the Contact.

      2. This option does not look across both objects (Lead & Contact) to apply the rule. Cloudingo will only look at Lead records to process the rule selected.

7. Choose a tiebreaker if Cloudingo indicates that the ‘And break ties with’ setting is required. 

   1. Tiebreakers are only required on certain rules. More information regarding tiebreakers can be found in the Creating & Managing Merge Rules article.

8. Set up Options settings if Cloudingo indicates that a setting is required. 

   1. Options are only required on certain rules. More information regarding rules and options settings can be found in the Creating & Managing Merge Rules article.

9. Set up Actions settings as desired. More information regarding Actions settings can be found in the Creating & Managing Merge Rules article.

Exceptions

1. Set up an Exceptions to skip automatic conversions on certain records.

2. ‘Target’ record = Contact or Account record in the definitions below.

3. Exception options include:

   1. Group when NO value exists for the resulting target record for field (needs field mapping)

   2. Group when one or more records is protected

   3. Group when same value does not exist in all records (Blank not treated as a value)

   4. Group when Value exists in more than one record

   5. Group when Specified Value exists in more than one record

   6. Group when record has less than X% of the fields with values

   7. Group when its size is >=X

   8. Group when its size is <=X

   9. Source Record when Record has any value in field

   10. Source Record when Record has specified value in field

   11. Source Record when Value does not match target record for fields (needs field mapping)

   12. Source Record when Value does not match target record (blank value is matched, needs field mapping)

Lead to Account

1. Steps 1 and 2 are the same process as described in the Lead to Contact section above with the exception that rules are configured on Account object fields rather than Contact object fields. Field rules will override the Account object data, not the Contact object data.

   1. Field rules update Account field values with every Lead conversion performed.

   2. Field rules are rarely used for Lead to Account conversions.

   3. Field rules do not apply to Contact values. Salesforce field mappings control which data carries over to the created Contact record.

2. In Step 3, tell Cloudingo how to assign ownership and Contact record type on newly created Contacts.
   

   1. Assign all newly created Contacts to the Account Owner.

   2. Assign all newly created Contacts to the respective Lead Owner.

   3. Choose the desired Contact record type for newly created Contacts.

      1. This option will only appear if record types are enabled in the Salesforce org.

      2. If left blank, Cloudingo will not send a specific record type value to Salesforce (defaults will apply).

Step 4: Additional Convert Options

1. Choose a ‘Converted Status’ to default to all conversions.

   1. Convert Status options pull from Salesforce. The list will include Lead Status’ configured as a convert status option.

   2. To exclude Cloudingo dedupe conversions from Salesforce Conversion Reports, consider setting up a new convert status and assigning it to the Cloudingo defaulted status. Then, exclude records with that status from the Convert reports.

2. Create Opportunity: By default, this option is disabled. This is because dedupe conversions are not typically part of a Sales cycle, but rather cleanup efforts.
   
   When enabled:

   1. Specify the desired Opportunity Name.

      1. Set a specific value to be applied to all converted records.

      2. Or use the lookup by selecting ‘Add Field’ and choosing which Lead or Contact/Account field(s) to pull the value(s) from.

         1. Contact fields will be available for Lead to Contact rules and Account fields will be available for Lead to Account rules.

         2. Multiple fields can be used to form the name. ie: {src:FirstName} {src:LastName} will pull the Lead’s first and last name for the Opportunity record creation.

         3. Be sure and type in spaces between the lookup fields as necessary.

   2. Choose the desired Opportunity Record Type for newly created Opportunities.

      1. This option will only appear if record types are enabled in the Salesforce org.

      2. If left blank, Cloudingo will not send a specific record type value to Salesforce (defaults will apply).

3. Send email to owners: By default, this option is disabled. This is because dedupe conversions are not typically part of a Sales cycle, but rather cleanup efforts.

4. Create Task: By default, this option is disabled. This is because dedupe conversions are not typically part of a Sales cycle, but rather cleanup efforts.