PARAS MADAN
All writing

Latest in AI

Mem Is Shutting Down: Export Notes, Attachments and Meeting Audio

Mem becomes read-only on December 18 and closes January 15. Save a verified archive, then choose an Obsidian or Notion migration route.

Mem users have two deadlines, and they mean different things. Notes become read-only on December 18, 2026. Mem shuts down on January 15, 2027. Reading and exporting remain available during the read-only period, but access ends with the shutdown. Download your library beforehand rather than treating January 15 as an export day.

The November 16 announcement also says charging has been paused and users will not be charged again. Previously paid features and limits remain available for the remaining service period, subject to the read-only change.

I would separate this into two jobs: preserve the library first, then decide where to work with it. This guide follows Mem's published instructions. I have not run an export or tested an import, so the verification steps below are checks to perform, not completed results.

Download a copy before choosing a replacement

Mem's download instructions start on a computer in Settings → Exports. Select Start new export, then My Computer → Next. Review the options and start the export. A first export may go directly to destination selection. Return to the export entry and download its ZIP when ready.

If meetings matter, check the audio option before starting. Available transcripts are included by default, but original recordings require that selection and can substantially increase the download. A meeting note, transcript and recording are separate items.

Keep the original ZIP and unpack a working copy. The documented layout contains notes/ with Markdown files, collections/ with indexes, and attachments/ with available referenced files. Preserve their relative arrangement. If export-report.md is present, inspect it for omissions.

Choose a private storage location appropriate for the information in your notes. A library accumulated over several years may contain client details or old credentials you no longer remember saving. Do not upload the archive to a conversion service just because its landing page promises an easy migration.

Check the archive before reorganizing it

Mem's migration checks recommend inspecting familiar notes, collection membership, attachments and meeting content. A ready export can still have missing items. If an entry shows Needs attention, inspect its result; use Retry if offered for a failed entry. For a Markdown download, the export report can identify flagged items.

My acceptance check would use a small sample selected before the move: one long note, one image-heavy note, a PDF, a note in two collections, and a meeting whose recording matters. Record whether each opens in the archive and later in the destination. That separates an export omission from an import problem.

For an unresolved issue, Mem lists support@mem.ai and asks for the destination, export start time and status or error. Start with those details rather than sending your whole archive. Give yourself enough time to investigate while Mem is still accessible.

Obsidian: open the parent folder

The Mem-to-Obsidian guide says both Obsidian and My Computer export choices produce Markdown. In Obsidian, choose Open folder as vault and select the folder containing notes/, collections/ and the attachments. Selecting only notes/ leaves the other material outside the vault.

I would try this route first if the immediate goal is to inspect a file-based copy without committing to another hosted workspace. Keep cleanup separate from recovery: changing folder names and reorganizing attachments before checking links creates another possible cause of failure.

Notion: choose one import route

Mem's Notion instructions offer a direct transfer through Create pages in Notion or a ZIP for manual import. The direct route asks you to connect the intended workspace and grant access to the destination page. The manual route uses Notion's desktop or web Settings → Import → Text & Markdown with the ZIP still compressed.

Use one route for a given batch. Mem warns that importing the same files again can create another set of pages. Check the workspace and destination permissions before transferring private notes; a successful import into the wrong shared location is still a failed migration.

Set a cutover date

The migration overview says to export again if you edit notes after saving your first copy. Decide when new writing moves to the replacement, and label each archive with its export date. Do not mistake a month-old download for the final state of your library.

Finish when the important content is readable, required files open and you know where new notes will go. A replacement app can be refined later. Recovering something you never exported may not be possible after the service closes.

I'm Paras. I work at the intersection of AI, engineering and distribution.

I help teams turn product changes into practical migration guides with clear checks and data boundaries.

Book a 30-minute call.