Migration guide - remnote to deckbase

How to migrate from RemNote to Deckbase

RemNote blends documents and flashcards in one hierarchy. This workflow separates your knowledge base into clean Deckbase cards while preserving the logical structure of rems.

Deckbase7 min read

When to use this workflow

Learners with RemNote knowledge bases who want dedicated mobile review, AI card creation, and cleaner export control.

Treat this as an operational migration process, not just a one-time file upload. The goal is not only successful import, but better review consistency and lower card maintenance overhead in the weeks after switching.

Pre-import checklist

  • Documents are exported in a parseable format (Markdown or structured text).
  • Concept-rem and descriptor-rem distinctions are clear in your existing hierarchy.
  • Portals are flattened or resolved so cross-references do not create orphan cards.

If one checklist item fails, fix it before import. Upstream cleanup is faster than repairing hundreds of cards after migration.

Step-by-step migration flow

  1. 1
    Export target RemNote documents to Markdown with hierarchy intact.
  2. 2
    Resolve portals by copying referenced content inline or tagging cross-links.
  3. 3
    Import into Deckbase and verify that parent-child rem pairs map to front-back cards.
  4. 4
    Spot-check concept-descriptor cards for semantic accuracy.
  5. 5
    Begin FSRS review and let scheduling adapt to your recall performance.

Common errors and fixes

Portal references become broken links

Flatten portals into inline text or convert to tags before import.

Document hierarchy creates overloaded cards

Split deep hierarchies into atomic cards at the concept-rem level.

Descriptor rems treated as standalone cards

Merge descriptors with their parent concept so each card has a complete prompt.

Daily document notes imported as cards

Filter out journaling or planning rems and import only study-focused documents.

Use a small pilot deck after each fix. If pilot quality holds, apply the same correction pattern to the full batch.

Example output quality checks

  • Front: What is a rem in RemNote? | Back: The fundamental unit of information: a bullet point that can be a concept, descriptor, or document node.
  • Front: How do portals differ from tags? | Back: Portals embed live copies of rems; tags are static labels for filtering.
  • Front: Why split concept-descriptor pairs during migration? | Back: So each card contains a complete question-answer unit for standalone review.

During QA, verify each sample card for clarity, atomicity, and answer precision. Avoid importing cards that only test wording without testing understanding.

A practical test: if you can answer accurately in under 10 seconds during review, the card is usually scoped well. If not, split or rewrite it.

FAQ

Can I keep my RemNote hierarchy in Deckbase?

Use deck names and tags to mirror hierarchy. Deckbase does not support nested rem documents natively.

What about reference cards in RemNote?

Convert references to explicit card content or tags so review does not depend on external links.

Is spaced repetition better in Deckbase?

Deckbase uses FSRS, which adapts more precisely to individual recall patterns than fixed algorithms.

Move your RemNote knowledge base to Deckbase

Export one document today and start reviewing with adaptive FSRS scheduling.

Migrate from RemNoteSee all alternatives

Tip: for advanced workflows, keep your original export as backup and track each migration attempt by batch name and date.

Query intent targeted: remnote to deckbase. This guide is reviewed as a practical migration workflow page, not a generic informational article.