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

Upgrade path for Confluence 4.3.2 to 7.8


We're currently using Confluence 4.3.2 and have a plan to upgrade this to 7.8.

wondering what would be the successful path, your responses would be greatly appreciated!!

1 answer

0 votes
Dave Theodore [Coyote Creek Consulting]
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 14, 2020

You need to read over all the Upgrade Notes for the major and minor versions in between 4.3 and 7.8 (warning, it's a lot.) There will be interim steps that you need to take to get to 7.8, so you won't be able to go directly to 7.8.  I don't recall what the interim versions are, but I'd expect to have to step through 3 or 4 in order to get to version 7.8. You should obviously do this in a development environment and document the steps, before doing this in production.  Good luck!

You may want to work with a Partner on this, as it could be a messy upgrade, and you may need to update your Plugins/Add-ons/Apps in a particular way, as well. We don't see old versions of Confluence that much any more, but when we do, they are typically fairly complicated to update. It would also be a good idea to get the new version in the hands of your power users for a while in your development environment, to give them the chance to become familiar with the new version. Nothing irritates a Project Manager more than not being able to find "the button" they need when they're in the middle of a release.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events