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

# Remote Field Classes

> Overview of Remote Field Classes — a standardized way to read and write integration-specific fields (both standard and custom) that aren't part of Common Models.

> **Info**
>
> This feature is only available to customers on our **Professional** and **Enterprise** plans. View the [Merge Plans](https://www.merge.dev/pricing) to learn more.

---

## Overview

Merge's Remote Field Classes feature allows you to programmatically access additional fields that are not mapped to Merge's Common Model fields. These non-mapped fields can be both standard fields on the third-party platform and custom fields on a Linked Account.

Remote Field Classes also surfaces metadata about each field, such as display name and type.

Merge will generally leave field values untouched, but will normalize values into a standardized format if necessary, such as DateTime fields.

## How is this different from Remote Data and Field Mapping?

[Remote Data](/merge-unified/supplemental-data/remote-data) is all the raw data from a model in the original format Merge received it in.

[Field Mapping](/merge-unified/supplemental-data/field-mapping/overview) and Remote Field Classes both build on top of Remote Data to return fields in a normalized format:

* **Field Mapping** is best for reading fields from the third-party by mapping them to a Merge Common Model
* **Remote Field Classes** is best for accessing highly variable custom fields and writing those fields back to your users' third-party platform

## Supported categories

Remote Field Classes are currently available for:

* Accounting

  Beta
* CRM

  Beta
* Ticketing

  Beta

Please reach out to your Merge contact if you are interested in other categories.