A useful custom-field mapping keeps the CRM field’s identity and type alongside its readable column label. LC Bridge’s early-access import preview combines standard and discovered custom fields in one chooser. Check the sample values and source access before relying on a field in a report or outgoing update.
A column heading is a label, not a field identity
Teams rename custom fields as their processes change. They also reuse familiar names such as Priority or Renewal date. A connection should retain the source field ID and object context so a renamed label does not silently point a column at another field.
Give the worksheet a readable heading, but keep its relationship with the selected CRM definition. A contact’s custom field and an opportunity’s custom field are separate fields even when their display names match.
Preserve the meaning of the field type
Text, numbers, dates, and selection values need different treatment. A numeric score should be usable in a calculation. A date should not depend on guessing whether 04/05 means April 5 or May 4. A selection should retain the accepted source options.
Keep null and empty values visible while testing. Replacing them with zeros or default text can make a report look complete while changing its meaning. Record any transformation in a separate calculated column.
Inspect fields in the import preview
Choose the record type, open the Fields chooser, search for the field, and select it alongside the standard columns. Preview a few values and adjust column order before running the import. After changing fields or filters, use a fresh preview before Save & Run.
If the catalog is empty, distinguish an account with no matching custom fields from missing access or a load error. Those outcomes need different recovery. Reconnecting should preserve the rest of the unfinished import.
Use one field definition consistently in reporting
A category chart needs a deliberate rule for empty and unfamiliar values. A date filter needs a timezone and boundary. A score-based segment needs a documented comparison. These choices are part of the report definition, not decorative spreadsheet formatting.
The Custom Records sample demonstrates another boundary: reporting on a custom object requires its schema and customer associations. Seeing a contact custom field does not establish support for every custom-object schema.
Example: keep labels readable and mappings stable
| Field identity | Sheet heading | Type | Check |
|---|---|---|---|
| field-example-renewal | Renewal date | Date | Correct local date; blank stays absent |
| field-example-score | Lead score | Number | Measured zero differs from blank |
| field-example-services | Services requested | Multiple choice | Preserve the supported collection format |
These invented identities illustrate a mapping ledger, not provider API field IDs. If someone renames “Renewal date” to “Next renewal,” the readable heading changes; it should not silently bind the column to an unrelated field with a similar name.
Check write eligibility separately
Reading a custom field does not guarantee that the same field can be edited through the integration. Outgoing updates need an eligible field, valid type, matching record, permission, and explicit change review.
Use the data catalog to understand current boundaries. The public samples are synthetic, and broad custom-field or custom-object writeback is not promised. Request early access with the fields your team needs so their actual source support can be reviewed.
Sources and further reading
- HighLevel: update a contact
- LC Bridge data catalog and availability
- LC Bridge report definitions and samples
Provider references checked October 16, 2026. Menu labels and source access can change. Product examples describe the reviewed early-access design.