# Migration to Hosted Mender from self-hosted one **URL:** https://hub.mender.io/t/migration-to-hosted-mender-from-self-hosted-one/1076 **Category:** General Discussions **Created:** [September 26, 2019, 3:32pm UTC](https://hub.mender.io/t/migration-to-hosted-mender-from-self-hosted-one/1076 "2019-09-26T15:32:48Z") **Posts on this page:** 1 **Showing post:** 4
### Author: ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley) #### Post date: [July 7, 2020, 2:28pm UTC](https://hub.mender.io/t/migration-to-hosted-mender-from-self-hosted-one/1076/4 "2020-07-07T14:28:23Z")
My guess is that this is an issue with the certificate in use which is definitely going to be different between the servers. We are working on making this smoother but in the meantime you may need to use a statescript with some extra logic on your end to update the server.crt file. I think if you deploy an update that adds the second ServerURL but does not update /etc/mender/server.crt, then the deployment should complete from server1. You can then use a ArtifactCommit\_Leave state script to update /etc/mender/server.crt (or just delete it and remove the conf file entry if your new server uses a CA-signed cert). At this point you _may_ need to restart Mender. Please let us know if you try this method and what success you have with it. Drew --- _[View the full topic](https://hub.mender.io/t/migration-to-hosted-mender-from-self-hosted-one/1076)._