What happens to your tags if you change platform?

The tags always survive

A tag is a chip and an antenna holding a small amount of content. Nothing about a platform change touches it.

Unless it was locked, it can be rewritten. If it holds an address you control, it may not even need rewriting.

So the physical layer of a home automation deployment is the durable part, which is the opposite of what people assume when a platform changes.

What is lost is the logic, and where the logic lived decides how much work that is.

The decision you already made

If your automations were configured inside a phone application tied to the platform, they go with the platform. Every one has to be rebuilt.

If your tags hold addresses on a domain you own, the tags stay where they are and only the destinations change. That is an afternoon.

If your tags hold addresses belonging to the platform, they point at something that no longer exists and every tag must be physically rewritten.

Nobody makes that choice deliberately at the time. It is made by whichever route was easiest when the first tag was written.

What a migration involves

Listing what you have, which is the step nobody can do from memory after two years.

Recreating each scene in the new system, with the same names if the tags refer to them by name.

Rewriting tags, if they held platform specific addresses.

Testing each one, since a scene recreated from memory is usually missing a step nobody remembers until a light stays on.

And telling the household, because everything they relied on changed at once.

What to do now

Write down which tag is where and what each one does. A page of notes, kept somewhere findable.

Use addresses on a domain you own for anything you intend to keep, even where the platform offers something easier.

Never lock a home tag, so rewriting stays possible.

And keep scene names stable and generic, so a name like the evening scene survives a platform change while one naming a specific product does not.