tinymash transfer

The core transfer commands move editable tinymash state. Use them when the destination is another tinymash installation and the content must remain manageable there.

This is different from a static export, which produces public files, and from an operational backup, which is designed for recovery.

Site transfer

php8.4 bin/tinymash.php export:site /path/to/site-export
php8.4 bin/tinymash.php import:site /path/to/site-export

The export destination must be prepared for the command and should be stored outside the public web root. Add --with-plugins only when plugin-owned export data is required. The receiving installation must have the corresponding active plugins before importing that data.

import:site --replace-existing permits conflicting site state to be replaced. Run the command help and inspect the destination before using it.

Author transfer

php8.4 bin/tinymash.php export:author cajo /path/to/cajo-export
php8.4 bin/tinymash.php import:author /path/to/cajo-export NEW-PASSWORD

The author import sets a new local login password. The password argument is visible in the process list and can enter shell history. Run the command only in a trusted local shell, then clear or rotate the exposed credential as appropriate.

Use --replace-existing only when the destination conflict policy has been reviewed. Plugin data is optional through --with-plugins on both export and import.

After transfer

Check users, account state, author slugs, root aggregation, posts, pages, drafts, media, menus, active plugins, and private settings. Clear the destination cache after a large transfer and keep the source bundle private until it is no longer needed.