The object sync imports your properties from onOffice into the platform's central object database. Once set up it runs automatically every day, and all tools work with the same object inventory.
You find this area under Settings → Integrations → onOffice, in the "Objects from onOffice" frame. It requires an existing connection (see the connection guide).
What the sync does
Read objects
The platform reads your objects from onOffice page by page (100 per page). Even large inventories are processed in full: the first run fetches as many pages as possible immediately, the rest continues in the background.
Map fields
Each onOffice field is imported into the matching platform field per your field mapping (title, object type, price, area and so on). The status is detected automatically (see below).
Link owners
The owner relation (object to address) is read along the way, so an object and its owner contact belong together without duplicate work.
Create or update
New objects are created, already imported ones updated. The sync is repeatable: it never duplicates and updates existing objects on every run (status changes such as "sold" keep flowing in).
Prerequisite: object rights of the API user
For every object to arrive, the onOffice API user must be allowed to read objects, including the unpublished ones:
- Read objects (all) is enabled.
- The checkbox "can only read objects published on the website" is disabled.
The status is detected automatically
This is the most important part. You do not need to map the status by hand: the platform derives it from onOffice's reliable standard fields.
Order: "sold" beats "reserved" beats the active flag. A sold object is therefore always Sold, whatever else is set.
If your onOffice uses a custom status value list (often a field named
Status2 with values like "Active marketing", "Reserved", "Sold, sole sale"),
you can map it in addition. Your mapping then takes precedence whenever it
resolves a value. See the
status guide.
Photos are imported automatically
After the object data is synced, the platform fetches the object photos from onOffice and stores them in the platform. The gallery and object detail then show real images instead of the gradient placeholder.
Loading images at full quality
The small preview images are fine for browsing, not for working. As soon as you need a photo for a brochure, for homestaging or for your website, open the property and click In voller Qualität laden above the gallery. The platform then fetches that property's originals from onOffice and replaces the previews.
Next to it you see roughly how much storage this takes. The button deliberately covers one property at a time: at full resolution a single property quickly runs to a few dozen megabytes, and across several hundred properties that would be more storage than your plan provides.
Field mapping
Sensible default mappings (title, object type, marketing type, address, areas, rooms, prices, energy) ship out of the box. Review and extend them in the collapsible "Field mapping" area. After saving it collapses again to keep the page calm; reopen it via "Show".
Details, custom fields and value translation are covered in the field mapping guide.
Start the first sync
Review the field mapping
Open the "Field mapping" area, review the defaults and save. (For the standard case you need not change anything.)
Sync now
Click "Sync now". The first run fetches your inventory; the result arrives as a notification ("X new, Y updated").
Review the result
Open Objects in the platform. You see your properties with the correct status and filter as needed.
After that the sync runs automatically every day. Status changes and new objects flow in on their own.