Imports and exports

tinymash provides separate workflows for source-system migration, editable tinymash transfer, maintained Markdown publication, recovery backups, and static publishing.

Content importers

The Blogger, WordPress, and Bludit import plugins create a preview before writing content. Browser imports run in resumable batches. CLI variants are better suited to large source files and long imports.

Always inspect the target owner, entry type, publication state, dates, slugs, media handling, and preview warnings before applying an import. Create a verified backup first. A replace option can delete every existing post or page in the selected target, not only entries with matching slugs.

tinymash transfer

The core CLI can export and import a whole site or one author. Plugin data is included only when requested and supported by the plugin. These commands transfer tinymash state; they are not replacements for a full operational backup policy.

Maintained Markdown

Markdown Sync pushes a directory of page sources beneath an entry point selected by the receiving site. Stable source IDs preserve receiver identity across edits and moves. The receiver detects local edits and does not overwrite conflicts silently.

Static export

Static export writes a browsable, PHP-free copy of supported public routes and local assets. It is publishing output, not an editable tinymash installation and not a backup of private source state.