# Sync objects from onOffice 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 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. 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). The owner relation (object to address) is read along the way, so an object and its owner contact belong together without duplicate work. 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). **All** objects are imported, not just active ones. Sold and reserved objects come in with their correct status. You then filter by status in the object gallery instead of missing objects. ## 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**. If "only published objects" is still active, onOffice returns only some of your objects. Disable it in onOffice under **Extras → Settings → Users → your API user → Rights**. ## 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. Object status becomes **Sold**. Object status becomes **Reserved**. Object status becomes **Active**. Object status becomes **Draft**. 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. The onOffice title image becomes the platform title image (first position). The title image is stored in good quality, the rest web-optimized (to save storage). Originals stay in onOffice and are fetched at full resolution on demand. The label you maintain on the image in onOffice comes along ("Wohnzimmer", "Blick nach Süden"). If none is set, the caption or the uploaded file name is used. If both are empty, photos are named "Titelbild", "Foto 2", "Foto 3" so they stay distinguishable. Photos imported before this change are renamed by a background pass; names you gave yourself are left alone. The photo import starts automatically once the object sync finishes and continues in the background. Existing or manually uploaded images are never overwritten. Objects with no photo in onOffice keep the placeholder. A property is reserved before its first photo is fetched, so an interrupted run never creates a second copy. If the plan storage is full, the photo import stops and you get a notification. After an upgrade or cleanup the remaining photos load on the next sync. ### 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. With many objects the photos are fetched gradually (each object has several images), so it can take a few minutes for all title images to appear. A repeated sync fetches photos that were still missing after the first run. ## 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. Unmapped fields are not lost: all raw data read is kept in full in the object details. You can add a mapping later and re-sync without changing anything in onOffice. ## Start the first sync Open the "Field mapping" area, review the defaults and save. (For the standard case you need not change anything.) Click **"Sync now"**. The first run fetches your inventory; the result arrives as a notification ("X new, Y updated"). 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. ## Two common symptoms and their cause This was a bug in the first-import filter (only "active" objects were created). It is fixed: the entire inventory is now imported. If the message persists, restart the sync once and check the object rights (disable "only published objects"). The cause was that the status was wrongly set to "active" on insert when no status mapping resolved. The status is now derived from sold / reserved / the active flag. On the next sync, already imported objects correct themselves automatically. See the status guide. ## Next How the object status is determined and how to map a custom status value list. Standard fields, custom fields, value translation and how unknown fields are handled. Fixes for the most common sync problems.