> ## Documentation Index
> Fetch the complete documentation index at: https://docs.myfundingmachine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Account Location field

> Identify the client account field and safely change its CRM display name.

**Product Location ID** and **Sub-Account Location ID** refer to the same existing
opportunity custom field. The latter is the preferred display name. Its key stays
`opportunity.product_location_id`; its field ID and saved values stay unchanged.
Some existing app messages and historical documentation still use the original name.

## Keep the subscriber field separate

**FM Subscriber Source Location ID** belongs to the separate subscriber-sync
integration. Its key is `opportunity.fm_subscriber_source_location_id`. Do not
rename, delete or substitute that field when updating the account-mapping label.
See [subscriber sync](/staff/subscriber-sync).

## Rename the existing field safely

Deploy the compatible account-linking, identity, reconciliation and onboarding-reminder
code before changing the CRM label. Those paths resolve the account field by its stable key;
metadata that omits a key retains the original exact-name behavior. Wrong-Location,
wrong-model and ambiguous definitions do not qualify.

1. In the Operations account, locate the existing **opportunity** field by
   `opportunity.product_location_id`. Record its field ID and current metadata.
2. Update only its display name to **Sub-Account Location ID**, using the CRM UI
   or the Locations custom-field update API. Preserve the model and existing
   position and settings. Do not delete and recreate the field or change its key.
3. Read its metadata back. Confirm the field ID, key, model and settings are
   unchanged, and that the subscriber-source field is untouched.
4. Check existing mapped Onboarding and Retention records and refresh account
   reconciliation. Confirm their Location IDs remain available and that a mapped
   Open onboarding opportunity still enables setup reminders.

Renaming the label does not repair missing account links, change billing or move
pipeline stages. [Account linking](/staff/onboarding-account-linking) explains
how to establish those separate relationships.

To undo the rename, restore the original display name on the same field. Restore
that label before rolling back the compatibility release; older code may still
require the original name. Production changes require the usual explicit approval.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.