Migration guide - anki import plain text

How to import plain-text flashcards into Deckbase

Plain text is the simplest import path. If your cards are stored as raw Q/A pairs with a consistent delimiter, you can migrate them in minutes with almost no preprocessing.

Deckbase5 min read

When to use this workflow

Learners with minimal-tech study files, exported chat logs, or simple text dumps who want the fastest possible migration.

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

Each card uses a consistent separator between front and back (tab, pipe, or custom delimiter).
One card per line with no multi-line breaks inside individual cards.
File is saved as plain UTF-8 text with no rich formatting.

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
Open your text file and confirm the delimiter is consistent across all lines.
2
Remove blank lines and trim leading or trailing whitespace.
3
Import into Deckbase and specify the delimiter used in your file.
4
Preview 20 cards to verify split accuracy.
5
Import the full file and start review immediately.

Common errors and fixes

Delimiter appears inside card content

Choose a delimiter that does not appear in your text, or escape delimiter occurrences.

Mixed delimiters in same file

Standardize to a single delimiter before import.

Line breaks inside cards split incorrectly

Replace internal line breaks with a placeholder, import, then restore inside Deckbase if needed.

Invisible characters cause parsing errors

Strip non-printable characters with a text cleaner before importing.

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: Capital of Australia | Back: Canberra
Front: SQL command to select all rows | Back: SELECT * FROM table_name;
Front: Define opportunity cost | Back: Value of the next best alternative foregone.

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

What delimiter should I use?

Tab or pipe (|) work best because they rarely appear inside normal card content.

Can I include tags in plain text?

Yes. Use a third delimiter to separate tags, or append them as a comma-separated field.

Is plain text the fastest import method?

Yes. It requires the least preprocessing and is ideal for simple Q/A datasets.

Import plain-text cards in under 5 minutes

Choose your delimiter, verify a preview, and start reviewing today.

Import plain text See CSV workflow

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

Query intent targeted: anki import plain text. This guide is reviewed as a practical migration workflow page, not a generic informational article.