# How connections and sync work

Adresse: https://docs.athaus.ai/en/konzepte/anbindungen-und-abgleich

> How Athaus stays in constant conversation with onOffice, Propstack and Google, what rest, source identifier and canon mean, and when anything is written back.

Type: Concept
Last updated: 2026-11-10

Athaus does not replace your CRM overnight. It reads what is there and writes back only what you approve. The move brings a portfolio over once; the sync keeps it current afterwards.

## What can be connected [#what-can-be-connected]

CRM: onOffice and Propstack (Pro and Scale plans). Also Google Calendar, Gmail and other mailboxes via IMAP and SMTP, Google Drive and the portals Immowelt and Kleinanzeigen. An office has at most one connection per system ([How to connect onOffice, Propstack or Google](/en/anleitungen/anbindung-einrichten)).

## Move and sync [#move-and-sync]

* The **move** brings contacts, properties, owners, search profiles, history and documents over once, completely, and can be repeated without creating anything twice ([Move your portfolio](/en/anleitungen/bestand-umziehen)).
* The **sync** then fetches at a fixed interval what changes in the CRM, and reads everything once at night.

On the page **View sync**, each area shows whether Athaus reads it, whether your key in the CRM does not allow reading it (**Not permitted**), or whether Athaus only writes there (**Written back only**).

## The terms [#the-terms]

* **Canon:** the one format in which Athaus knows a record, whatever the source.
* **Source identifier:** the identifier under which the CRM holds a record. Two records from the same source are two properties, even at the same address; that is why a second run creates nothing twice.
* **Rest:** what a read record carries that is not an Athaus field, such as fields you created yourself in your CRM. It shows under **From the old CRM** on the record and never goes back. When you confirm a mapping under **Map fields**, it becomes an Athaus field.
* **Conflict:** A detail was changed differently in Athaus and in the CRM. You decide which value counts.

## Writing back: off out of the box [#writing-back-off-out-of-the-box]

Out of the box Athaus only reads. Whether changes go back to the CRM is decided by the owner or admin per connection and area. Even then:

* In the first 24 hours after the first finished sync nothing goes out.
* Only what a person or a named automation did goes out, not syncing, merging, imports or the agent's reactions.
* Athaus sends only touched fields and empties no field that has a value in the CRM unless you emptied exactly that one.
* Under **Written back recently** you see what went out, when and by whom.

## Deleting and networks [#deleting-and-networks]

If you delete in the CRM, Athaus follows softly: the record is removed like a delete by hand and a running listing is withdrawn; nothing is deleted for good. If another source still holds the record, it stays. If you delete in Athaus, the CRM follows only if writing back is on for that area. An address hidden in the CRM appears in the listing as postcode and town only.

If an office is part of a network, the CRM delivers the whole network's stock. A connection can then carry a filter on up to 20 beginnings of property numbers (each at most 40 characters): Athaus imports only properties whose number begins that way; what was imported stays. The filter is set on the connection; the app does not show it.
