The data is all in the database, it can be exported. But typically when you're moving from software A to software B, you ask, B about importing from A. Not A about how to move your data to B, which we have no clue about, since we don't support/use that software. And that software is not the topic of the site.
The data is all in the database, it can be exported. But typically when you're moving from software A to software B, you ask, B about importing from A. Not A about how to move your data to B, which we have no clue about, since we don't support/use that software. And that software is not the topic of the site.
Yes I understand this, I should have named the topic different I am sorry. So How do I export this data, what are the names, what do I look for...ect.
You have this data ni your database, chances are software B is going to have an importer to pull the data straight out of your current database with no changes or extra work on your end with the vBulletin software.
You have this data ni your database, chances are software B is going to have an importer to pull the data straight out of your current database with no changes or extra work on your end with the vBulletin software.
Could you please tell me or point me to the data in the database that has the data I am looking for? The purpose is so I have it and when I go "B" I will have it just in case I need to have it to import if there is no way for "B" to directly import out of the VB database.
Assuming you're in vB4, you're going to be looking at the user, thread, post, forum, and blog tables. When it gets to the article system you're going into a highly complex area of node and parent child structure.
Assuming you're in vB4, you're going to be looking at the user, thread, post, forum, and blog tables. When it gets to the article system you're going into a highly complex area of node and parent child structure.