Norv:
You don't actually need the forum itself, but you need the vbulletin database, and a configuration file where the converter finds information like what is the name of the vbulletin database and table prefix.Please eventually:- install SMF- restore the database backup into a database. (make sure that database has the same user as the SMF database user; it could also be the same database as SMF; or the SMF database user has also access to it)- make a folder for vbulletin, and a folder /includes in it.- make a file config.php into the ./includes folder, with the contents

--- End code ---- upload the converter files in your SMF folder and run convert.php

Red G. Brown:
It would be awesome if I could enter that info manually, and upload an SQL backup file. I'm switching web hosts, so the database isn't even on the new host, and I can't create the db with the same naming scheme used by the old host.

----

update:

I just found out that not only will I have that problem, but the work around for this problem requires the webhost to change my username to the same username I used on the old webhost. This will allow the backup mysql file to work, but it will break the smf installation. In other words, I can't convert a VB backup from another webhost, which defeats the purpose of having backups in the special case where I want to resttore the backup and convert at the same time, and there's no other choice but to do it that way.

Norv:

--- Quote from: qwasty on October 05, 2009, 01:52:05 PM ---It would be awesome if I could enter that info manually, and upload an SQL backup file. I'm switching web hosts, so the database isn't even on the new host, and I can't create the db with the same naming scheme used by the old host.

--- End quote ---You can enter the information manually, in the config file. The name of the database, and the table prefix.If you restore the backup under another name, then please enter in the config file the name you use. I didn't say you need to have the same name as the one the former installation had (though when you create a database, you should be able to name it any way you want).(in most cases)Please explain, what exactly are you talking about when saying "can't create the db with the same naming scheme used by the old host"?

--- Quote from: qwasty on October 05, 2009, 01:52:05 PM ---I just found out that not only will I have that problem, but the work around for this problem requires the webhost to change my username to the same username I used on the old webhost. This will allow the backup mysql file to work, but it will break the smf installation. In other words, I can't convert a VB backup from another webhost, which defeats the purpose of having backups in the special case where I want to resttore the backup and convert at the same time, and there's no other choice but to do it that way.

--- End quote ---Why do you say that you need the webhost to change your username to the same username used by the old webhost? That should not be the case at all. Please explain what you refer to, the username for the database of vbulletin? Why do you need it changed?

Red G. Brown:
Sorry for being vague. I don't understand the technical issues just yet, but my webhost uses cpanel, and it enforces a prefix on database names of the client's username. I tried to create database with a name appropriate under those restrictions, and then I tried to import the backup using phpmyadimn, but that gives me the following error:

Apparently, the import does not give me an option to choose which database to but the backup sql data into, and instead tries to put it into whatever db is hardcoded into the backup from the old web host.

So, I tried to create a db with the name "oldhostusername_bulletin", but the new host cpanel only allows "newhostusername_bulletin". After that, I gave up, since I don't know what else to do.

Norv:
Please try to open the backup file in a text editor (a lightweight text editor like Notepad++ should do just fine if you are on windows), and comment out the CREATE DATABASE line, like:

Note: you can make the backup without CREATE DATABASE too (thus allowing you to import the tables into an existing database). Typically a backup made with phpMyAdmin's Export feature does not have CREATE DATABASE (at least if you have the database already selected and go to the Export tab).