# Migrating vBulletin onto existing and live Discourse instance

**URL:** <https://meta.discourse.org/t/migrating-vbulletin-onto-existing-and-live-discourse-instance/54236>\
**Category:** Product Support\
**Created:** [14.Декабрь.2016 13:52:01 UTC](https://meta.discourse.org/t/migrating-vbulletin-onto-existing-and-live-discourse-instance/54236 "2016-12-14T13:52:01Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [14.Декабрь.2016 18:23:17 UTC](https://meta.discourse.org/t/migrating-vbulletin-onto-existing-and-live-discourse-instance/54236/7 "2016-12-14T18:23:17Z")

</div>

> [@Emilio\_F\_Castillo](#):
>
> Naturally, conversations have started to occur and we’re off to a solid start, with new members already posting.

Oh. Darn. I hadn’t realized that. We should have talked more about how imports worked when we started our discussions.

> [@Emilio\_F\_Castillo](#):
>
> The entire database with images is approximately 500 mb

A more useful measure is how many users and topics/posts there are.

> [@steko](#):
>
> I suggest to create a separate temporary Discourse instance for the purpose of converting the existing vBulletin content.

That’s probably what to do, though it’s possible to backup your existing instance, restore it on a dev box and do the import on top of it. I think it may duplicate user accounts, though. The vbulletin importer creates permalinks for topics, which might be important to you for maintaining SEO juice. It’s not a recommended path, but it could be one way to proceed.

---

_[View the full topic](https://meta.discourse.org/t/migrating-vbulletin-onto-existing-and-live-discourse-instance/54236)._
