> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/integrations/crm/write-behavior.md).

# Write behavior

Your CRM is your team's source of truth. Some fields — a hand-curated job title, a specific email or phone your team has verified, custom notes on a contact — you don't want Mobly to overwrite with enriched data, no matter how confident the enrichment.

**Write Behavior** lets you decide, field by field, whether Mobly can overwrite the CRM value or should leave it alone if a value is already there. Set it once on the Mapping tab and every future sync respects it.

## The two settings

For each mapped field, you pick between:

* **Overwrite** *(default)* — Mobly writes its value to the CRM every time, replacing whatever was there. This is the historical behavior and stays the default for backwards compatibility with existing mappings.
* **Write if Blank** — Mobly writes its value only if the CRM field is empty. If the CRM already has a value, Mobly leaves it alone.

Both settings still run enrichment as usual — the difference is only what happens at CRM sync time.

## Configure Write Behavior

1. Open your CRM integration in the Hub and click into the **Mapping** tab.
2. Find the field you want to protect and click the **gear icon** on the right side of that field's row.
3. A settings panel slides open below the row. The **Write Behavior** row shows one button per CRM object column (Lead, Contact, Account — depending on your sync mode).
4. Click the button to toggle between **Overwrite** and **Write if Blank**.
5. The setting saves as soon as you click; no separate save button on the Mapping tab.

Each object column is independent — you can set a field to Overwrite on Contact but Write if Blank on Lead, if your team's data-governance rules differ across objects.

## When to use each

**Overwrite** — fields where Mobly's enrichment is more reliable or more current than what's in the CRM. Common picks:

* Company size, revenue, industry (Mobly's enrichment refreshes; CRM records may be stale)
* LinkedIn URL, headshot
* Address fields when your enrichment is your primary source

**Write if Blank** — fields your team owns and edits by hand. Common picks:

* Job title on curated Contacts (your inside-sales team has already cleaned these up)
* Notes / description fields your reps write
* Personal email / phone when your CRM's version came from a customer relationship your team owns

## Scope and behavior notes

* **Available on every connected CRM** — Salesforce, HubSpot, Pipedrive, and Zoho all use the same Mapping tab and honor Write Behavior identically.
* **Applies to future syncs only.** Changing a field from Overwrite to Write if Blank doesn't restore previously-overwritten values in the CRM. Those are already there. The setting only affects what happens next.
* **Per-object independence.** If your integration syncs to multiple CRM objects (Lead + Contact, or Contact + Account), each object has its own Write Behavior button for the same Mobly field. Set them independently.
* **Default is Overwrite for existing mappings.** Every existing field mapping was created before this feature shipped, so all of them start as Overwrite. No customer's sync behavior changes without a deliberate configuration.

## Related articles

* [Field mapping](/help-center/integrations/crm/field-mapping.md) — the how-to for mapping Mobly fields to CRM fields in the first place
* [Sync modes](/help-center/integrations/crm/sync-modes.md) — Automatic vs Manual sync
* [Reconciliation](/help-center/integrations/crm/reconciliation.md) — what happens when a sync fails