Support » Installing WordPress » Upgrade Steps

  • I have a 2.1.1 install running. I want to migrate to 3.1 but I wish to do so by moving to a new server in the process.

    Please confirm my approach or otherwise share some advice:

    (1) take a full backup of the DB on server 2.1.1
    (2) restore full backup of DB on server 3.1
    (3) download and install WP 3.1 on server 3.1
    (4) walk through setup and have it update/upgrade MySQL DB form 2.1.1 to 3.1

    Will this approach essentially work?


Viewing 15 replies - 1 through 15 (of 27 total)
  • No you will have to upgrade in steps as You have very old version You will find them here

    each time upgrading your database.



    Forum Moderator

    Try something like: 2.1.1 -> 2.2.1 -> 2.3 -> 2.5 -> 2.7 -> 2.9 -> 3.0 -> 3.1

    Remember to:
    – deactivate all plugins first
    – switch to the default theme
    – backup your database before you begin and again after every successful upgrade step.

    Good luck 🙂

    Ok, so it sounds like I also have to put a copy of WordPress 2.1.1 on server 3.1 and then step through the upgrades. I was thinking that just having the 2.1.1 Database would be enough for WP 3.1 to figure out what to do. But I also need to put a copy of the software on the new server as well. Ok…that is enlightening because my interpretation of the upgrades I have been doing on other servers was that the new version worked solely against the existing database. I was not aware that it touched the software too.

    yes with each version there are some changes made to core files as well that is reason why you have to upgrade in steps.

    Ok, thanks “govpatel”.

    Also, “esmi” states “Try something like: 2.1.1 -> 2.2.1 -> 2.3 -> 2.5 -> 2.7 -> 2.9 -> 3.0 -> 3.1”

    Is that just a suggested path or is that the actual path?

    I guess if I needed to step through each version the migration would look something like this “2.1.1 > 2.1.2 > 2.1.3 > 2.2 > 2.2.1 > 2.2.2 > 2.2.3 > 2.3 > 2.3.1 > 2.3.2 > 2.3.3 > 2.5 > 2.5.1 > 2.6 > 2.6.1 > 2.6.2 > 2.6.3 > 2.6.5 > 2.7 > 2.7.1 > 2.8 > 2.8.1 > 2.8.2 > 2.8.3 > 2.8.4 > 2.8.5 > 2.8.6 > 2.9 > 2.9.1 > 2.9.2 > 3.0 > 3.0.1 > 3.0.2 > 3.0.3 > 3.0.4 > 3.0.5 > 3.1”

    Something else that’s curious to me.

    On another server I have that I have kept the versions updated on a more regular basis, WP offers me the ability to automatically upgrade to the newest version. So I have been doing that (through the auto FTP feature). But I know for sure that I have skipped a version/sub-version ‘here and there’.

    So does the auto update process know to step through sub-versioning updates on its own, or have I been jeopradizing my upgrades by not doing it manually sub-ver to sub-ver?

    the ones Esmi suggested are main upgrades and others are updates when found some problem or bug so as long as you update as Esmin suggested you will be fine.

    How did you know which ones were “upgrades” and which ones were “updates”? I didn’t see any sort of tagging or indication on the download page…

    Ok, here’s a good one…

    I inherited this very old WP version (2.1.1). My WP experience started with 3.0. In WP 3.0 I could upgrade right within the dash board. But in the 2.1.1 dashboard there is not obvious place to kick-off the upgrade to 2.2.1 (which I have downloaded from and uploaded to my server).

    Can you tell me how to upgrade to this interim version? Thanks.

    Silly me…I guess I should have searched the forums first. Here’s how to update if anyone is following this thread:

    esmi states

    “Remember to:
    – deactivate all plugins first
    – switch to the default theme”

    If I use the automatic (ftp) upgrade feature in WP, will it deactivate plug-ins > switch theme to default > do upgrade > switch theme back > re-activate plug-ins?

    Or do I need to handle the plug-ins and themes before/after the auto upgrade?

    You will need upgrade manually as You will not find upgrades in automatic upgrade in steps.

    I have video and article on my website on how to upgrade manually

    You will have download each one and replace like I have done and upgrade your database as needed and then go next version.

    Backup database as well for each version just to be on safe side.

    Ok, so since the auto (ftp) update does not “deactivate all plugins first” and does not “switch to the default theme”, then I should manually upgrade when a new version is an “upgrade” but let WP auto update then the new version is an “update”? How can I tell if a new version is an “update” or an “upgrade”?

    Also, I already manually stepped through each upgrade per esmi’s instructions. My site is not at 3.1. I am asking this for future updates/upgrades.

    Thanks for the clarification…

    typo in above s/b “My site is now at 3.1.”.

    If your site is updated now and working with 3.1 when ever there is update or upgrade you will get update available for wordpress and plugins with in admin panel you can stay updated so you do not fall behind.

Viewing 15 replies - 1 through 15 (of 27 total)
  • The topic ‘Upgrade Steps’ is closed to new replies.