01
Open the same work
Install OpenWork, create a workspace from the folder or repository you used with Cowork, and ask the agent to summarize it before making changes.
Migration guide
Move from Claude Cowork without rebuilding your setup.
Start with one real task, bring over the capabilities it needs, and keep Cowork available until that task works end to end in OpenWork.
What carries over
Keep the work. Reconnect the access.
Files and folders
Open the same folder or repository as an OpenWork workspace.
SKILL.md skills
Copy the skill folder or install the plugin that contains it.
Claude-compatible plugins
Import the manifest; OpenWork normalizes its skills and MCP dependencies.
MCP servers
Reconnect through OpenWork Connect or add the server URL as a custom app.
Claude models
Add an Anthropic API key or provision Anthropic through OpenWork Cloud.
Scheduled tasks
Recreate each schedule, then verify its workspace, permissions, and output.
Conversation history and credentials do not transfer automatically. Save important instructions in workspace files or skills, then authorize each connected service in OpenWork.
Migration path
One workflow at a time.
02
Choose your models
Keep Claude with an Anthropic API key, add another provider, or let your organization provision models centrally. Your Claude subscription and Anthropic API billing may be separate.
03
Bring over skills and plugins
OpenWork uses the same SKILL.md format. Import one skill at a time, check its paths and environment variables, then run the smallest task that should trigger it.
04
Reconnect apps and MCP servers
Reauthorize every service. Test read-only actions first, then test write actions with a disposable example.
05
Recreate schedules and browser tasks
Record each prompt, schedule, time zone, workspace, connection, and output location. Run it manually once before enabling recurrence.
06
Roll it out without configuration drift
Use OpenWork Cloud to publish approved capabilities once, assign them by team, and apply desktop policies centrally instead of repeating setup on every machine.
Useful guides
Configure each piece.
Cutover checklist
The same workspace opens and the agent can read the expected files.
At least one model is connected and its billing is understood.
Each required skill triggers on a representative task.
Each connector or MCP server is authorized and tested.
Scheduled and browser tasks have been run manually once.
Important Cowork instructions are saved in files or skills.
Make OpenWork the default only after the real workflow passes.
Keep Cowork available during validation. Once the checklist passes, switch that workflow and migrate the next one.
Download OpenWork