Can't really tell from documentation how to go about doing this. Thanks!

First, back up.  :)  Download a copy of your db folder in BINARY mode as a back up and also do an export of your entries.

What version are you running right now?  If it's 2.21, download the upgrade installation and upload /schemas to the same directory as mt.cgi.  Put your password in mt-db-pass and upload that to the same place.  Add the required mysql lines to your mt.cfg following the instructions and run mt-db2mysql.cgi.

Follow the instructions for 2.11 -> 2.21 upgrade and that should get you there, please post back how that goes for you.

Thanks for the pointers.

I'm considering moving to my domain where MySQL is available, so I thought I'd make that switch at the same time.

Or would it be advisable to move the Berkeley DB version first then upgrade to MySQL once all is running smoothly at the new site?

I *think* it's easier to move a mysql install because you don't have to worry about whether the new server has the same Berkeley version like you would have to if you moved a regular install.

I haven't moved mine, so I don't know for sure, but I think that's the case.

Maybe it would just be easiest to set up MT at the new site and then just do a complete import from the old site, with all the new info going directly into MySQL format?

Or is that not how it would go?

I was thinking you could upgrade to mysql now, export the mysql database when it's time to switch and then import the data into mysql on the new server.

Then you'd keep your settings, authors, and templates... if you do just an entry import into a fresh install you won't keep that stuff... it only does entries.  But that would work too.

jdbanks - It sounds like you don't have MySQL available at your current host. Is that correct?

I'd think it depends on how complex your MT set up is. If you're the only author then it might be fastest to do a fresh MT install at the new host, setting it up from the start with MySQL, and then configure your settings for each blog, copy and paste your templates, and import your entries.

Also, if the new host has a different version of Berkeley DB than the old host, you could run into other problems and a lot of hassle sorting them out and then converting.

It depends on how much work you think it'll take to replicate your current set-up.

Oh, you're switching hosts to get mysql.  Gosh, you must have been wondering what the heck I was doing telling you to upgrade now.  sheesh, I'm silly sometimes, the sentence I'm considering moving to my domain where MySQL is available swooshed right over my head, lol!  Sorry about that.  Thanks almuhajabah.

Yeah, then I'd probably do a fresh mysql install at the new host and import your entries.  So make sure you have a good export, you may want to make a practice blog where you're at, while you still have access to the account, and make sure the import will go smooth.  And copy out any templates you want to paste into the new install later.  :)

Thanks, bmk and almuhajabah, for your expertise. It's just me and my single little blog, so it sounds like the fresh install and import routine is probably the way to go.

Are there quirky things to look out for when importing into MT into MySQL?

Others might disagree, but I was a MySQL newbie when I upgraded to MT 2.21 and switched over, and the conversion went fine for me - MySQL is the way to go.