> This page is for Unified.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.merge.dev/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.merge.dev/_mcp/server.

# Field Mapping

> How Field Mapping works — create target fields on Common Models, then map third-party custom fields to them at the integration or Linked Account level.

---

## Overview

Merge Field Mapping allows you or your users to map data from your users' platforms to new fields on your Merge Common Models.

[Remote Data](/merge-unified/supplemental-data/remote-data) must be enabled to create target fields and mappings on a Common Model. This feature is available to **Professional** and **Enterprise** customers.

![Field Mapping Overview](/_fern-files/merge-test.docs.buildwithfern.com/04c3554e630deadffac361d8e798e4dd5339c9d24c37954d52e94cfeb6127c5d/docs/src/assets/images/docs/guides/field-mapping/FieldMappingOverviewSVG.svg)

There are two ways a Field Mapping can be created:

#### [For all Linked Accounts across an integration](./mapping-across-an-integration)

Integration-wide mappings allow you to map fields that are not Common Model fields to all Linked Accounts for that integration

#### [For a specific Linked Account](./mapping-for-a-linked-account)

Linked Account-level mappings allow you to map a custom field that is specific to a Linked Account