Migrate from Mem with a conversion-first workflow.

Important: This is not a one-click move. Capacities does not import a Mem workspace directly. You export or copy notes as Markdown, make sure you have one Markdown file per note, then import in the Capacities desktop app. If Mem gives you one big file with every note inside, you need to split it before Bulk Import.

For general import docs, see:

• Import content to Capacities
• Bulk Import Reference

Quick migration flow

1. Decide how Mem collections should map to Capacities object types or tags.
2. Export or copy your notes as Markdown.
3. Split into one Markdown file per note if needed, and keep media nearby.
4. Review mapping in Bulk Import, then import on desktop.
5. Check results, then continue in batches if needed.

Warnings

• Mem's help docs do not clearly show a full-workspace Markdown export path
• Bulk Import expects separate Markdown files, not one combined archive
• Bulk Import runs in the Capacities desktop app, not only in the browser
• Do not continue if mapping looks wrong

Understand the paradigm shift

Mem is collection-first and AI-assisted. Capacities is object-type-first.

Your migration will be cleaner if you first decide which notes should become typed objects (for example Person, Project) and which should stay as Pages or tagged notes.

If you want a deeper explanation of this shift, read Understanding the paradigm shift.

How Mem organizes your content

Mem avoids folders. Instead, it combines notes, flexible groupings, and AI-assisted retrieval.

Mem also has AI features that shape daily use but are not part of exported note files:

• Auto-organize suggests or creates collections for notes
• Chat answers questions using your notes as context
• Heads Up surfaces related notes while you work
• Related notes finds semantic connections without manual linking

What usually travels with a note is the title, the body text, which collections it belongs to, and when it was created or updated. Version history, AI chat history, and meeting transcript extras usually stay behind in Mem.

Translate to Capacities

Mem's collections feel like tags, but they are often used like project buckets. Capacities gives you a clearer split: object types for what something is, tags for cross-cutting themes.

The Capacities editor works differently

Mem makes it easy to keep adding to a note over time, then find related content through search, collections, or AI.

Capacities uses a block-based editor with linear flow. Notes read top to bottom in blocks, with fewer layout options than a free-form canvas. Structure comes from linking between notes with @ or [[...]], not from letting one note grow until it holds a whole topic.

When a Mem note mixes several subjects, split it into separate objects before import and link them in Capacities. Replace Mem's automatic related-note surfacing with explicit object links, tags, and queries.

If you use Mem mainly for AI-driven organization without building your own structure, Capacities may not be the right fit. Capacities expects you to define object types and links yourself. We do have an AI assistant and related content features, but it is not built in the same way as Mem's.

Decide collection by collection

Review your collections before export.

Topic collections → Capacities tags:

• Self development, Investing, Knitting → tag imported notes (any object type)

Noun collections → object types:

• Clients, Meetings, Books, Ideas, Writing → create matching object types

Project collections → object type or tag:

• Website relaunch can be a Project object type for notes that belong to that project, or a tag on mixed Page notes

Because one Mem note can sit in many collections, pick one object type per note in Capacities and turn the other collections into tags.

Example mappings

Standalone capture

• Mem: note Compound interest basics, collections Investing, Self development
• Capacities: Page with tags #Investing and #Self development

Meeting note

• Mem: note Kickoff - Acme, collection Meetings, @ links to Acme Corp
• Capacities: Meeting object, link to Person or Project objects if those notes exist

Template-based note

• Mem: note created from a Weekly review template
• Capacities: Page (or a custom type you create), then rebuild the template in Capacities if you still use it

Map structure before export

Create key object types first (People, Projects, Meetings, and so on), then add core properties.

Look at your Mem collections and group notes into clear noun-based buckets where you can (for example People, Projects, Meetings).

Then create matching object types in Capacities before import.

Mem collections can map well to Capacities tags when a note does not need its own object type. For collections that are not noun-like (Inbox, scratch notes, planning), either:

1. Restructure notes into noun-based groups before import, or
2. Import as Pages (good for free-form notes, but without properties).

Export from Mem

Mem supports Markdown in places, but its help docs do not spell out a reliable, step-by-step full-workspace export. Treat export as something you verify with a small test first.

Practical options:

• Small set: In Mem, use Copy as Markdown from the note menu (...) for one note or a few notes, then paste into Capacities or save each as its own .md file
• Larger set: Look for Mem’s Markdown export if your account has it. Exports are often emailed as a download link. Many people receive one large Markdown file with many notes inside (sometimes separated by horizontal rules). Split that file into separate .md files before Bulk Import
• By collection: Export or copy in batches by collection so you can map and import one group at a time

We cannot confirm every menu label from Mem’s official docs alone. If a step does not match what you see in Mem, start with copy-as-Markdown on a few notes so you know the format before you move a large library.

Prepare Markdown files for import

Capacities Bulk Import works best with one Markdown file per note (plus any media those notes use).

Before importing:

• Split any combined export into separate .md files if needed
• Put files for one object type in one folder when you can
• Keep filenames clear and unique
• Keep media files with the notes that use them

Review mapping, then import

In the Capacities desktop app, go to Settings > Import Content, open the Mem guide in Migration guides, then click Start importing and upload your folders.

Before importing:

• Confirm recognized object types are correct
• Optionally add an import marker
• Stop and fix setup if preview looks wrong

Then click Analyze, review, and click Import. Keep Capacities open until import completes.

Verify after import

Check:

• Titles and object types
• Key properties (dates, tags, and similar details)
• Internal links (where present)
• Attachments and media