 <p>Based on your edited requirements, I would:</p> <ol> <li><p>get your app running on new server with blank mongodb </p></li> <li><p>set up a reverse proxy that forwards both sub. and sub2.domain.com traffic to your app </p></li> <li><p>set up a CNAME that points sub2.domain.com to the new server </p></li> <li><p>copy over the DB data as found in <a href="http://stackoverflow.com/a/19305144/219238">Andrew's answer</a></p></li> <li><p>update your meteor.com app to just do a temporary redirect (something like window.location="http://sub2.domain.com")</p></li> <li><p>update your sub.domain.com CNAME to point to the new server</p></li> </ol> <p>This should result in minimal disruption; clients who connect to <a href="http://sub.domain.com" rel="nofollow">http://sub.domain.com</a> are auto-redirected to <a href="http://sub2.domain.com" rel="nofollow">http://sub2.domain.com</a> until the CNAME DNS change propagates. After a few days, the sub2 cname won't be needed anymore and you can remove the sub2 cname and entry from the reverse proxy.</p>