Broken versioning after cloud migration

[Maria Petkova]

Hi,

I am using Scroll Versions on server. I have 3 versions per space on average. After migrating to cloud these versions disappear and instead of a picker (drop-down menu for versions) the pages appears in the page tree several times with vvX.X at the end. 

I know that for cloud the app that has to be used in Scroll Document.

My question is is there an easy way to restore the versioning on an entire space or I should somehow manage it page by page and version by version? One of the spaces has over 1000 pages and it is in 4 versions and it will be an enormous effort.

[Nils Bier _K15t_ · Accepted solution]

Hi @Maria Petkova

Due to various reasons (most of them being technical constraints in Cloud), we weren't able to ship Scroll Versions for Confluence Cloud.

Instead we've developed a new app, Scroll Documents, which is the Cloud-equivelent of Scroll Versions.

In order for you to continue using the version management functionality, you'd need to firstly convert your Scroll Versions space(s) to (a) Scroll Documents managed space(s) on your Server instance, and then take this newly created space to the Cloud using the Confluence Cloud Migration Assistant.

From your description it sounds like, you've taken the Scroll Versions managed space and migrated that one to the Cloud, which - as you can see - does not work.

We have a dedicated microsite available on migration.k15t.com that provides further context and deeply explains what users need to do if they want to migrate their Scroll Versions spaces to Confluence Cloud.

If you have additional questions after going through the content, or have concrete questions regarding your use case, we're happy to support you.
Please feel free to open a ticket with us, so we can further discuss and help you with the transformation to Cloud.

Looking forward to hearing from you.

Cheers,
Nils

[Maria Petkova]

@Nils Bier _K15t_ Thanks a lot! I will go step by step through your instruction.  

[Kristian Klima · Accepted solution]

Hello @Maria Petkova 

If I remember correctly, you first have to migrate Scroll Versions to Scroll Documents on the Server side, then migrate Scroll Docs from Server to Scroll Docs on Cloud.

I'd ping K15t directly.

Scroll Documents has a rather different approach to versioning compared to Scroll Versions.

[Maria Petkova]

@Kristian Klima 

You remember correctly according to Nils' answer.

Thank you!