Local Data and Backups

MikroPlan has two storage modes: browser-local storage and API-backed SQLite storage.

Local Mode

In local mode, MikroPlan stores the workspace in IndexedDB for the current browser profile and origin.

The workspace includes:

boards
columns
work items
comments and image assets
labels
people
active board metadata

Browser storage is private and convenient, but it can be removed by browser cleanup, site-data deletion, private browsing behavior, profile resets, or origin changes.

API Mode

In API mode, the Node server stores the workspace in SQLite. By default, the database file is data/mikroplan.sqlite.

databasePath is not part of the JSON config surface. Set MIKROPLAN_DB_PATH only when a deployment needs a different storage file.

Export Data

Use Export data to download a JSON file with boards, columns, work items, comments, labels, and people. Data export does not include image files.

Use this when you want a small, scriptable, portable data file.

Export Archive

Use Export archive to download a ZIP backup. The archive contains workspace.json, manifest.json, and any uploaded image assets. Images are stored as a compressed display image plus a smaller thumbnail.

Use archives before clearing browser data, moving to another deployment, or testing risky edits on an important board.

Import

Use import to restore a JSON data file or ZIP archive. Import replaces the current workspace with the imported data.

When importing into API mode, the imported workspace is saved through the API and becomes the shared server workspace.

Import is intentionally for MikroPlan backup formats. Vendor exports from Trello, Jira, Linear, or other SaaS tools should be treated as source material for a migration step, not as files MikroPlan opens directly.

Moving Between Modes

To move local work into API mode:

Export data or export an archive from the local board.
Start MikroPlan in API mode.
Import the backup.

To move API work into local-only mode, export from API mode and import in the static app.