Claude Cowork migration guide
Switch from Claude Cowork in one prompt.
Bring your Cowork plugins and Claude skills to OpenWork, the open-source Claude Cowork alternative. Your agent moves them and tells you what is left.
Free and open source · Needs an owner or admin account to share plugins with your team
Follow https://openworklabs.com/migrate.md to move my Claude plugins and skills to OpenWork.
Your plugins and skills, ready on day one.
Cowork and Claude Code plugins
Plugins you added from a GitHub marketplace, such as Anthropic's knowledge-work-plugins, are imported into your OpenWork organization. Their skills work right away.
Claude skills you wrote
Your own SKILL.md skills become private OpenWork skills that only you can use until you share them.
Connectors and MCP servers
Slack, Notion, HubSpot and the other connectors a plugin suggests are added as optional. Each person connects the services they use.
Changes later
Run the same prompt again to pick up plugin updates and edits to your skills. Nothing is duplicated.
Stays behind: Conversation history and saved credentials; Plugins that are not in a public GitHub repository; Scheduled tasks, which you recreate and run once by hand.
Look first. Then move only what you use.
- 01
Finds what you use
Reads the marketplaces you added in Claude Cowork or Claude Code and the skills you wrote. Nothing leaves your computer yet.
openwork-bootstrap migrate scan - 02
Shows you the plan
Lists every plugin with its skills and connectors, and asks which ones you actually use.
openwork-bootstrap migrate plan - 03
Moves what you choose
Imports those plugins and your skills into OpenWork, then tells you what is left, such as connecting Gmail.
openwork-bootstrap migrate apply
No agent? Install the command with curl -fsSLo /tmp/openwork-install.sh https://openworklabs.com/install.sh, run it with sh, then openwork-bootstrap login and the three commands above.
Everything Cowork does. No lock-in.
Frequently asked questions
- Can I keep my Claude Cowork plugins in OpenWork?
- Yes. Plugins from public GitHub marketplaces, including Anthropic's knowledge-work-plugins for Cowork, import into your OpenWork organization with their skills. Paste the migration prompt into Claude Code or run openwork-bootstrap migrate.
- Do Claude skills (SKILL.md) work in OpenWork?
- Yes. OpenWork uses the same SKILL.md format as Claude Cowork and Claude Code. Skills you wrote in Cowork move as private skills; skills inside plugins move with their plugin.
- What happens to connectors like Slack, Gmail, and Google Calendar?
- Connectors a plugin suggests are added as optional, so skills work before anything is connected. Each person connects the services they use in OpenWork. Gmail and Google Calendar use OpenWork's Google Workspace connection.
- Can I keep using Claude models after switching from Cowork?
- Yes. Add an Anthropic API key, or let your organization provide Claude centrally. OpenWork also runs 50+ other providers and local models, so you are not locked into one vendor.
- What does not transfer from Claude Cowork?
- Conversation history, saved credentials, and scheduled tasks do not move. Plugins that are not in a public GitHub repository need to be added by hand.
- Can I run the migration again later?
- Yes. Running it again updates plugins and skills that changed and leaves everything else as it is, so nothing is duplicated.
Keep your work. Change your tools.
Move your Cowork plugins and skills today, and keep Cowork until your real work runs in OpenWork.