# Porting to new server

**URL:** <https://hub.mender.io/t/porting-to-new-server/450>\
**Category:** General Discussions\
**Created:** [April 4, 2019, 2:14am UTC](https://hub.mender.io/t/porting-to-new-server/450 "2019-04-04T02:14:51Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohnS](https://avatars.discourse-cdn.com/v4/letter/j/87869e/32.png) [@JohnS](https://hub.mender.io/u/JohnS)\
**Post date:** [April 4, 2019, 2:14am UTC](https://hub.mender.io/t/porting-to-new-server/450/1 "2019-04-04T02:14:52Z")

</div>

Hello,

I am using Mender to manage 10 Raspberry Pis. I have to port the Pis to a new management server because the older server will not be available to me. I set up a new management server with new certificate keys and created an artifact to deploy to the Pis from the old server. The Pis did reach the new server and I approved them. But they soon rollbacked to the old artifact because the old server thought the deployment failed. Please advise me how I can finish the server switching. Any suggestion will be appreciated!

---

<div class="post-metadata">

**Author:** ![JohnS](https://avatars.discourse-cdn.com/v4/letter/j/87869e/32.png) [@JohnS](https://hub.mender.io/u/JohnS)\
**Post date:** [April 4, 2019, 3:04am UTC](https://hub.mender.io/t/porting-to-new-server/450/2 "2019-04-04T03:04:49Z")

</div>

Fortunately found this thread that works for me via SSH  
[Migrating a device from one Mender server to another](https://hub.mender.io/t/migrating-a-device-from-one-mender-server-to-another/438/5).

Thank OP and mirzak for providing the scheme.

Still curious whether the server switch can be done through deployment.

---

<div class="post-metadata">

**Author:** ![dellgreen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/dellgreen/32/85_2.png) [@dellgreen](https://hub.mender.io/u/dellgreen)\
**Post date:** [April 4, 2019, 5:03am UTC](https://hub.mender.io/t/porting-to-new-server/450/3 "2019-04-04T05:03:53Z")

</div>

Have you tried deleting the files in the linked article as part of an update script packaged in the deployment artifact?

---

<div class="post-metadata">

**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\
**Post date:** [April 4, 2019, 7:17am UTC](https://hub.mender.io/t/porting-to-new-server/450/4 "2019-04-04T07:17:01Z")

</div>

Also note that there are less invasive ways of migrating.

You are able to configure multiple servers on the client side using the `Servers` configuration option, more on it here,

[https://docs.mender.io/1.7/client-configuration/configuration-file/configuration-options#servers](https://docs.mender.io/1.7/client-configuration/configuration-file/configuration-options#servers)

And if one migrates authentication data between servers the migration **should** be more seamless. There are plans on improving this workflow by providing more tooling or documentation but we are not there yet.

---

<div class="post-metadata">

**Author:** ![mterwoord](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mterwoord/32/100_2.png) [@mterwoord](https://hub.mender.io/u/mterwoord)\
**Post date:** [April 4, 2019, 7:30am UTC](https://hub.mender.io/t/porting-to-new-server/450/5 "2019-04-04T07:30:13Z")

</div>

I recently migrated to a new server. What I did was just point the DNS to the new server, and I could adopt the devices there.

---

<div class="post-metadata">

**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\
**Post date:** [April 4, 2019, 7:36am UTC](https://hub.mender.io/t/porting-to-new-server/450/6 "2019-04-04T07:36:03Z")

</div>

That is interesting @mterwoord. If you are able to share more details about the procedure I am sure that it will be helpful to the community.

---

<div class="post-metadata">

**Author:** ![mterwoord](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mterwoord/32/100_2.png) [@mterwoord](https://hub.mender.io/u/mterwoord)\
**Post date:** [April 4, 2019, 7:49am UTC](https://hub.mender.io/t/porting-to-new-server/450/7 "2019-04-04T07:49:44Z")

</div>

My situation was, that I had a “test” setup with 4-5 devices in it. I had to visit those 5 devices to reflash anyway, so I started setting up the production environment. New server, new images, etc. At some point i switched over my dns entry to the new server, andsuddenly the old devices appeared there. Not really more involved… The moment the old devices hit the new server it worked…

---

<div class="post-metadata">

**Author:** ![JohnS](https://avatars.discourse-cdn.com/v4/letter/j/87869e/32.png) [@JohnS](https://hub.mender.io/u/JohnS)\
**Post date:** [April 4, 2019, 6:01pm UTC](https://hub.mender.io/t/porting-to-new-server/450/8 "2019-04-04T18:01:04Z")

</div>

This is a good idea. Let me try it out and update here.

---

<div class="post-metadata">

**Author:** ![JohnS](https://avatars.discourse-cdn.com/v4/letter/j/87869e/32.png) [@JohnS](https://hub.mender.io/u/JohnS)\
**Post date:** [April 4, 2019, 6:05pm UTC](https://hub.mender.io/t/porting-to-new-server/450/9 "2019-04-04T18:05:03Z")

</div>

Multiple server configuration is a very good concept. Will check how it works. Thanks!

---

<div class="post-metadata">

**Author:** ![JohnS](https://avatars.discourse-cdn.com/v4/letter/j/87869e/32.png) [@JohnS](https://hub.mender.io/u/JohnS)\
**Post date:** [April 4, 2019, 6:08pm UTC](https://hub.mender.io/t/porting-to-new-server/450/10 "2019-04-04T18:08:40Z")

</div>

This is the way I practically prefer. Thanks for proving its feasibility. I am actually asking my IT manager to let me keep the old server domain as an alias of my new server. By doing this I won’t have to do any porting. It may not always work though, depending on how much my manager likes me. 😀
