Migration errors

looking for some input if anyone has run into this issues with any of there migrations, i opened a ticket with support and got the generic link to the wiki... which i've tried in my orignal migrations and still not having any success, hoping that someone here might be able to share there experiences if they were similar

Issue Summary: I recently migrated from an eisy v1 (which was stable for years) to a new eisy v2. Since the migration and backup restore, I have been unable to achieve stable two-way communication, despite testing three different PLM units and moving the controller to multiple physical locations.

Detailed Timeline:

• Initial Migration: Upon the first restore to the eisy v2, the original PLM (2413S with the serial-to-USB adapter) was not recognized at all. Despite multiple reboots and full factory resets of the PLM (holding the set button until the beep stopped), the eisy v2 would not acknowledge the hardware.

• New Hardware (2413U): I purchased a brand-new USB PLM (2413U). The eisy v2 discovered this unit immediately. I performed a Restore Modem, and while the system appeared to function initially, I began experiencing "one-way" communication issues.

• Linking Failures: Multiple existing switches stopped reporting status updates to the interface. Furthermore, when attempting to add a new KeypadLinc, I consistently received the error: "Cannot determine device link table address".

• Isolation Testing: I attempted to "Restore Device" on several switches; however, the communication was too unstable to complete the writes. I physically moved the eisy v2 and PLM to a different part of the house to rule out local interference, but the "Reason 9" timeouts and status update failures persisted.

• Regression Test: I attempted to revert to the original PLM and even a third, brand-new-in-box 2413S unit. The eisy v2 continues to fail in recognizing the older serial units and maintains unstable communication with the USB unit.

Request: Because this mesh was 100% stable on the eisy v1 and the issues persist across multiple PLMs on the v2, I suspect a hardware defect in the eisy v2's USB bus or a corruption in the migrated link database.