Export, import, migration and backups

This page is for administrators. It explains how to take a brain's data out of TomaTío 1.9.10, bring it into another brain, and back it up. Everything except backups is on TomaTío > Export and import: export and import side by side at the top, the other flows in their own boxes below, and the long explanations under About this page.

Export

Under Take everything with you, click Make a full export. You get one zip file in the open Portable Context Protocol (PCP) v0.3 format, signed with this brain's own key.

It holds the whole brain: memories, knowledge and procedures with their history, people, agents and scopes, house rules, documents and pages with their data and files, review requests, the audit log and forget receipts. It never holds passwords, keys, connection tokens, share-link tokens or settings. You cannot export only part of a brain.

An export is not encrypted. Keep it as carefully as the brain itself.

The archive is kept on the server for 24 hours by default (1 hour to 7 days, in Kept archives), so download it right away. Forget deletes every kept archive. If the server has no private folder for archives, the button reads Export and download and nothing is kept. A server admin can set one with AGENT_BRAIN_EXPORT_DIR in wp-config.php.

A big brain can take longer than a web request allows. Export it with WP-CLI (the WordPress command line) instead:

wp tomatio export --output=/secure/place/brain.pcp.zip

Migrate a brain here

Use this to move a brain to a new server.

1. Install TomaTío on a fresh WordPress site.
2. Make a full export on the old brain and download it.
3. On the new brain, open Migrate a brain here and choose the file.
4. Under Bind me to this person of the archive, pick who you were in the old brain.
5. Leave Dry run ticked and click Check or migrate. Nothing is written yet; read the report.
6. Untick Dry run and run it again.

For a big archive, use wp tomatio migrate <file> --user=<admin> --dry-run, then run it without --dry-run.

The new brain must be empty: no memories, knowledge, procedures, documents, pages, review requests, house rules, forget receipts, or scopes other than the one a new brain starts with. User accounts may exist. The migration is all or nothing. You can leave chosen scopes, people or agents behind.

Passwords, keys and connections never come over, and old share links do not work at the new address. Every person and agent comes back unbound, so nobody can sign in yet. Two sections of the page fix that:

• Principals: Bind and send link emails a person a link to set a password. Bind and make an application password gives an agent a new key, shown once.
• Reconnect: Send invitations to everyone at once, Make keys and download them for all agents, make share links again (Make a new link or Not needed), and free names claimed on shared pages (Release the name).

Then add every AI (artificial intelligence) connector again at the new address, as in Connect an AI.

Move scopes here

Use this to bring a project from another brain into this one while it is in use. Choose the scopes to move from the other brain's export. Their people and agents come too, as unbound accounts unless you match them to accounts here.

Everything waits for a person: pages go to the Review Queue, approved document sections go back to waiting for review, and no page version is live until someone approves it, unless you tick Keep approved what the source had approved. Share links are never brought over. Do a dry run first.

Import an archive

Use Bring pages in to add pages from another brain or another PCP tool: drop the archive on the box or choose it. They arrive as proposals in the Review Queue. Scopes, people and access here do not change. Documents, HTML (HyperText Markup Language) pages and earlier versions stay behind.

Under Options, choose a scope for the pages (import never creates one), and what to do when a page's path is taken: keep both, skip, or replace. Do a dry run first. Importing the same archive again skips what came in before. For an archive bigger than the server's upload limit, use wp tomatio import.

Signatures

When an archive this brain made comes back, one changed after export is refused. An archive from another brain cannot be checked, so it is accepted with a note that its origin cannot be verified.

Backups

Backups are in TomaTío > Settings > Backups. They need the optional TomaTío Cloud service, connected in the Summarising section.

• Turn on Back up every day and click Save, or click Back up now.
• Backups are encrypted on your site before they are sent. Click Generate and download backup key (later Download backup key) and keep the key safe: the cloud never has a copy.
• When a Forget completes, older backups are deleted and a new one starts.

There is no way to restore a backup yet: no button and no command. To be able to rebuild a brain, keep a recent full export somewhere safe.

Forget and uninstall

To remove a person's or a subject's data, see Memory. For what uninstalling removes, see Install.