Team Calendars

Note: Team Calendars migration is available as of WikiTraccs v1.37.0

WikiTraccs can migrate Confluence Team Calendars to SharePoint.

What you get

For each calendar owned by a migrated space, WikiTraccs creates one SharePoint list with a calendar view on the target site of that space. Calendar events become list items. The list name ends with (Confluence Calendar).

Permissions are not migrated: the generated lists inherit the permissions of their target site, so configure list access separately.

How to enable

Check Synchronize team calendars to SharePoint lists in WikiTraccs.GUI: dialog Transformation Settings, tab Migration. The feature is off by default.

"Features": {
    "SynchronizeTeamCalendars": true
}

When it runs

Calendar synchronization runs once per space and migration run. It runs only for selectors that select a complete Confluence space by space key. CQL and content ID selectors do not trigger it.

Requirements

• Works with Confluence Cloud and Confluence Data Center (with the Team Calendars app). Confluence Server has not been tested; it is expected to behave like Data Center because Team Calendars is the same app there.
• Interactive Login is not required. Cloud API tokens and Data Center Personal Access Tokens work, subject to the source account’s calendar permissions. Anonymous access does not.
• A calendar must be discoverable and exportable as a complete iCalendar (VCALENDAR) document. An unavailable or malformed export causes that calendar to be skipped.

Calendar failures do not fail or stop page migration. Check the discovered and synchronized calendar counts and the migration log for partial results. The counts are stamped on the space’s row in the Confluence Space Inventory list, in the columns WT_In_CfCalendarCount (discovered) and WT_Out_CfSyncedCalendarCount (synchronized); a synchronized count below the discovered count reveals failing calendars.

Learn more

• What is migrated, what is not
• Updates and manual changes