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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Could I please get the definitive upgrade path for Confluence.

We are currently running Confluence 3.5.9.
As I understand it, I need to upgrade to 5.0.3 and then to 5.9.

But I was recently informed of the need to go 3.5.17 when I asked this question:

I need to know what the proper upgrade path is and if UT Southwestern has licenses to run the current production server, a migration server and then a final destination server concurrently.

Is this the proper avenue to request this kind of support?

5 answers

1 vote

The answers you got on the other question are correct.  The definitive path is, and always has been 3.x -> 3.5.17 -> 5.0.3 -> 5.9. 

You might need more versions like 4.0 in there, but that will come out in your testing (and generally is not needed, 5.03 should be fine).  You might be able to get away with 3.5.9 to 5.0, but that is absolutely NOT definitive, and again, you won't know unless you test it.

For the licences, we don't know.  If you have current supported commercial licence (which you should find in your my.Atlassian account), then yes, you have production licence, and you can use the associated developer licences for your migration.

Strange, this guide indicates that it's 5.0.3 -> 5.10.???

Would be great if Atlassian could pin the landing version here. I.e. move to this version as there are still older versions out there in the wild. 

1 vote
Artur J Atlassian Team Dec 29, 2015

Hi Adam,

We have a very detailed documentation, see Upgrading Confluence.

In order to make sure everything works as expected, to keep the downtime as short as possible and not end up with an unusable system:

    Try all steps on a test system first! Make sure you take notes of every step!

    Backup everything! Be sure you know how to restore the system in case something goes wrong.

    Test everything throughly after the test and the productive migration!

I hope this helps. The whole procedure needs a bit of planning but it can be done.

Hey Adam,

                    You need to Upgrade to 3.5.17 and later to 5.0.3 and then to 5.9. For any Upgrade support you have to raise support ticket with Atlassian at


Hope this helps



Chander Inguva

Thank you for the prompt reply.
Is the data import path the same as the upgrade path?

We are thinking now that maybe we build a clean Virtual Machine and then import the data.
Would we need to build 3.5.17 on one VM and import our 3.5.9 data, then build a 5.0.3 machine and import that data? 

Hey Adam,

                 You can import XML Data from 3.5.9 on to 3.5.17 and also from 3.5.17 to 5.0.3 and then from 5.0.3 to latest.I would have done an Upgrade from 3.5.17 to latest after importing data from 3.5.9 to 3.5.17.

Again, Please make sure you test it on Dev Instance first before proceeding on Production.




Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

Announcing Team Calendars in Confluence Data Center

Hi Community! We're thrilled to share that Team Calendars for Confluence is now a built-in feature for Confluence Data Center releases 7.11 and beyond.  A long time favorite,  Team Cale...

153 views 0 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you