---
title: Map Incoming Fields
description: "Field mapping tells PloverCRM where each incoming source column or form field should be stored on a lead. > ![image 56 - Plover CRM](https://plovercrm.com/wp-content/uploads/2026/10/image-56-1024x486.png) ## Map fields 1. Open the source setup or CSV import mapping step. 2. Review the…"
url: "https://plovercrm.com/docs/map-incoming-fields/"
updated: "2026-11-03"
category: "Integrations & Data / CSV Imports & Field Mapping"
tags:
  - Custom Fields
  - Field Mapping
  - Lead Import
  - Lead Sources
  - Web
---

# Map Incoming Fields

Field mapping tells PloverCRM where each incoming source column or form field should be stored on a lead.

> ![image 56 - Plover CRM](https://plovercrm.com/wp-content/uploads/2026/10/image-56-1024x486.png)

## Map fields

1. Open the source setup or CSV import mapping step.
2. Review the incoming field names and sample values.
3. Select the matching PloverCRM field for each incoming field.
4. Map standard fields such as name, email, and phone to the correct destinations.
5. Map custom fields only when their meaning and data type match.
6. Leave unknown fields unmapped rather than assigning them incorrectly.
7. Review required fields and save the mapping.

## Check the mapping

Use the preview or an approved test submission to confirm that values appear in the intended fields. Check phone and email formatting, dates, numbers, and multi-value fields carefully.

A mapping error can place customer information in the wrong field or cause a submission to fail validation.