> 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.

# Mapping across an integration

> How to create integration-wide Field Mappings that apply to all Linked Accounts using a given integration (e.g., all Salesforce accounts).

---

## Overview

Creating a mapping across an integration is useful if you want to map an additional field that is standard to a particular integration, without creating additional Field Mappings for each Linked Account.

Integration-wide Field Mappings are available for frequently used Remote Fields - if you're not seeing the field you need, contact [support@merge.dev](mailto:support@merge.dev?subject=Field%20Mapping%20Origin%20Field%20Inquire). To see what integrations Merge supports for integration-wide mappings, visit our [Help Center](https://help.merge.dev/en/articles/7236095-supported-integrations-for-integration-wide-field-mapping).

---

## Create a Field Mapping across an integration

Click on an organization-wide target field or Common Model override field in the [Field Mapping](https://app.merge.dev/configuration/field-mappings/target-fields) page in Advanced configuration. Under **Field Mappings** or **Overrides by integration**, you can search for and select an integration for which to create a mapping. Click **+ Field Mapping** or **+ Override** to select a Remote Field to map to the target field.

![Integration-wide Target Field Configuration](/_fern-files/merge-test.docs.buildwithfern.com/b2baee9a52c34c4ebf31629848cf873ae0bf9a5adea6ab64f2d505c2b82ef78d/docs/src/assets/images/docs/guides/field-mapping/IntegWideTargetFieldConfig.svg)

This integration-wide mapping will be created by default for any existing and new Linked Accounts of that integration. It will appear labeled as an **organization-wide mapping** in each Linked Account's Field Mapping page in your dashboard and the target field will not appear in Link as mappable for your users.

Integration-wide mappings and overrides are authored against a third-party API endpoint, so they apply only to Linked Accounts that Merge syncs through that integration's API. If you connect the same integration through report files as well, for example through Generic SFTP, those Linked Accounts keep the value they get from the report and need a [Linked Account level mapping](/merge-unified/supplemental-data/field-mapping/mapping-for-a-linked-account) instead.

> **Info**
>
> A Remote Field must be returned in 95% of all Production Linked Accounts in Merge to be available for integration-wide mapping. Any integration that does not have at least 25 Production Linked Accounts will not show any fields as available for integration-wide Field Mappings.