Diaries do not arrive as working Cloud diaries. Right now, there is no migration path from Diary for Data Center to Diary for Confluence Cloud. Please read this page before you migrate.
What happens to your content
Your content is safe. The Atlassian Cloud Migration Assistant moves every page, including the pages that hold a Data Center Diary, with their full history, attachments, and permissions intact.
Diary for Data Center stores its entries as a table in the page. That table is page content, so the words your team wrote in Diary do migrate. No content is deleted or lost.
What does not carry over
The macro itself is not migrated. Diary for Data Center and Diary for Confluence Cloud are different apps with different macros, and the Cloud macro does not recognize a Data Center one. After migration:
-
Pages that held a Diary show an unrendered or unknown macro where the Diary macro used to be.
-
The entries are still inside that macro, and arrive as a table in the page, which is perfectly readable - but they are not a Cloud Diary, so you cannot add, edit, or delete entries from view mode.
-
The Data Center Properties column comes across with the table. Diary for Cloud has no such column; it was empty in every row on Data Center, so nothing of value is in it.
This is not something we can work around from our side. The Cloud Migration Assistant transfers page content, but it cannot turn one app's macro into another app's macro.
Recommended: decide what to keep before you migrate
Because the Diary macro will not be live on the other side, it is worth taking stock shortly before you move.
-
For Diaries you only need to read, do nothing. The entries will be displayed on the page as a table - it simply is not an interactive Diary any more.
-
For Diaries you want to keep writing in, insert a fresh Diary macro on the page after migration and re-create the entries you still need. For a handful, writing them again is quickest. For a long Diary, someone comfortable with the page editor can move rows across by hand - but note that the Cloud entry table has four columns (Date, Time, From, Content) rather than Data Center's five, and each author cell has to be a real user mention. Check that a couple of rows render before doing the lot.
-
For Diaries nobody needs any more, this is a good moment to delete them.
Whichever route you take, nothing here is destructive. The original table stays in the page, and page history keeps every version from before the migration.
Feature differences to expect
Diary for Cloud is a rebuild rather than a port, so a few things work differently. The ones most likely to affect a team coming from Data Center are the keyboard shortcuts, the anchor links for sharing a single entry, and task lists inside entries. All of them are listed in Known Issues and Differences from Data Center.
Questions?
Reach out via our Service Desk or support@livelyapps.com - we are happy to help!