# Migrating vBulletin 5 database - Import script errors

**URL:** https://meta.discourse.org/t/migrating-vbulletin-5-database-import-script-errors/249495
**Category:** Migration
**Tags:** vbulletin5
**Created:** [December 20, 2022, 5:22pm UTC](https://meta.discourse.org/t/migrating-vbulletin-5-database-import-script-errors/249495 "2022-12-20T17:22:51Z")
**Posts on this page:** 1
**Showing post:** 36

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [December 22, 2022, 8:12pm UTC](https://meta.discourse.org/t/migrating-vbulletin-5-database-import-script-errors/249495/36 "2022-12-22T20:12:19Z")

</div>

> [@pfaffman](#):
>
> Usually when I say that Richard will come in and save the day

LOL, well, I guess I’m going to disappoint you today. I tried though, but I suspect that the commit of this importer was incomplete and did not include some changes to `base.rb`. @justin worked on this, maybe he knows. I do suspect that this could have been a customer specific thing that can be commented out without further consequences.

I have never used the bulk importers myself either.

Yes, import scripts can be complex and depend on the database specifics, but some scripts are simply not in a working state. That goes for this one as well, and there are some more scripts with for instance `# frozen_string_literal: true` that are just not working out of the box.

---

_[View the full topic](https://meta.discourse.org/t/migrating-vbulletin-5-database-import-script-errors/249495)._