# How to move a node between flows without deleting it and losing its unique ID

**URL:** https://discourse.nodered.org/t/how-to-move-a-node-between-flows-without-deleting-it-and-losing-its-unique-id/52408
**Category:** General
**Created:** [19 October 2021 10:20 UTC](https://discourse.nodered.org/t/how-to-move-a-node-between-flows-without-deleting-it-and-losing-its-unique-id/52408 "2021-10-19T10:20:50Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![bwims](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bwims/32/64907_2.png) [@bwims](https://discourse.nodered.org/u/bwims)
#### Post date: [19 October 2021 10:20 UTC](https://discourse.nodered.org/t/how-to-move-a-node-between-flows-without-deleting-it-and-losing-its-unique-id/52408/1 "2021-10-19T10:20:50Z")

</div>

I am using an Alexa skill / node red contrib that provides virtual Alexa devices to Node Red.  
It works wonderfully, but since it uses the node red node ID to create the virtual device in Alexa, if you need to move the node to another flow the whole process becomes rather tedious in terms of deleting the duplicate device and rediscovering it in Alexa.

Is there a way to move a node between flows that I am unaware of?

All I can think of is to move everything else out of the flow to another flow and rebuild around the device node.

Thanks!

---

<div class="post-metadata">

### Author: ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [19 October 2021 11:26 UTC](https://discourse.nodered.org/t/how-to-move-a-node-between-flows-without-deleting-it-and-losing-its-unique-id/52408/2 "2021-10-19T11:26:59Z")

</div>

There isn't a built-in way to move a node to a different tab and preserve its ID.

But you can achieve it by selecting the node, exporting its json to your clipboard (Ctrl-E), delete the node, then import its json on the other tab. This will keep the node's id intact.

---

<div class="post-metadata">

### Author: ![bwims](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bwims/32/64907_2.png) [@bwims](https://discourse.nodered.org/u/bwims)
#### Post date: [19 October 2021 12:04 UTC](https://discourse.nodered.org/t/how-to-move-a-node-between-flows-without-deleting-it-and-losing-its-unique-id/52408/3 "2021-10-19T12:04:15Z")

</div>

Is that a new feature of a recent version of Node-Red? I am running 1.1.3 and the node id changes when I try to export/import it.

Is a deployment essential at an intermediate stage? I'm sure I've tried it both ways.

Many thanks for replying!

---

<div class="post-metadata">

### Author: ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [19 October 2021 12:07 UTC](https://discourse.nodered.org/t/how-to-move-a-node-between-flows-without-deleting-it-and-losing-its-unique-id/52408/4 "2021-10-19T12:07:49Z")

</div>

The behaviour was changed in 1.2 to not generate new ids by default - [Version 1.2 released : Node-RED](https://nodered.org/blog/2020/10/15/version-1-2-released#importing-duplicate-nodes)

---

<div class="post-metadata">

### Author: ![bwims](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bwims/32/64907_2.png) [@bwims](https://discourse.nodered.org/u/bwims)
#### Post date: [19 October 2021 12:20 UTC](https://discourse.nodered.org/t/how-to-move-a-node-between-flows-without-deleting-it-and-losing-its-unique-id/52408/5 "2021-10-19T12:20:41Z")

</div>

That's great! Thank you!

Lastly, could you point me at any notes or articles on hazards upgrading from 1.1.3 to 1.2? I haven't upgraded a "production" machine yet...

Thanks again!

B.

---

<div class="post-metadata">

### Author: ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [19 October 2021 12:23 UTC](https://discourse.nodered.org/t/how-to-move-a-node-between-flows-without-deleting-it-and-losing-its-unique-id/52408/6 "2021-10-19T12:23:23Z")

</div>

The link I sent previously was the release blog post for 1.2 - it will cover any thing you need to be aware of.

We would always recommend testing the upgrade first - and make sure you have a good backup you can quickly restore in case something unexpected happens.

---

<div class="post-metadata">

### Author: ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [19 October 2021 12:24 UTC](https://discourse.nodered.org/t/how-to-move-a-node-between-flows-without-deleting-it-and-losing-its-unique-id/52408/7 "2021-10-19T12:24:35Z")

</div>

If you are going to upgrade, and don't want to move the current 2.x stream, we would also recommend you upgrade to the latest in the 1.x stream - 1.3.7.

---

<div class="post-metadata">

### Author: ![bwims](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bwims/32/64907_2.png) [@bwims](https://discourse.nodered.org/u/bwims)
#### Post date: [19 October 2021 21:14 UTC](https://discourse.nodered.org/t/how-to-move-a-node-between-flows-without-deleting-it-and-losing-its-unique-id/52408/8 "2021-10-19T21:14:09Z")

</div>

Thanks Nick, you are a brilliant resource! Sorry to be such a noob, but are there any particularly scary aspects to going to 2.0? I feel another Raspberry Pi coming on...

Thanks!

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)
#### Post date: [18 December 2021 21:14 UTC](https://discourse.nodered.org/t/how-to-move-a-node-between-flows-without-deleting-it-and-losing-its-unique-id/52408/9 "2021-12-18T21:14:41Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
