Field mapping for the onOffice sync

You find it under Settings → Integrations → onOffice in both frames ("Addresses from onOffice" and "Objects from onOffice"), each in the collapsible "Field mapping" area.

Anatomy of a mapping#

Each row connects an onOffice field (left) with a platform field (right). The switch enables or disables a row, the trash icon removes it.

onOffice field

The technical field name from your onOffice (e.g. objekttitel, kaufpreis, Email).

Platform field

The target field in the platform (e.g. Title, Sale price, Email).

Add a custom field#

Field names differ per onOffice account, especially for custom fields. So you can enter any field:

1. 1

   Pick or type a field

   In the "Add" row, choose a field from the list or, via "Custom field", type the exact onOffice field name (case-sensitive, as in onOffice).

2. 2

   Pick the target field

   Select the matching platform field.

3. 3

   Add and save

   Click "Add", then save the mapping.

Translate values (value lists)#

Fields with a fixed value list (for example object type, marketing type or a custom status field) often need the onOffice values translated into platform values. For suitable target fields the "Values" button appears.

1. 1

   Open the values dialog

   Click "Values" in the row.

2. 2

   Load values from onOffice

   "Load values from onOffice" fetches the field's real value list. The platform suggests a translation for each value.

3. 3

   Review and save

   Review each row, adjust as needed, then apply. Values without a translation leave the target field unchanged.

Unmapped fields are not lost#

Fields onOffice does not deliver#

Field catalogs differ per onOffice account. If onOffice cannot deliver a requested field, the sync skips it so the whole run does not fail. Such fields are noted in the run log as "no counterpart in onOffice".

Reset to defaults#

"Reset to defaults" restores the factory mapping. Your own rows are replaced.

Next#