Google has opened new migration tools for Gemini, which allow you to transfer to the service not only the history of communication with other AI assistants, but also the context they have collected about the user.
Google has opened new migration tools for Gemini, which allow you to transfer to the service not only the history of communication with other AI assistants, but also the context they have collected about the user.
According to Engadget, Gemini has two separate import scenarios. The first allows you to generate a special query to another AI service so that it summarizes everything it has «learned» about the user: writing style, key preferences, or personal details that help personalize responses. After that, such a summary can be inserted into Gemini. The second option involves transferring the entire chat history from another assistant so that you can refer to old conversations and tasks in Gemini.
The feature is available for both free and paid individual accounts, but is not yet available for business, enterprise accounts, or users under 18. Chat history is imported via a .zip file upload, with a file size limit of 5GB. Google has also renamed the past chats feature to memory to more clearly tie it to long-term context storage.
In essence, Google is trying to eliminate one of the main reasons why users don’t want to change AI tools: the loss of «memory» of previous experiences. If before, switching between bots meant starting from scratch, now Gemini is trying to take with it both old conversations and the user’s personal profile. This turns the competition between chatbots not only into a race of models, but also into a fight for convenient migration.
Back in early February, dev.ua wrote that Google was testing exporting chat history to Gemini with ChatGPT, Claude, and Microsoft Copilot. Back then, it was just a matter of preparing the feature, but now the company has actually launched it for users.
Also recently, a large number of Gemini users have been complaining about their chat histories disappearing. Some believe that the occurrence of this issue coincides with the launch of Gemini 3.1.
