After DeepSeek's old conversation limits, official and community channels offer multiple migration solutions
Starting November 15, DeepSeek App and web users have successively seen limit prompts; some long conversations inactive for more than 72 hours are temporarily unavailable, while other users see a 7-day limit, and pop-ups suggest exporting history records for use in other apps. On November 13, DeepSeek opened application APIs including web search, deep-thinking search, PDF reading, web reading, speech recognition and speech synthesis, and open-sourced the chat client Chat Demo, whose documentation supports importing DeepSeek Chat history records, but importing will replace all original local conversations and attachments in the client. The article also introduces the experimental session import plugin for DSH v0.2.2-rc.3, the community plugin dsh-chat-migration, the browser extension DeepShare and the offline browsing project deepseek-keeper, and recommends first downloading raw records from the data management page as a backup.
Why read this
AI score 62
The article brings together the limit phenomenon with several official and community migration paths, helping readers determine how to back up and continue old conversations.
Topics
Body · AI translation
I suggest everyone "plan ahead" and, while DeepSeek is still usable, have it do a summary and review first: what has been discussed before, which requirements have been confirmed, and what remains unfinished.
DeepSeek has produced two pieces of news in the past two days. Looked at together, they are somewhat both amusing and exasperating.
On November 13, DeepSeek announced the opening of a full set of application APIs. Web search, deep-thinking search, PDF reading, web page reading, speech recognition, and speech synthesis can all be integrated by developers into their own products. The official team even open-sourced the ready-made chat client code as well.
Two days later, a group of users discovered that their old DeepSeek conversations suddenly "could not continue."
Starting November 15, quota prompts began appearing successively on the app and web versions. Some users received "insufficient compute power," with long conversations inactive for more than 72 hours temporarily unavailable, while others saw a limit of 7 days.
The pop-up also included a line: "Historical records can be exported for use in other apps."
As of today, feedback such as a single input of about 40,000 characters and suspension of use after the daily quota is reached has also appeared in concentrated form.
01
Chat records are still there, but continuing the conversation is troublesome
Phoenix Technology searched online posts and found that most users currently report that old DeepSeek chat windows can still be opened and previous questions and answers can still be browsed, but messages can no longer be sent.
In the DeepSeek community on Reddit, one user said that multiple chat windows they had accumulated were restricted, with only a few still usable.
Another user began looking for ways to transfer historical records. He first exported a ZIP from DeepSeek, then asked ChatGPT to help split it into JSON files, attempting to migrate the original chat content over.
But exporting files does not equal restoring conversations.
The original chat records were too long, and the new platform could not receive all the content at once. That user could only rely on other models to repeatedly organize the material, compress the historical records in segments, extract important information, and then gradually put it into new chat windows.
Some users encountered an even more awkward situation:
They wanted DeepSeek to help summarize what had been discussed before as background material for a new conversation, only to find that the old window could no longer reply, making even this last step impossible.
Phoenix Technology checked its own DeepSeek and found that, as of press time, conversation records from January 2025 could still normally send messages and receive corresponding contextual replies.
For example, when using DeepSeek to revise an article continuously, a user may have already spent several days telling it which expressions cannot be used and which paragraphs have been finalized. Starting over in a different window means these requirements must be reorganized.
Although chat records can be exported, getting another model to fully absorb the context and then continue the previous work is not so easy.
There is a detail in this quota limit: some of those affected are long conversations that have not been used for some time.
From a technical perspective, this may be related to the computational cost of long context.
A chat window used continuously for several months may have accumulated dozens or even hundreds of rounds of questions and answers. If a user reopens the window and continues asking questions, how much historical content the model needs to process depends on how the system manages context.
DeepSeek had previously adopted context caching technology, which can reduce the computational overhead of repeated content. But the cache does not remain forever. If a long conversation has not been used for a long time, after the original cache expires, processing a large number of historical messages again may incur higher costs.
This also makes "inactive for a long time" a noteworthy restriction condition.
However, DeepSeek has not yet announced the specific technical reasons for this quota limit.
Why some users see 72 hours while others see 7 days, and whether this is also related to conversation length or account usage, has not yet been clearly explained.
For chats that can no longer continue, users can first export historical records; both official and community migration tools are available to try.
03
The official team has just launched two migration paths
On November 13, DeepSeek opened a full set of application APIs and also open-sourced the chat client Chat Demo.
Chat Demo provides a ready-made chat interface. After configuring the DeepSeek API Key, it can call the model and functions such as search, file reading, and speech. Developers can deploy it themselves or modify it on that basis.
The official documentation also includes a feature: it supports importing the history of DeepSeek Chat and continuing the conversation in the new client.
However, note that according to the official instructions, the import operation will replace all original local conversations and attachments in the client. Therefore, if other chat records have already accumulated in Chat Demo, it is best to back them up first before performing the import.
Another tool is DeepSeek Harness (DSH).
Also on November 13, DSH released the v0.2.2-rc.3 preview version, which added an experimental DeepSeek session import plugin.
It can import historical records from the DeepSeek App or web version into the workspace.
Compared with Chat Demo, DSH is more oriented toward an Agent work environment, and imported chats can be used together with files and tasks.
However, it is still an experimental feature and requires users to enable it themselves.
Both tools support migrating history records, but the barriers to use differ. Chat Demo requires configuring an API Key and bearing the call costs, while DSH requires installing and configuring the corresponding plugins and model services.
04
Beyond official tools, there are several more convenient ways to move
In addition to the Chat Demo and DSH released officially by DeepSeek, community developers have also made some tools specifically for handling historical chat records.
For example, dsh-chat-migration, released by developer Xiaozhuang, is a community plugin that adds DeepSeek historical conversation migration capabilities to DSH.
It actually contains two plugins: "Import Conversations" and "Chat Mode."
The former can read the JSON or ZIP exported officially by DeepSeek, preview the original chat records, and then select the conversations to migrate. Titles, chronological order, question-and-answer content, and the thinking records saved in the export file can all be converted into chat records in DSH.
Conversations that have already been imported will also be marked, so they can be skipped when importing again.
"Chat Mode" provides an entry point closer to ordinary chat software, so there is no need to bind a workspace every time.
Note that this community plugin and the DSH official experimental import plugin mentioned earlier are different projects, and their installation methods are also different.
If you do not usually use DSH, you can also take a look at the browser extension DeepShare.
Its operation is closer to the chat page familiar to ordinary users.
Users first download their history records from DeepSeek, and DeepShare can then build a local history library in the browser. After that, they can search past chats, select the passages they need, and organize them into Markdown files.
For example, if you previously revised an article repeatedly with DeepSeek and want to continue writing it with another AI, you can first organize the discussions related to that article and then upload the Markdown file to a new chat window.
DeepShare also supports directly placing selected history records as attachments into a new DeepSeek conversation.
However, this method only lets the model re-read the old content; it does not restore the original chat thread.
According to the developer documentation, the parsing, searching, and Markdown generation of history records are all completed locally in the browser, with no need to configure an additional API Key.
If you do not even need to continue chatting and only want to preserve past records, there is also an open-source project called deepseek-keeper.
It is mainly used for offline browsing of DeepSeek chat records. Historical content can be viewed in a terminal or browser, making it suitable for local backups of old chats.
These tools can all start from the history files exported by DeepSeek, but their handling methods differ.
If you want to preserve the conversation format and continue using DSH, you can consider the conversation import plugin; if you want to organize old content for other AIs to use, DeepShare provides a lighter-weight approach; if you only want to archive, there is no need to deploy a dedicated chat client.
Whichever tool you choose, it is best to first download the original history records from DeepSeek's "Data Management" page and keep a backup.
Export files may contain private chats, work documents, and other sensitive information. Before using third-party tools, it is advisable to confirm whether the files need to be uploaded to external servers, and it is also best to save separately attachments such as PDFs and images used in the original chats.
Finally, I still recommend that everyone "prepare for a rainy day": while DeepSeek can still be used, first have it do a summary review: what has been discussed before, which requirements have been confirmed, and what remains unfinished.
After all, when you really run into quota limits, no matter what you say, it will ignore you.
This article is from the WeChat public account "Phoenix Technology", author: Shi Yan, editor: Dong Yuqing, published by 36Kr with authorization.
AI Trends