Calendar pairs & sync direction

A calendar pair links one calendar on your CalDAV server with one calendar in the cloud. Syncing always happens at the pair level, which gives you fine-grained control: you decide exactly which calendars are connected and how.

Creating a pair

Inside a connection, choose the CalDAV calendar and the cloud calendar you want to link, then pick a direction. A connection can hold multiple pairs (up to your plan's connection allowance), so you can sync several calendars independently.

Creating a new calendar from the wizard

You don't have to create the target calendar beforehand. In each calendar dropdown of the pair setup, there's a "+ Create new calendar…" option. Pick it, enter a name and a color, and CalDAVconnect creates the calendar for you and selects it for the pair — no need to leave the wizard.

This works on both sides:

• Cloud side (Google / Microsoft 365): always available.
• CalDAV side: available for servers that support calendar creation — Nextcloud, SOGo, Radicale, Baïkal and Synology. For Posteo, mailbox.org and Generic CalDAV servers the option isn't offered, because those expose only their existing calendar; pick the existing calendar instead.

If a server rejects the new calendar (for example due to permissions), CalDAVconnect tells you and you can simply choose an existing calendar.

Sync directions

• Bidirectional (default) — changes flow both ways. Create or edit an event on either side and it appears on the other.
• CalDAV → Cloud — one-way mirror from your server into the cloud calendar.
• Cloud → CalDAV — one-way mirror from the cloud into your server.

Use one-way directions when one side should be the single source of truth.

What gets synced

For each event, CalDAVconnect syncs the details that matter for scheduling: title, start/end time, all-day flag, location, description, attendees and recurrence rules. Recurring events and their exceptions are handled too.

How conflicts are handled

With bidirectional sync, the same event can change on both sides between syncs. CalDAVconnect keeps a record of the last known state of every event and compares it against both sides, so it can tell what actually changed rather than blindly overwriting. In the rare case of a true conflict (both sides edited the same field), the most recent change wins, and nothing is silently deleted.

Deletions

Deleting an event on one side propagates the deletion to the other side (subject to the pair's direction). CalDAVconnect includes safeguards so that a temporarily unavailable or cancelled cloud event does not cause events to be wrongly recreated or removed.

Privacy between calendars

Because syncing is scoped to the specific calendars in a pair, only those calendars are touched. Other calendars on either account are never read or modified.

Next

Curious how changes are detected so quickly? See How sync works.