Move to a new server

Your jobs live in your repos, so moving to a new server, in another Railway project or workspace, takes a few minutes.

1. Deploy the template again. See Deploy.

2. Connect Claude and GitHub on the new server’s /setup page, and add the same repos in step 3.

3. Restore your jobs: open a chat in CloudCLI. Claude sees the recorded jobs and offers to recreate them. It shows the list first, and creates them once you agree. See Restore on a new server.

4. Add the secrets the restore lists, on the Runner’s Harness / Runtime page in the new Paperclip, under Environment variables. See Secrets.

5. Connect Codex on /setup first if some jobs were recorded for it. See Codex.

6. Reconnect outside services you set up in Paperclip: apps, connections and plugins. They are not in git.

7. Test a job or two: “run the digest now and show me the log”.

8. Retire the old server: remove its project in Railway once the new one runs your jobs.

Don't run both

While both servers run, each runs your jobs, so every job runs twice. Don’t pause or archive the jobs on the old server through Claude either: those changes are written to the record in your repo, which the new server uses too.

What moves, and what doesn’t

Moves with your repos	Stays on the old server
Jobs: title, prompt, schedule, time zone, status, agent	Run history: tasks, transcripts, tokens
Skills	Secret values
Secret names	Apps, connections, plugins
Shared memory, once committed	CloudCLI chats

If you need the run history, keep the old project’s backups before you remove it. See Your data and backups.