Incorrect postids,userids etc after import

[megroup]

Hello,

I would like to ask if someone had same problem as I do.

I was doing export from PHPBB2 to vB 3.8.2 (around 1100000 posts)
After around 4 hours (importing posts step) Impex finished importing all posts and was was going in a loop executing some same sql scripts. I aborted and continued with the import process steps.

New vB Forum was launched on 13th of April and as appeared working fine apart from the fact that all userids, forumids, threadids, postids, parentids are screwed up. Threrefore all references to older posts are now irrelevant.

Forum is running fine apart from that problem. Could you please tell me how to resolve this problem and steps to do it without doing the import from the scratch again (cannot be done as >6000 posts have been posted since).

I still have importpostids and other import ids in most of tables.

Thank you.
Max

[Wayne Luke]

When using ImpEx it will automatically use the next sequential ID in the vBulletin database. It makes no attempt to maintain the IDs of the system being imported. This would jeopardize the integrity of the vBulletin database. Maintaining integrity is its first priority. There is no way to "restore" your old IDs.

If you have not finalized the import, then re-running it will delete all imported data first. However if you associated users or they have made new posts then that data will be lost as well. The best solution would be to prune the data that has already been imported from the source database. After prune, turn on Dupe Checking in the ImpExConfig.php file. Though this will slow down the import slightly it can find some of the duplicates that still exist in the old database and not reimport them. Dupe Checking is not a guarantee against duplicates though.

[megroup]

When using ImpEx it will automatically use the next sequential ID in the vBulletin database. It makes no attempt to maintain the IDs of the system being imported. This would jeopardize the integrity of the vBulletin database. Maintaining integrity is its first priority. There is no way to "restore" your old IDs.

If you have not finalized the import, then re-running it will delete all imported data first. However if you associated users or they have made new posts then that data will be lost as well. The best solution would be to prune the data that has already been imported from the source database. After prune, turn on Dupe Checking in the ImpExConfig.php file. Though this will slow down the import slightly it can find some of the duplicates that still exist in the old database and not reimport them. Dupe Checking is not a guarantee against duplicates though.

This doesn't seem like a realistic solution, because users have already made >6k posts since import in the new forum. You are proposing that i should discard of 6k posts and just redo the import.
My solution however using some sql scripts that utilize importid fields in imported tables to fix older posts where importids are >0.
I have to find all links within tables to posts and threads etc. this doesn't include userids though. Overall i have to modify 26 tables with scripts that do work. But i was interested in similar issues that occured in the past and their approaches.

[Wayne Luke]

No... I proposed that you deleted the stuff that was already imported from your source database and finish your import of extra data.

Realistically, the forum should have never been brought live until after you had tested the import on a development server and made sure all data and permissions were transferred and setup correctly.

[Jerry]

New vB Forum was launched on 13th of April and as appeared working fine apart from the fact that all userids, forumids, threadids, postids, parentids are screwed up. Threrefore all references to older posts are now irrelevant.


The links refer to old URLs that due to not being phpBB2 any more don't make sense, this is known as internal link parsing, the only way to reliably do it is in my signature.

As that will deal with external incoming links and search engine updates for 303s.