Jan 19

Urgent: Feedback regarding data continuity and MultiAI Chat migration

While I understand the technical explanation, I am deeply concerned by the current approach to this transition.Maintaining two separate versions of the tool is not an efficient long-term solution; it creates significant operational friction and complicates project tracking. More importantly, the current workaround carries the implicit risk that the "old link" will eventually be sunset or deprecated. Without a formal sync or migration tool, users face the very real possibility of losing their entire chat history without notice once that legacy support ends.Data continuity should be a foundational element of any platform upgrade, not an optional feature. Expecting users to manually toggle between versions to access historical data is a significant regression in service.I strongly urge the team to prioritize a migration path or a bulk export tool to ensure our data remains secure and accessible within the new interface before the legacy version is retired.I look forward to hearing about a more robust resolution.ThanksSandeep

Pending