Field Mapping Guide

Whether you are setting up a Sync, an Automation, or a Workflow, mapping your data correctly between monday.com and Mailchimp is the most critical step. This guide explains how data types interact and outlines the specific formatting requirements for complex fields.

Understanding the Mapping Logic

When you map fields, you connect a source data point to a target destination. In most setup screens (like the monday.com automation builder), the target is on the left, and the source is on the right.

To prevent sync errors, the app automatically filters your available options based on data type compatibility. If you cannot find a specific column or field in the dropdown list, the data types are incompatible. You can resolve this by changing the column type in your monday.com board or adjusting the merge field type in your Mailchimp audience.

Important: Fields marked with an asterisk (*) are mandatory. The automation or sync will not run if these are left unmapped.

Data Type Compatibility

Here is a quick overview of which fields can be mapped to each other:

---

Specific Field Rules & Formats

Review the specific formatting requirements and troubleshooting tips for complex field types below.

Dropdown Fields

Mailchimp will not create new dropdown values on the fly. Any unknown values sent from monday.com will be rejected, causing the sync or automation to fail.

• Best Practice: Only map Mailchimp dropdown fields to monday.com dropdown columns.
• Crucial Setting: Mailchimp expects a single selection, while monday.com allows multiple. You must limit your monday.com column to one selection: Column Title > Settings > Customize Dropdown column > Limit selection to 1 label.

Address & Location Fields

Address mapping requires a very specific structure. Depending on the feature you use, you can provide this information from a single column or combine multiple columns into the contact field.

Supported Formats:

• [Address Line 1], [City], [State Abbreviation] [Zip Code], US
• [Address Line 1], [Address Line 2], [City], [State Abbreviation] [Zip Code], US
• [Address Line 1], [City], [State Abbreviation] [Postal Code], CA
• [Address Line 1], [Address Line 2], [City], [Postal Code] [Zip Code], CA
• [Address Line 1], [Postal Code], [City], [Country Abbreviation]
• [Address Line 1], [Address Line 2], [Postal Code], [City], [Country Abbreviation]

Note: [Country Abbreviation] must be the two-letter code (e.g., FR for France, DE for Germany) based on ISO 3166-1.

Examples:

• 123 Main St, Anytown, CA 90210, US
• 456 Elm Ave, Apt 2B, Springfield, IL 62704, US
• Unter den Linden 77, 10117 Berlin, DE
• 10 Downing Street, Flat 2B, SW1A 2AA, London, GB

Phone Fields

While Mailchimp accepts almost any value as a phone number, monday.com is much stricter and requires a country assignment.

• US and Canada: The country is automatically detected based on the format.
• All other countries: You must use the international E.164 format, which requires the country code at the beginning (e.g., +44 for the UK or +49 for Germany).

---

Mapping Best Practices

• Standardize first: Ensure your dropdown values match exactly across both platforms before setting up a sync or automation.
• Start small: Always test your mappings with 1-2 sample contacts before running bulk updates or creating full board syncs.
• Email is king: Always map the Email Address to the required email fields, as it serves as the unique identifier for linking contacts.
• Tags: Do not try to map tags via standard text fields. Use the dedicated tag settings in Syncs, or specific automation triggers for tag management.