Migrate a scheduled Claude Cowork workflow
Enter the expected run IDs and the receipts produced by the old and new schedulers. Find missed or duplicate executions.
Capture everything the workflow needs to run
Choose a Cowork workflow whose inputs and expected outputs you can write down. Save its prompt, folder scope, approved connectors, output format, and expected handling of missing data. Capture representative inputs and reviewed outputs as test fixtures. Anthropic describes Skills as reusable filesystem-based resources, so inspect each skill you intend to reuse for file paths, dependencies, and tool permissions. Test those dependencies in the hosted environment with the same narrow data scope you plan to use in production.
In an illustrative pilot, the input is a folder of 12 synthetic support tickets, the output is a digest grouped by priority, and four tickets are labeled urgent in the expected result. Pass the run only if all four urgent IDs appear exactly once and the digest stays in the review destination. Keep machine-bound tasks in Cowork while you validate their dependencies separately.
Choose a cutover occurrence and record which scheduler owns each occurrence on either side. The ability to launch both environments does not prove that ownership transferred.
Agent Skills - Claude Platform DocsTransfer one schedule and keep a recovery path
Record the last accepted run ID, then pause that specific Cowork schedule before enabling its hosted replacement. Use the workflow name and scheduled interval as a record of which runs have already been delivered. Keep the old configuration available and check the first hosted run at its due time. If the hosted run misses the deadline or produces a duplicate, pause it, reconcile any output already sent, and resume Cowork from the first undelivered run.
If the workflow relies on conversational continuity, test that dependency separately. The Claude Agent SDK's SessionStore adapter can mirror SDK transcripts for resumption by another host with a matching working directory. For the Cowork migration, seed the hosted workflow with reviewed inputs, decisions, and checkpoints, then check that it can complete its first run from those materials alone.
Rehearse with a synthetic action that creates a harmless unique receipt. Verify that stopping the old schedule and enabling the new one yields exactly one receipt for each due run.
Persist sessions to external storage - Claude Code Docs