Back up and move your data
Everything you have built in Player One can be taken out as a file you keep, and put back into this installation or a different one. This is one of the few things you do on a page rather than by asking: Admin > Backups (/admin/backups), which opens on the Project Bundle tab. The other tabs export one kind of thing at a time, with Import and Audit Log at the end. Your assistant can explain any of it from the Help panel, but the export and the import are yours to press.
What a backup contains
A project bundle is one whole project in a single download: its agents, workspaces, Memory Spaces, flows, jobs, scheduled tasks and contact lists. Each is a tick box with a count beside it, so you can leave out what you do not need.
Three further choices sit underneath. Workspace files carry the documents your agents work in, which can be large. Agent-private skills carry what one agent has been taught. Memory Space content always travels with the Memory Space.
The Skills tab (/admin/backups/skills) is the one export not tied to a project. Built-in skills never travel, though your notes on them do.
What never travels
Nothing that signs in on your behalf. Your AI provider accounts, messaging and email authorisations and the tokens behind a knowledge source stay where they are, so an archive is never a set of keys to your business. You reconnect them on the receiving installation.
Chats do travel, if you ask for them. A chat carries its whole conversation, the files uploaded into it, its title and the project it belongs to. What it does not carry is where it was sent from: a chat that arrived over Telegram or WhatsApp comes back as a web chat, because the messaging account stays with the installation that owns it. Chats are off by default in a project bundle, because conversations and their uploads are usually the largest thing in the file.
One exception is yours to make deliberately. A Secrets box writes the credentials an agent holds into the archive in readable form. Leave it off unless you control the destination and have somewhere safe to keep the file.
Export your work
- Open Admin > Backups (
/admin/backups). - Under Project scope, choose one project, or All projects.
- Tick the kinds of thing to include; the count beside each says how many are in scope.
- Decide on workspace files, agent-private skills and secrets.
- Select Create Project bundle. Player One adds whatever your choices depend on, so a flow arrives with the agents it needs.
- When the export shows as ready below, select Download all. A large export arrives in several parts and you need all of them.
- Keep the file somewhere of your own. Links expire, and Re-run makes a fresh archive from the same choices.
Import it into an installation
- On the installation receiving the work, open Admin > Backups and go to the Import tab (
/admin/backups/import). - Drag in every part of the archive together and wait for the uploads to finish.
- Select Preview changes. Every item is listed as new, as a clash with something already here, or as missing something it needs.
- Untick anything you do not want. Dependencies stay in whether you tick them or not.
- Map the projects. An existing one is matched for you, a match by name asks you to confirm, and anything unmatched offers to create a project.
- Decide each clash. An import merges rather than replaces: keeping the copy already here is the default, overwriting is deliberate, and a kept item can still add to project.
- Select Review exact plan and read it: how many items will be created, overwritten, used as they are or skipped.
- Select Apply Import. The Audit Log tab (
/admin/backups/audit) then records what was imported, by whom and when.
If something goes wrong
A part is missing. Preview will not run until every part is uploaded. If a link has expired, re-run the export.
The plan will not apply. A blocking warning stops the import and names what is wrong. Fix that and review the plan again.
An item is missing something it needs. Point it at the equivalent already on this installation, or export the missing piece too.
A scheduled task arrived switched off. Tasks that deliver through a connected account are restored disabled. Connect the channel, then turn the task on.
A Memory Space lost its knowledge source. Connections are matched, never recreated, and an unclear match is skipped and named in the plan. Reconnect it yourself.
Nothing seems to have changed. Items shown as used as they are were kept on purpose, because a match was already here.
An old archive asks for one project. Archives made before projects existed carry no project information, so the import asks where to put everything.
Where next
- Projects explains what a project groups, which is what a bundle follows.
- Stay in control sets out what is yours.
- Your installation describes the rest of the Admin area.