Field mapping is where the source's data structure meets the destination's expected schema. Every bridge has a mapping step.
The mapping screen
Left column = source fields (auto-detected from the source — e.g. for Gravity Forms, every form field shows up).
Right column = destination fields (auto-loaded from the destination's API — e.g. ActiveCampaign lists every custom field on your account).
Drag-and-drop or dropdown: pick which source field feeds which destination field.
Required fields
Most destinations require at minimum:
- email (always required)
- first_name OR full name (most CRMs want this split)
Leave optional fields unmapped if you don't need them.
Static values
Not every field has to come from the source. Click 'Use static value' on any destination field and type a constant:
- Always tag new contacts with 'lead-gen-2026'
- Always set the country code to 'US'
- Always assign to a specific salesperson
Transformations
A few common transforms are built in:
- Split full name → first_name + last_name (handles 'John Smith' → John, Smith)
- Phone normalization → strips formatting (415-555-1234 → 4155551234)
- Lowercase email → ensures dedupe works across CRMs
- Date format conversion → ISO 8601 → CRM-friendly format
Map-once, reuses-everywhere
When you set up a bridge for a specific source/destination pair, the mapping is saved. Build a second bridge with the same pair and you can copy the existing map as a starting point — no re-mapping every time.
What to do if a field doesn't appear on the destination side
The destination's field list comes from its API. If you add a custom field in ActiveCampaign mid-setup, hit the Refresh fields button on the mapping screen — WP Sync re-fetches the schema.