Import from Heptabase

Heptabase can export all your cards as Markdown, and Capacities can import Markdown. Your cards come across as notes. Your whiteboards do not, so you rebuild the ones you still need on a Capacities whiteboard after the import.

For general import docs, see:

Quick migration flow

  1. Decide which Heptabase tags should become Capacities object types.
  2. Create those object types in Capacities.
  3. Export everything from Heptabase.
  4. Import the Markdown files in the Capacities desktop app.
  5. Check the results, then rebuild the whiteboards you still use.

Warnings

  • Bulk Import runs in the Capacities desktop app, not in the browser
  • Whiteboard layouts do not import
  • Do not continue if the mapping looks wrong

Understand the paradigm shift

In Heptabase, every note is a card, and the whiteboard is where you work with them. In Capacities, every note has a type, like a Person, a Book, or a Meeting, and a whiteboard is one way of looking at notes you already have.

Your import will be cleaner if you decide what your cards are before you start. If you want a deeper explanation of this shift, read Understanding the paradigm shift.

How Heptabase organizes your content

All your cards live in the Card Library. A card can sit on as many whiteboards as you like, because whiteboards do not own cards. They only show them.

HeptabaseWhat it is
CardA note. There are also journal, highlight, PDF, video, audio, and image cards
WhiteboardA canvas where you place cards, draw arrows, and group them into sections or sub-whiteboards
TagA label on a card. Tags can have properties and nest inside each other
Tag databaseA table or kanban view of every card with a tag
JournalA card for each day
Links@ mentions between cards, with backlinks on each card

Translate to Capacities

Tags are the main decision. In Heptabase, a Book tag with properties like author and rating is doing the job of an object type. In Capacities, make it a real Book type.

HeptabaseCapacitiesNotes
CardObjectA Page, or a type like Book or Person
Tag that names a kind of thingObject typeAdd the tag's properties to the type
Tag that names a topicTag
Tag databaseObject type view or query (Pro)
JournalDaily notes
WhiteboardWhiteboard (Pro)Rebuild by hand
@ mentionObject link
PDF, image, audioMedia objects

Before you export

Create your object types in Capacities first, with the properties you want to keep. Use the same property names as in Heptabase, because the importer matches properties by name.

Export from Heptabase

  1. Open Heptabase on desktop or the web.
  2. Go to Settings > Backup and click Export now.
  3. Make sure files and images are included, so your attachments come with your cards.
  4. Unzip the download.

You get one Markdown file for each card, your attachments, and a file called All-Data.json. The Markdown files are what you import. Tags and properties are written at the top of each file, where Capacities can read them. All-Data.json holds your whiteboard layouts, which Capacities cannot import, but it is worth keeping as a backup.

Heptabase notes that other apps may not keep its whiteboard layouts, relationships, or metadata. Check a few cards before you import everything.

Import into Capacities

In the Capacities desktop app, go to Settings > Import Content and click Start importing in the Bulk import section. Upload the folder of Markdown files.

Before you import:

  • Check that each card is going to the right object type
  • Check that properties match the properties on your types
  • Optionally add an import marker so you can find everything later

Then click Analyze, review, and click Import. Keep Capacities open until the import is done.

After the import

Check:

  • Titles and object types
  • Properties and tags
  • Links between notes
  • Images and other attachments

Then rebuild the whiteboards you still use. Create a whiteboard and drag your imported notes onto it. In Capacities, the same note can sit on as many boards as you like, just like in Heptabase.

Are you missing something in the documentation?

Ask a question! - The Docs Assistant knows everything about the documentation, and the ideas and feature requests from other users.

Create a ticket on our feedback board. - Let us know if you have an idea for a feature, improvement or think there is something missing.

Request additions to the documentation. - If your questions are not getting answered, let us know and we will extend the documentation.