Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Confluence version convertion old to nowadays



I've developed the software that is able to automate different software upgrades/migrations paths.

This is especially works for cases where manual upgrade efforts are outside of common sense.

So, now I'm testing my software to deal with a bit less than 1Tb of confluence data at version 3 to convert it to modern versions. It is impossible to convert all plugins, but confluence often used by big corporations to store different tech/non-tech knowledge bases.

I'm wondering if in the community there is any interest for my software to convert old PROD confluence to any target version? 



Partly, but I am not sure how much.

I work for an Atlassian partner, and we do a lot of upgrades.  For Confluence upgrades, we quote at "hours" if the source version is Confluence 4 or above and the target is "latest".  Obviously, plugins/add-ons/apps, integrations and automations can add a LOT of time to that.

So, we would be interested in stuff that can

  • Upgrade 3.x or lower to 7
  • Cope with all the apps that can be added
Like OleksandrK likes this


Yes, it can do from <2.6 to 'latest', for plugins and other subcomponents can be applied custom 'handlers'. Handlers can be written for any non-upgradeable things so such can be upgraded in at least controlled way.

>>Cope with all the apps that can be added

Not sure, I understand this requirement. But, it is not confluence specific software.

It intendeds to be adoptable, but at the moment i'm testing it on a legacy confluence.

So, Are you interested to talk about solution I have?


Actually, not really.  Confluence upgrades and migrations are incredibly simple from 4.x to latest, and there's hardly anyone left using lower versions - we do maybe two 1/2/3.x upgrades a year and the frequency of that is in decline (last couple of years has been 3, but 2019 is down to 1).  I'm sorry, but it's simply not worth writing "handlers" when they'd take longer than just dealing with it by hand.

Thank you Nic,

Ok, it is clear - the case I've made this software is unique, agree.

At the moment i'm using it as a scalable solution(few instances on separate servers), so users can request Spaces (or by list) that they need to migrate(Import XML/Export XML) that allows to bypass any manual operations at all. You simply tells to the software which space keys you want to copy to new Confluence, and as this software is in the middle it is upgrading Space(or some pages) with preserved structure. Is this case interesting in somehow?


Log in or Sign up to comment

Atlassian Community Events