How to handle team calendars when migrating to a new confluence instance

[William Scarce]

Hi All,

Our company has 2 confluence instances (seperate) and are in the midst of migrating one to the other. We understand that the spaces are a simple xml file transfer from CFL A to CFL B. Simple as long as versioning and add-ons match up, which they do.

Our question is how should we handle the migration of our team calendars? Are they treated the same as a space? Meaning is it a simple file transport, or is there something more difficult involved?

Thanks!

[Nathon Fowlie]

Wondering if anyone has found a good solution for this that doesn't involve hours of mindless point & clicking? For particularly large instances moving the calendars one by one is not feasible, particularly where calendar ownership is important. It'd be great if there was a way to do a single export + import of all calendars in the system.

[Ryan Goodwin]

Hi William,

The solution here is to export the calendars to ical. Yes, this is time consuming but due to the way calendars are stored (in the bandana table in the database) there is no easy way to extract the information. The ical export is the safest, quickest way out there.

If you have tons of users with calendars, I might advertise that users are responsible for bringing over their calendars. I'm not even sure if admins can access all the calendars out there, but if that's the case, the admin would need to subscribe to a calendar, then export it. Rinse repeat.

https://confluence.atlassian.com/display/TEAMCAL/Exporting+Team+Calendars+Content+to+Other+Calendars

[William Scarce]

Thanks Ryan! This worked great!

[cagua1]

I wish there was a good way to do this as well.  Right now, it's looking like exporting from the DB and importing into the new DB is the only way.

https://answers.atlassian.com/questions/48077

[Jason Smith]

We should vote up this feature request: https://jira.atlassian.com/browse/TEAMCAL-2423