When Samsung pulled the plug on its Messages app for U.S. Galaxy owners earlier this year, the company offered a simple promise: switch to Google Messages and your conversations will come with you. For a growing number of users, that promise has not held up. Reports on Google’s own support forums describe text message histories vanishing after completing the migration, leaving people without access to personal conversations they had every reason to expect would survive the move.
The complaints share a pattern. Users followed Samsung’s official step-by-step instructions, set Google Messages as their default, and then discovered that some or all of their prior texts were gone. A thread on the Google Messages Community forum, titled “Messages missing when switching from Samsung to Google Messages app,” has drawn multiple reports describing the same outcome. One user wrote that every conversation older than a few weeks had simply vanished, while another reported that the transfer appeared to complete normally but left their inbox nearly empty. As of May 2026, neither Samsung nor Google has publicly acknowledged the problem or offered a fix.
What Samsung told users to do
Samsung confirmed the discontinuation of its Messages app for the U.S. market through a dedicated page on its website. The page directs customers to Google Messages and states that “messages and conversations will transfer” between the two apps. Samsung also published step-by-step support instructions for setting Google Messages as the default on Galaxy phones and tablets, framing the switch as the officially recommended path rather than a workaround.
The discontinuation applies only to the United States, a detail confirmed by The Associated Press. Galaxy owners in other markets can continue using Samsung Messages as before.
Samsung’s guidance does note that transfer time “depends on certain factors,” but the company does not specify what those factors are, how long the process should take, or what users should do if something goes wrong.
Where the transfer breaks down
The trouble shows up on the other side of that migration. On the Google Messages Community forum, users report that message histories disappeared after they completed the switch. The complaints are specific: people describe losing entire conversation threads, not just individual texts. One poster said their phone showed “zero messages” after the migration despite years of stored conversations. Another noted that group chats transferred but all one-on-one threads were missing. Some report that recent messages carried over while older ones did not. Others say nothing transferred at all.
The forum thread serves as a timestamped, public record hosted on Google’s own support infrastructure, which gives the complaints more weight than scattered social media posts. But notably, the thread contains no responses from Google product experts or engineers. That silence is unusual for threads that gain traction on the platform and suggests the issue has not yet been triaged publicly.
The bug does not appear to hit every user. Some Galaxy owners have reported smooth transitions with full message histories intact. But the consistency of the complaints, all describing the same symptom tied to the same officially recommended migration, points to a real gap in the transfer process rather than isolated user error.
Why the transfer might fail
Neither company has offered a technical explanation, but the architecture of the two apps provides some clues. Samsung Messages and Google Messages handle messaging protocols differently. Google Messages relies on Google’s own RCS infrastructure for rich messaging, while Samsung Messages historically used carrier-based RCS implementations. Standard SMS and MMS messages are stored locally on the device, but RCS conversations may be indexed and threaded differently between the two systems.
A mismatch in how those threads are stored, labeled, or referenced during migration could explain why some conversations transfer and others do not. Message format, thread length, and whether a conversation used RCS or plain SMS could all be factors, but without official confirmation, this remains informed speculation rather than a diagnosed cause.
It is also worth noting that neither Samsung Cloud backups nor Google’s built-in backup service have been confirmed to capture messages in a way that survives this specific app-to-app migration. Samsung Cloud can back up messages stored in Samsung Messages, and Google backups can preserve messages within Google Messages, but whether either service can bridge the gap between the two apps during the switch is unaddressed in both companies’ documentation. RCS-specific threads may be especially vulnerable, since those conversations are tied to each app’s own messaging infrastructure rather than stored as simple SMS records on the device.
The scale of the problem is also unclear. The support thread captures a visible slice of affected users, but there is no public data from Samsung or Google on how many people have attempted the migration or how many experienced data loss. Whether certain Galaxy models or Android versions are more susceptible is unknown.
What to do before you switch
For Galaxy owners who have not yet migrated, the most important step is one Samsung’s support pages do not prominently recommend: back up your text messages before changing the default app. Samsung’s own Smart Switch tool can create a full device backup, and well-known apps like SMS Backup & Restore (available on the Google Play Store) can export SMS and MMS histories to a file you control. Note that third-party backup tools typically capture SMS and MMS but may not preserve RCS conversations, so users with RCS-heavy histories should be aware of that limitation.
Users who have already switched and lost messages have fewer options. Filing a report through Google Messages’ built-in feedback channel is a starting point. Adding details to the existing Google support thread may also help establish the scope of the problem and push it toward an official response. But until one of the two companies acknowledges the bug, there is no confirmed recovery method for conversations that disappeared during the transfer.
For people whose missing texts include important personal, medical, or financial information, the lack of any recovery path makes the silence from Samsung and Google especially frustrating.
Samsung’s migration promise vs. the forum record
The core issue is straightforward. Samsung told millions of U.S. customers to take a specific action and assured them their data would follow. For some of those customers, it did not. The company’s own documentation made the promise in plain language, and its own instructions defined the migration path. When that path led to lost data, neither Samsung nor Google stepped forward with an explanation, a fix, or even an acknowledgment that something went wrong.
Samsung began directing U.S. users to Google Messages in early 2026, and the complaints on Google’s forum appeared shortly after. Months into the transition, the gap between corporate assurance and user experience remains unaddressed. Until one or both companies respond publicly, Galaxy owners navigating the switch are left to protect themselves.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
