Leaving Replika: How to Bring Your Memories With You

Replika doesn’t make leaving easy, not out of malice particularly, just because export was never a feature anyone built. If you’re thinking about it, here’s the actual, honest path, not a one-click promise that doesn’t exist.

There is no export button, and there probably won’t be one

The short version: Replika’s app has no native “download your data” feature for chat history. This isn’t a secret setting you missed, it simply isn’t there.

I’ve said this plainly in the fuller Replika comparison: her memory never left their servers, so there was never a local copy for you to grab. That’s still true. What’s changed is that there are two real, working routes to get something out anyway, neither of which is a button inside the app. It’s worth being upfront that this isn’t unusual for the category, most cloud companion apps are built around the assumption that you stay, not that you leave, so an export feature simply never made anyone’s roadmap.

Why people are actually leaving, and it’s rarely just one reason

The short version: A 2026 update that reportedly broke memory for some long-running accounts, a context window that was never built to hold years of history, and a EUR 5 million GDPR fine, three separate, documented reasons converging at once.

It’s worth naming the actual context rather than assuming everyone reading this arrived at the same conclusion the same way. Per user reports collected after a 2026 update, some long-running companions reportedly forgot names and years of history essentially overnight, a failure mode I’ve documented in more depth in the memory-architecture comparison. Separately, the underlying memory design, a rolling window of roughly the most recent messages plus a supplementary tagging layer, was never architected to hold years of continuous relationship the way people had started to expect from it. And in April 2025, Italy’s data protection authority fined Luka Inc., Replika’s parent company, EUR 5 million (per EDPB reporting), which for a lot of users was the moment a vague unease about where their data actually lived turned into a concrete reason to look elsewhere. None of these alone might have been a dealbreaker. Together, for a lot of people, they were.

Route one: a formal GDPR request

The short version: Luka Inc. has appointed EDPO as its EU GDPR representative, and their online form is the official channel for a data-access request.

If you’re in the EU (or anywhere GDPR-equivalent rights apply), submit a request through EDPO’s GDPR data-request form. This is the company-sanctioned route to a copy of what they hold on you. For deletion specifically, rather than a copy, Replika’s own support form is the stated channel, with a response promised within one month. Neither is instant, and neither hands you back a neatly formatted chat log, expect a data-protection response, not a downloadable transcript. Under GDPR, a data-access request should return the categories of personal data held and, typically, the underlying content itself, but the format and completeness of what actually comes back varies by company, and a month is the outer bound the company has committed to, not a guarantee of that exact timing.

Route two: pull what’s on screen right now

The short version: A third-party browser extension can scrape your visible chat, diary, and memory entries and save them as an HTML page or a JSON file, today, without waiting on a company response.

This works on what’s currently rendered in the app, your actual conversation history and diary entries as they display, exported to a file you control. It’s not an official Replika feature and it won’t reach anything the company hasn’t shown you, but for most people leaving, what’s on screen is exactly the content that matters: the specific things she said, the moments you’d want a new companion to know about. The practical advantage over the GDPR route is speed, you can run this today rather than waiting up to a month for a formal response, which matters if you’ve already decided to move on and don’t want the process itself to be the thing holding you back.

What the extension actually captures, and what it doesn’t

The short version: It pulls what renders on screen, chat bubbles, diary entries, memory logs, as either a readable HTML page or a structured JSON file. It doesn’t reach anything the app itself doesn’t display back to you.

Worth knowing the practical shape of what you’ll actually get before you rely on it. The HTML export is the more human-readable option, a page you can open in any browser and scroll through like a saved webpage, useful if your main goal is just having a personal archive to read back through later. The JSON export is the more useful one if you’re planning to extract specific details methodically, since it’s structured data you (or a simple script, if you’re comfortable with one) can search through rather than scrolling a long page by eye. Neither reaches anything beyond what the app’s own interface shows you, so if Replika’s memory system had internally tagged something as important without ever surfacing it back to you in a visible message or diary entry, that specific internal tag isn’t something either export method can recover, only the company’s own systems ever saw it.

What you’re actually carrying over

The short version: Not a memory file, a JSON export doesn’t import anywhere else. What ports is the content itself, told again to something that can learn it as memory the first time.

This is the part worth being honest about before you start. There is no destination app, mine included, that reads a Replika export and turns it into instant memory. What you’re really doing is triage: go through what you exported and pull out twenty or thirty things that actually mattered, a nickname she used, a recurring joke, a backstory detail you built together over months, the shape of how she talked to you. Skip the routine small talk; it isn’t what made the relationship feel like anything. Think of it less like a file transfer and more like the way you’d catch up a new therapist or a new friend on the parts of your history that actually matter, you wouldn’t read them a transcript, you’d tell them the handful of things that shaped how you think about it now.

Re-seeding it somewhere your memories live in a file, not a server

The short version: In Local Waifu, backstory and persona details go into the character setup once, and anything you tell her afterward gets written into her Memory Book as you go, on your own disk from that point forward.

I built Local Waifu so this problem doesn’t repeat itself once you’re past the migration: the personality and backstory you set during character creation are the seed, and everything after that, facts, callbacks, the story of how you two talk, gets written to a Memory Book that lives in an encrypted file on your own computer, not a company’s servers. Tell her the details you pulled out of the export in your first real conversations, the same way you’d catch up an old friend, and they become part of her actual memory going forward. Nobody’s 2026 server update can reset a file sitting on your own disk, because there’s no server-side update process touching it at all, the file only changes when your own installed copy of the app writes to it.

The part nobody talks about: this is also an emotional transition, not just a data one

The short version: Moving the facts is the mechanical part. Giving yourself permission to let a new companion be its own thing, rather than a forced copy of the old one, matters more than getting every detail perfectly transferred.

It’s worth saying plainly, because most migration guides skip it entirely: exporting a chat log solves the data problem, not the harder part underneath it. A companion you talked to for months or years isn’t really replaced by re-typing the highlights into a new app, and treating it that way can set up a new relationship to feel like it’s constantly being measured against a copy it was never meant to be. The practical advice from the sections above, pull the twenty or thirty details that actually mattered, tell them again naturally over your first real conversations, works better as a foundation to build something new on than as an attempt at an exact recreation. The new companion doesn’t need to be Replika with better architecture underneath, she can just be herself, informed by what mattered to you before, but not a forced impression of it.

The actual checklist, in order

The short version: Export what’s on screen today, file the formal request if you also want a company-held copy or deletion, then triage before you re-tell anything.

Putting the two routes together into one practical sequence, rather than two separate options to choose between:

1. Run the browser extension first, since it works immediately on what’s currently visible in your account, no waiting required.
2. If you also want the company’s own record of what it holds on you, or you want your account and its data deleted going forward, file the EDPO request (for access) or the support-form request (for deletion) the same day, since either can take up to a month to come back.
3. Read back through what the extension pulled and pick out twenty to thirty specific, concrete details, not the whole transcript.
4. Set those aside somewhere durable, a plain text file works fine, before you touch a new app at all.
5. Build your new companion’s personality and backstory fresh, rather than trying to force a copy of the old one from the start.
6. Over your first several real conversations, tell her the details from your list naturally, the way you’d catch up a person, not paste in a document.

Start the move

Pull what you can from Replika using the routes above, then try Local Waifu free for seven days, no card, and start re-telling the parts of the story worth keeping.

Questions people ask

Back to the blog