Configure State Field Mappings for CRM Exports

Configure state field mappings to ensure state and province values exported from Cognism match the values used in your CRM.

This helps prevent validation errors when exporting records to CRM fields that use predefined picklist values.

Before you begin

Before configuring state mappings, ensure that:

• You are a Cognism administrator.
• Your CRM has been connected to Cognism.
• You have permission to edit CRM integration settings.
• State and country fields have been mapped in your CRM.

Why state mapping is required

Many CRMs use predefined picklist values for states or provinces.

For example, your CRM may expect:

• California
• CA
• New South Wales
• NSW

If the value exported from Cognism does not exactly match the value configured in your CRM, the export may fail or the field may be left blank.

State field mapping allows you to define how Cognism values should be translated before they are exported.

Configure state field mappings

1. Go to Settings > Integrations.
2. Select Configure next to your connected CRM.
3. Open Field Mappings.
4. Select the CRM object you want to configure.
5. Locate the State field (or Company HQ State for company records).
6. Select Advanced.
7. Configure how Cognism state values should map to your CRM values.
8. Add additional mappings as required.
9. Save your changes.

Saving your changes

Saving differs slightly depending on your CRM.

Salesforce

Select Save in the mapping window.

Other supported CRMs

1. Select Save in the mapping window.
2. Select Save again on the Field Mappings page.

Important considerations

When configuring state mappings:

• Always configure the corresponding Country mapping.
• Ensure your mapped values exactly match the values used in your CRM.
• Review mappings whenever CRM picklist values change.

If no matching state value exists, the state field may be exported without a value or the export may fail, depending on your CRM configuration.

Supported countries and regions

State mapping is supported for countries and regions that use state, province, or regional administrative values.

The available mappings depend on your connected CRM and its supported picklist values.

Expected result

After configuring state mappings:

• State values match your CRM picklists.
• Export validation errors are reduced.
• CRM data remains consistent.
• Users spend less time correcting exported records.