How to configure state field mappings in Cognism

Map state values from Cognism to your CRM

This article explains how Cognism admins can configure state field mappings so state values exported from Cognism match the picklist values used in your CRM.

State mapping can be configured for Leads, Contacts, and Accounts.

How state field mapping works

When exporting data from Cognism to your CRM, the State field is mapped based on the rules you configure.

By default:

• State is mapped for Leads and Contacts  
• Company HQ State is mapped for Accounts  

These values map to your CRM’s State picklist field. You can customise this mapping to ensure exported values align with your CRM configuration.

Configure state field mappings (admin)

Only Cognism admins can configure state field mappings.

Open field mappings

1. Go to Settings > Integrations.  

2. Select Configure next to your connected CRM.  
3. Open Field mappings.  
4. Select Lead, Contact, or Account, depending on the object you want to configure.  

Define state mapping rules

1. Locate the State (or Company HQ State) field.  
2. Select Advanced.

3. Choose how Cognism state values should map to your CRM picklist values. 

4. Select Add field to map additional states.  
5. Select Save.  

Saving behaviour depends on your CRM:

• Salesforce: select Save in the popup only  
• All other CRMs: select Save in the popup, then select Save again in the bottom-right corner  

Important considerations

• If you map a state, you must also map the corresponding country.  
• If a state value is not mapped, it is exported without a value.  
• State mapping applies only to the supported countries listed below. 

Supported countries

State mapping is supported for the following countries and regions:

• United States 
• Australia 
• Austria 
• Brazil 
• Germany 
• India 
• Malaysia 
• Mexico 
• Canada (provinces and territories) 
• United Kingdom (countries within the UK) 

Expected results

After configuration:

• State values exported from Cognism match your CRM picklists 
• Data imports remain consistent and clean 
• CRM workflows relying on state values continue to function correctly 

Next steps

• Configure country field mappings  
• Review other conditional field mappings  
• Test exports to confirm expected behaviour