Importing from an older version (8 posts)

  1. tzenes
    Posted 7 years ago #

    I recently decided to move servers.

    Now, what I'd like to do is to take my old blog and move it on to the service at wordpress.com

    Sadly I never upgraded from 2.0.X so the only thing I can get out is an sql dump.

    Now I'm not sure how I am supposed to get that into the 2.6 wordpress.com seems to be running, and an option like rss importing doesn't seem possible (not that I'm very clear on how to do that either).

    Now if this has already been asked, please point me to the answer, but how do I import my backup from 2.0.X to 2.6 with my limited access?

  2. moshu
    Posted 7 years ago #

    You upgrade it to the latest and it will have an Export option (and wp.com has the Import feature).

  3. Chris_K
    Posted 7 years ago #

    Another option might be to try this plugin on the old blog:

  4. tzenes
    Posted 7 years ago #

    I no longer have access to the old server, is there some way I can convert my backup to the proper version without it?

  5. moshu
    Posted 7 years ago #

    If that plugin doesn't work for you either... then the only thing I can think of would be this:
    - make a local install using XAMPP
    - import your mysql backup into the DB using phpMyAdmin
    - upgrade
    - use the WP's built-in Export (in 2.6)
    - Import the exported file to wp.com

  6. tzenes
    Posted 7 years ago #

    I got as far as step 3 before I hit a road block.

    After upgrading my database I got the following message when logging in:

    You do not have sufficient permissions to access this page.

    Since I'm logging in with the admin account I'm not really sure how to procede.

    I do have direct access to the sql database through phpmyadmin though.

  7. @mercime
    Volunteer Moderator
    Posted 7 years ago #

    Slow but successful way to upgrade

  8. tzenes
    Posted 7 years ago #

    Same problem... different versions.

    Does anyone know how to deal with this sufficient permissions bug?

    nm, fixed that bug.

    Apparently, while my databases were prefixed with jim (lowercase) the correct prefix was Jim (with the uppercase J), I find it strange that it doesn't require consistency between these two.

Topic Closed

This topic has been closed to new replies.

About this Topic


No tags yet.