# vBulletin import\_script bug in importing children categories

**URL:** <https://meta.discourse.org/t/vbulletin-import-script-bug-in-importing-children-categories/143769>\
**Category:** Product Support\
**Created:** [March 10, 2020, 5:43am UTC](https://meta.discourse.org/t/vbulletin-import-script-bug-in-importing-children-categories/143769 "2020-03-10T05:43:37Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [March 11, 2020, 6:48am UTC](https://meta.discourse.org/t/vbulletin-import-script-bug-in-importing-children-categories/143769/17 "2020-03-11T06:48:09Z")

</div>

> [@michaeld](#):
>
> I never asked you to _run_ vB4, I suggested you migrated your database to it and _then_ run it through the importer. True “unix-style” where you pipe multiple steps to get to the desired outcome - IMHO the shortest and cheapest migration path.

This is the proper advice. Is there some reason you can’t upgrade to VB4? Because that might be easier than writing a whole new migratory for VB3.

---

_[View the full topic](https://meta.discourse.org/t/vbulletin-import-script-bug-in-importing-children-categories/143769)._