Thank you for contacting us about this.
The best way to migrate your calendars is to recreate them in Confluence Cloud using the .ics URL.
Essentially, you'll export your calendars to .ics format, and then import them again. However, I do want you to be aware of a current bug that I ran into myself when doing this for my own instance:
If your calendar contains any custom event types, which it likely does, then these will be converted to default events. You will need to manually recreate your custom event types and then apply these once again to your events. If you have recurring events then please make sure to modify all events and not just the single event, and it should apply the change to each recurring day.
Do let me know if you have any questions about this.
Note that CONFCLOUD-49097 custom event types has now been fixed!
This issue is now fixed. When importing a calendar with custom event types, the event types are now retained after import.
Hi @Shannon S ,
My company is migrating all our Team Calendars data from Confluence Server to Cloud.
Could you tell if the workaround you are providing keeps the person field data safe ? Moreover is there any workaround to migrate seamlessly all our calendars to the Cloud ?
Thanks in advance.
We found Atlassian's calendar migration tools riddled with errors and design flaws: while Atlassian has no hesitation shoving customers to the Cloud, they don't provide the tools they promised to support that migration.
We exported our Confluence Server calendars to .ics and loaded them in Google Calendar. We lost some fields in the migration — but bizarrely retained a lot more data than when we tried migrating from Confluence Server to Confluence Cloud.
We ditched Confluence Calendars, switched to Google Calendars, and never looked back. You may find similar "success" with Outlook or another calendar system that can import .ics.
Good luck — you're going to need it.
Here is the solution that Atlassian offered.
The good news is that we have a team-calendars migration script. Full details are in the README of the script posted here:
warning: Please note that this is not an officially supported tool/script, so this is intended to be used as-is with thorough testing until an official migration method is released.
That way we expect to see better results and all the team Calendars migrated successfully to your cloud site!
Been reading over the documentation and even for me as a seasoned IT veteran it is a bit complex. And my environment does not lend it self to having the ability to install python to run the script so I am still trying to figure out how to execute it. I will report back when I was able to run it. Please do the same.
Agreed with @Darren Newberry - not everyone has the ability to work with scripts. However, the share and the effort that went into this solution are very much appreciated!
This is one of those times that remind me that I need to learn Python, and maybe pick up some other scripting experience.
(free time always being the limiting factor)