Here is a forum thread on the Jellyfin forums from 2 days ago with an explanation and a solution. Looks like somehow the Roku Jellyfin client somehow has been marked as Beta which requires some extra steps for installation.

I have sets of both:

Sena 30k Cardo Packtalk Bold.

In my opinion the Sena 30k is terrible audio quality for music very tinny sound, no bass reproduction (not the primary purpose, but nice to have) and decent quality for communication. I had issues with being able to hear my riding partner, and issues with being able to hear while on the phone as well. I will say that the person on the other end did not have issues with hearing me (comms, or phone calls). Could have been placement of the speakers in my helmet, though I tried additional spacers and adjusting speaker placement with little to no change for myself.

Cardo Packtalk with JBL speakers is excellent quality for music (excellent given the size of the speakers, I mean they are 40mm speakers in a helmet not audiophile units) and decent quality for communication. I can say in the half dozen times I've needed to answer a phone call I could hear clearly, and the person I was talking to was unaware that I was on my bike.

In the end my wife and I use the Cardo system. More expensive than the Sena but overall we have been happy with them.

Unfortunately I do not have any experience outside the above. Comms are expensive and at some point I had to prioritize cash to other wants/needs.

While a direct migration does not exist, since you have access to the data on both instances it would theoretically be possible to export/import the database tables from one to the other. That will require digging and knowledge on your end to figure out which data needs to move over.

Another option would be to duplicate the database from the first instance and connect to that front the second instance. From there make the changes to the second instance by hand.

Just make sure before you go mucking about with and database imports you have a good solid backup in case things go south.

Note: The above is theoretical as I have not setup am instance of Lemmy of my own. Just typical of how a database works.