Is it common to develop on confluence server and then migrate to cloud?
Asked by Bill OLeary:

I had a confluence server where I was writing user documentation for tools I am selling.  
When my harddrive crashed, I realized I had no backup and lost all of my documentation.  
I thought I would have been OK if I had a cloud account instead so I went and got one.   
Now it turns out the cloud doesn't support the stepShot plugin which is invaluable for writing my documentation.

Is this a common problem?

Would it make sense to develop my documentation on my Server instance and then migrate what I produce over to my Cloud instance?


Answers:
author: Sasha Reminnyi
body: It's so good that [StepShot](https://marketplace.atlassian.com/plugins/net.stepshot.plugins.confluence.v35/cloud/overview)now supports Confluence Cloud and Mac content development :)


author: Rob Woodgate
body: Hi Bill,

Cloud not supporting things that the server version does is a common problem (the list of restricted Cloud functionality is [here](https://confluence.atlassian.com/confcloud/restricted-functions-in-confluence-cloud-734070955.html)), as are addons that only work on the server version. I don't know if it's common to develop pages on a server and keep the pages on a cloud. My gut feeling is "No", but there are plenty of experienced consultants on here who can verify that (or not) for you.

With regard to your specific problem, you can create your own backups very easily, and Confluence creates a daily backup anyway - see [here](https://confluence.atlassian.com/doc/site-backup-and-restore-163578.html) for more information. So you may not have lost your work after all. Paying for a server installation and a Cloud installation as well just to get limited disaster recovery backups (Atlassian only keep [7 days worth of backups](https://confluence.atlassian.com/cloud/data-storage-faq-744721620.html#DatastorageFAQ-Howoftenisdatabackedup) for Confluence Cloud) doesn't seem good value for money to me, but only you can say if it's good value for money for you.

comments: author: Nic Brough -Adaptavist-
body: To fill in the bit that Rob says he's not sure about, I'd say his gut-feel is spot-on. Most people don't write on one system and publish on another because transferring them, while not **hard** , is also not **a really simple intuitive thing to do**. Copy and paste a section from a single page is fine, but beyond that, you're looking at import/export, transfer mechanisms, yada yada yada. I don't know of anyone who does it like that (Although some places do have "write once and share via Scroll Versions or other content managing add-ons")


author: Rob Woodgate
body: Thanks Nic.

Bill - Nic is an experienced Atlassian consultant (and the person I was hoping would verify it one way or the other).


author: Bill OLeary
body: Thanks guys...

The only place the data backup would have been was on my dead hard drive :smile:...

I had also never migrated to use anything but the evaluation Database.

The other reason I wanted the cloud version is that I wanted to publicly host the documentation I am writing and I don't have the infrastructure (or maybe just the knowledge on how to get my website to link back to a server at my home)

I thought the cloud was going to solve my backup, development and hosting problem, but It really only seems to solve the hosting problem.

Bill


Tags: cloud

confluence-cloud