# Migrating a production website: Doing it right the first time

**URL:** <https://meta.discourse.org/t/migrating-a-production-website-doing-it-right-the-first-time/33484>\
**Category:** Self-hosting\
**Created:** [September 19, 2015, 11:05pm UTC](https://meta.discourse.org/t/migrating-a-production-website-doing-it-right-the-first-time/33484 "2015-09-19T23:05:26Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [September 20, 2015, 12:46am UTC](https://meta.discourse.org/t/migrating-a-production-website-doing-it-right-the-first-time/33484/2 "2015-09-20T00:46:55Z")

</div>

This is going to sound like a sales pitch, and I apologize. But with so much at stake, I strongly recommend you work with someone who has migrated a bunch of sites to Discourse, and knows how to run the gauntlet of the issues you describe, because they have done it before.

So whether us, or someone else, I would secure professional help to get your migration done right.

Happy to document all this stuff as we go, of course. Nothing we do is or will ever be a secret. But it is hard work to get it right and fix whatever needs fixing.

---

_[View the full topic](https://meta.discourse.org/t/migrating-a-production-website-doing-it-right-the-first-time/33484)._