The object status (Active, Reserved, Sold and so on) is detected from onOffice automatically during the sync. This page explains exactly how that works, how to attach your own status value list, and how to fix "all objects set to active".
Automatic detection from standard fields
onOffice provides three reliable standard fields with every object, and the platform derives the status from them. You can rely on these because onOffice always includes them, regardless of the broker configuration.
The order is unambiguous: sold beats reserved, which beats the active flag. A sold object is therefore always "Sold", even if onOffice still lists it as active. An unknown status code is deliberately kept visible (Active) rather than hiding the object under a guessed value.
Map a custom status value list (e.g. Status2)
Many onOffice accounts keep the marketing status in a custom field, often
Status2, with an individual value list: "Active marketing", "Passive
marketing", "Reserved", "Sold, sole sale", "In acquisition", "Market
observation", "Order expired" and so on.
The automatic detection cannot know such fine stages (Acquisition, Preparation, Lost, Archived). For those you map the field yourself:
Open the field mapping
Under Settings → Integrations → onOffice, in the "Objects from onOffice" frame, open the "Field mapping" area.
Add the status field
Add a new row: pick your status field as the onOffice field (e.g.
Status2), and "Status" as the platform field.Translate the values
Click "Values" in the row. "Load values from onOffice" fetches the field's real value list, and you map each onOffice value to a platform status (e.g. "Sold, sole sale" → Sold). Suggestions are pre-filled; review them.
Save and sync
Save the mapping, then click "Sync now". On the next sync your mapping wins whenever it resolves a value.
Fixing "all objects set to active"
Previously it could happen that all imported objects were "active", including sold ones. This had a clear cause and is fixed.