Page unavailable? Copy its Markdown and paste it into your chat.
Moving from Kalender Sync
Plan a controlled transition between two separate products.
Reviewed · 2026-09-20 / Ridian
Ridian and Kalender Sync are separate products
Section titled “Ridian and Kalender Sync are separate products”Ridian extends the calendar-infrastructure direction with a shared permission model for users, teams and integrations. An existing Kalender Sync connection, subscription or assistant setup does not automatically become a Ridian connection.
Inventory before moving
Section titled “Inventory before moving”Record the connected providers, calendar pairs, directions, content levels and any assistant access. Identify managed copies and the original calendars. Agree which connections will be recreated and how the old ones will be stopped without deleting unrelated events.
Validate one workflow
Section titled “Validate one workflow”Connect the intended account in Ridian, use a separate test calendar and verify the required operations. Check provider-specific differences, especially CalDAV, recurrence, room flows and client permissions. Do not assume feature parity from similar menu labels.
Switch deliberately
Section titled “Switch deliberately”Arrange the transition so both systems do not independently maintain the same target copies. Keep a clear rollback plan and verify the original provider calendars. Subscription and pilot terms are a separate agreement; this guide does not promise automatic account migration or cancellation.
Use the capability guide and contact support before switching a business-critical workflow.