We would like to have the ability to sync two instances in a way that would allow us to update the content in the "internal" confluence a it would automatically update the content in the "external" confluence. I know there is a plugin for this, but our Cybersecurity department doesn't like the plugin solution much, so having a native solution would be ideal. This would solve our problem of sharing content with external parties that do not have our company certificates so can't access our Confluence. (again I know there is a plugin specifically for this, but it was rejected by our cybersec)

We only use on-prem (DC) instances of Confluence. 

Our Company explore any built-in features (we have a group of users have a need) because we explored the AddOn "Space Sync for Confluence" behavior, we need to grant the admin privileges to normal user, cannot fit enterprise use fully.

Any more flexible enhancements for Jira automation to different level, it can be more flexibility 

eg) apply for different product - Confluence 

eg) apply to administration, Backup & Restore unique Jira project & Confluence Spaces

This is a good feature to have and will help immensely in providing a graceful transition from on-prem to the cloud.

I've tested out the Jira and Confluence migration tools and it does the job well enough for migrating the raw data from server to cloud, but it appears that many of the plugins are not available in the cloud. 

We're looking at testing sync options in Jira, to sync server to cloud with the idea that we can install plugins, configure and work out those details and then do a final sync. We selected a plugin and it failed to initialize with no errors, anywhere so we've contacted the vendor.

We're looking at sync options in Confluence an it appears that for server to cloud, NONE EXIST. 

It would be super nice if there were some way we could access the command line of our cloud instance so we could write our own syncing scripts but it appears to me that command line access to the server we are paying for.... does not exist. 

This seems like a very odd oversight. It seems to me that this is a feature which should be built in to the product. 

The only option I really see is that I should carefully recreate the functionality using new plugins where possible, document exact steps, blow away the migration and start fresh and recreate it exactly again from scratch during a scheduled maintenance window while the entire company is watching while under pressure to make a deadline. 

What is the opposite of love? 

I'm going to reach out to the team at Atlassian to discuss in more detail, but I really feel like I should not have to. This should be a built in feature. It feels as if we're being forced into a cloud solution with no reasonable path to get there. I would really like to know if you're losing customers due to this forced transition, and if so, what products are they moving to? I'd like to know if there are other ticketing or systems that can import from Jira or Confluence. Anyone have any suggestions?

Still needed =)

This request created since Y2016, we wait as such a long time, this feature is not just benefit under company which run multiple confluence instance but the company which have their sub-company or acquired from another company which they cannot migrate or consolidate space in short term, this will resolve by implementing space / pages synchronization. 

Looking forward on this feature!

Yes, this would be very helpful for us to synchronize two different confluence instances in a disconnected network.

Hey Ez Aldin,

thats a good idea. Is there any chance that you will make this script public? Would be very nice from you.
I'm also into the idea to sync to Conf Server instances over Python API Calls/Posts.

Regards,
Emil

Heidelberg, Germany

i am working right now on implementing a python script for this issue. it synchronizes a confluence server to confluence cloud. i would like to say that is almost finished. 

Since Altassian will no longer support Confluence Server from 2024, I believe, we in the company have to transfer the entire content of the Confluence Server used so far to the Confluence Cloud and synchronize the two instances again and again.

best regards,

Ez Aldin Aybak Al Hari

Kiel, Germany

I’m curious about solutions other firms have implemented for this story. We are considering: a Cloud instance of Confluence and add-on(s) capable of publishing/copying/synchronising between instances. We would allocate Could logon accounts to third parties as needed, and synchronise the space or spaces we need to share from our Server (Parent) to Cloud (Child).

Obviously the more dynamic the content, the greater the level of synchronisation needed. For training material, or software doco, this isn’t a problem (infrequent updates). For things like meeting minutes, or requirements gathering, the update frequency is high and more synchronisation runs are required.

How are others managing this sort of requirement?
Cheers,
Peter Quick
Pronto Software
Melbourne, Aus