Editing the ImpEx Configuration File 
Before uploading the ImpEx files to your web server, you must edit the ImpEx configuration file (upload/impex/ImpExConfig.php) to tell ImpEx how to communicate with your database(s).

To edit the ImpExConfig.php file, you will need to open the file in a text editor such as Windows® WordPad. (Note that we do not recommend that you use Windows® Notepad to edit ImpExConfig.php, as Notepad has problems displaying the line breaks in some file types.)

The settings in this file need to be edited in order to create a working configuration file. These settings are devided in two groups. The target* and the source*:

Target Database Information (Into which database do we import?)

If you have ImpEx installed correctly and are running it via the admincp, you can ignore the target settings go to the source. This is because ImpEx will read you vBulletin config file.
$impexconfig['target']['databasetype']Enter the type of database here, currently this can only be mysql
$impexconfig['target']['server']This sets the address of your database server. On most installations the database server is located on the same computer as the web server, in which case the address should be set to 'localhost', otherwise use the address of the database server as supplied by your web host.
$impexconfig['target']['user']This variable contains the username provided to you by your host for connecting to your database server.
$impexconfig['target']['password']The password that accompanies the database username should be entered here.
$impexconfig['target']['database']This value should be altered to state the name of the database that will contain your vBulletin installation on the database server.
$impexconfig['target']['tableprefix']If your vBulletin installation uses a prefix on the tables, set it here.
Source Database Information (From which database do we import?)
$impexconfig['sourceexists']If the system that is being imported from uses a database, enter the details for it here and set 'sourceexists' to TRUE. If the source data is NOT stored in a database, set 'sourceexists' to FALSE.
$impexconfig['source']['databasetype']Enter the type of database here, usually this is mysql. If you are importing from a MS-SQL database, you will need MS-SQL support in PHP
$impexconfig['source']['server']This sets the address of database server from which you want to import data from. On most installations the database server is located on the same computer as the web server, in which case the address should be set to 'localhost', if this database is hosted on another domain use the address of the database server as supplied by your web host. If you are attempting to import from a remote server (i.e. you have just moved hosts) ensure that the database will allow remote connections. Other wise you will need to back up the source database and restore it on your new server so it is local.
$impexconfig['source']['user']This variable contains the username provided to you by your host for connecting to your database server.
$impexconfig['source']['password']The password that accompanies the database username should be entered here.
$impexconfig['source']['database']This value should be altered to state the name of the database that contains your other forum software data on the database server.
$impexconfig['source']['tableprefix']If that database uses a prefix for the tables, set it here.
Note:
Please note that Jelsoft / vBulletin Support can not provide the values you require for your database(s). These variables are only available from the web host providing your web/database server.

If you need to create a new database for vBulletin to use, instructions for doing so in a variety of systems are available here.
The error logging can be used by the support or development team to understand an import issue or to gain clues during debug.

The language is the language file that is used for the display of text, English, German, etc.

The page speed is the seconds of wait between the page refresh when automatically refreshing. Setting a longer time will help with network lag and server load.

The defines are typical settings that are changed for problem imports :

Defines for special cases (What do we want to turn off/on ?)
impexdebugPrints out to the screen any debug added to an install of ImpEx.
emailcasesensitiveWhen matching emails in the user module (user merge), this forces the matching to be case sensitive or not (follwing the RFC strictly, emails should be case sensitive, for the vast majority of the time, this isn't the case).
forcesqlmodeSome MySQL servers that have MYSQL_STRICT mode, will not accept a lot of the ImpEx SQL as it currently uses the database defaults and not a value for even field, this attempts to override that setting by passing the SQL ' set sql_mode = '' '
skipparentidsThe last set of updating post is setting the parent id's for the imported posts if they don't have one. This can be (and usually is) very intensive due to the amount of SQL used. The number of queries run is the number of threads times two, plus one. Though this is very effected by the number of posts as usually the post table has to be scanned (MySQL intensive).

Sometimes due to the load on larger boards the final page of the import posts can time out, setting this define to true will skip that all together. The load and bottle neck here is a know issue and being looked at.
When you have finished editing the ImpExConfig.php file you should save it again and prepare to upload the file to your web server.
User Contributed Notes: Editing the ImpEx Configuration File Add a Comment