Migration

Move your team from Claude to Context

Your skills, project files, connectors and scheduled tasks move into one workspace your team shares, and Claude models stay available inside it.

Book a migration callCompare first

Skills

5 items New Skill
Brindle Capital FilterSort
  • Quarterly portfolio reviewBuild the quarterly review deck from the updates doc and the valuation bridge, flagged companies first. Restricted portfolio by Atlas Run
  • Covenant test rerunRerun every covenant test from the valuation bridge and list the tight ones. Brindle Capital covenants by Ledger Run
  • Board pack extractionPull the quarter's actuals from each company's board pack into the updates doc. Brindle Capital data room by Scout Run
  • LP letter draftDraft the quarterly LP letter from the review deck and the fund summary. Restricted investor relations by Maya Okafor Run
  • Data room sweepList every new file in the data room since the last review and who added it. Brindle Capital data room by Scout Run
Quarterly portfolio review
Quarterly portfolio reviewSavedv22/3 Improve RunSave
Quarterly portfolio review

Build the quarterly review deck from the updates doc and the valuation bridge, flagged companies first.

Scope
Restricted
Tags
portfolio
Files
SKILL.md deck-template.pptx Add files
Connectors
+ Attach
Scorecards
Deck quality

Steps

  1. Read the quarter's updates doc and the valuation bridge workbook.
  2. Draft the slides from last quarter's template, one company per slide.
  3. Place every company more than 10% off plan first, on slides 3 to 5.
  4. Render the deck and post it to the review channel with the flagged companies named.

Written by

Atlas · from the Q3 review deck task

Quarterly portfolio review
Quarterly portfolio reviewSavedv22/3 Improve RunSave
Quarterly portfolio review

Build the quarterly review deck from the updates doc and the valuation bridge, flagged companies first.

Scope
Restricted
Tags
portfolio
Files
SKILL.md deck-template.pptx Add files
Connectors
+ Attach
Scorecards
Deck quality

Steps

  1. Read the quarter's updates doc and the valuation bridge workbook.
  2. Draft the slides from last quarter's template, one company per slide.
  3. Place every company more than 10% off plan first, on slides 3 to 5.
  4. Render the deck and post it to the review channel with the flagged companies named.

Written by

Atlas · from the Q3 review deck task

Why teams move from Claude

Claude stays one of the models you run. What changes is where the work lives: in a workspace your whole team can open, version and score.

q3-portfolio-reviewThursday's review: updates, bridge, deck, covenant watch7
Messages FilesDetails
Today
Maya Okafor09:02

Review is Thursday. Priya, can you get the portfolio pack started? Same structure as Q2, and Northwind and Alder go in the risk section this time.

Priya Natarajan09:04

@Scout pull the Q3 updates for all 14 portfolio companies from the data room and flag anything more than 10% off plan.

Scout09:04
Q3 portfolio updates
Done in 6 min 12 s
Wrote q3-portfolio-updates.docx, 184 KB
q3-portfolio-updates.docxworkspaces/b/q3-portfolio-reviewDoc · 184 KB

Three companies moved more than 10% against plan: Northwind Logistics (revenue down 14%, one lost contract), Alder Health (up 18%, the payer contract started early) and Fenwick Tools (EBITDA down 11%, freight). Sources are linked in the doc.

2
Marco Vitale09:12

@Ledger rebuild the valuation bridge with the Q3 actuals and rerun the covenant tests for Northwind and Fenwick.

Ledger09:13
Q3 valuation bridge
Done in 4 min 40 s
Wrote q3-valuation-bridge.xlsx, 612 KB
q3-valuation-bridge.xlsxworkspaces/b/q3-portfolio-reviewSheet · 612 KB

Northwind passes leverage at 3.9x against a 4.5x covenant. Fenwick's interest cover is 2.1x with the test at 2.0x: passing, but tight. One tab per company in the workbook.

Maya Okafor09:20

@Atlas can we have the review deck from this, flagged companies up front?

Atlas09:21
Q3 portfolio review deck
Done in 3 min 48 s
Wrote q3-portfolio-review.pptx, 4.1 MB
q3-portfolio-review.pptxworkspaces/b/q3-portfolio-reviewDeck · 4.1 MB
3
Maya Okafor09:30

@Ledger keep the covenant headroom somewhere we can all watch it

Ledger09:31
Covenant headroom applet
Done in 2 min 05 s

Published Covenant headroom to the workspace. It reads the bridge workbook and refreshes whenever the workbook changes; it is open on the right.

Send a message in #q3-portfolio-review
q3-portfolio-review7
Messages FilesDetails
Today
Maya Okafor09:02

Review is Thursday. Priya, can you get the portfolio pack started? Same structure as Q2, and Northwind and Alder go in the risk section this time.

Priya Natarajan09:04

@Scout pull the Q3 updates for all 14 portfolio companies from the data room and flag anything more than 10% off plan.

Scout09:04
Q3 portfolio updates
Done in 6 min 12 s
Wrote q3-portfolio-updates.docx, 184 KB
q3-portfolio-updates.docxworkspaces/b/q3-portfolio-reviewDoc · 184 KB

Three companies moved more than 10% against plan: Northwind Logistics (revenue down 14%, one lost contract), Alder Health (up 18%, the payer contract started early) and Fenwick Tools (EBITDA down 11%, freight). Sources are linked in the doc.

2
Marco Vitale09:12

@Ledger rebuild the valuation bridge with the Q3 actuals and rerun the covenant tests for Northwind and Fenwick.

Ledger09:13
Q3 valuation bridge
Done in 4 min 40 s
Wrote q3-valuation-bridge.xlsx, 612 KB
q3-valuation-bridge.xlsxworkspaces/b/q3-portfolio-reviewSheet · 612 KB

Northwind passes leverage at 3.9x against a 4.5x covenant. Fenwick's interest cover is 2.1x with the test at 2.0x: passing, but tight. One tab per company in the workbook.

Maya Okafor09:20

@Atlas can we have the review deck from this, flagged companies up front?

Atlas09:21
Q3 portfolio review deck
Done in 3 min 48 s
Wrote q3-portfolio-review.pptx, 4.1 MB
q3-portfolio-review.pptxworkspaces/b/q3-portfolio-reviewDeck · 4.1 MB
3
Maya Okafor09:30

@Ledger keep the covenant headroom somewhere we can all watch it

Ledger09:31
Covenant headroom applet
Done in 2 min 05 s

Published Covenant headroom to the workspace. It reads the bridge workbook and refreshes whenever the workbook changes; it is open on the right.

Send a message in #q3-portfolio-review

What our team does for you

Context engineers run the move with the people who own each workflow. Your team keeps its current tool until the moved work passes on real tasks.

Home

Fri, Sep 11 72°
RecentPinnedTasks
  • q3-portfolio-review.pptx1h ago
  • q3-valuation-bridge.xlsx2h ago
  • q3-portfolio-updates.docx3h ago
  • lp-letter.pptx5h ago
Working on Q3 portfolio review deck

Home

Fri, Sep 11 72°
RecentPinnedTasks
  • q3-portfolio-review.pptx1h ago
  • q3-valuation-bridge.xlsx2h ago
  • q3-portfolio-updates.docx3h ago
  • lp-letter.pptx5h ago
Working on Q3 portfolio review deck

What moves, and how

Everything your team has in Claude, where it lands in Context, and who moves it.

Moves with a tool Context ships today

  • SkillsWorkspace skills, versionedClaude skills and Context skills are both folders with a SKILL.md and a name and description in its frontmatter, so the folder uploads as it is with context-cli skill create.
  • Knowledge filesDrive foldersUpload the source files as folders or zip archives; Drive keeps the folder tree and agents read from it.
  • Connectors and MCP serversConnectors from the catalog, or your own remote MCP serverCatalog connectors are switched on for your organization; a remote MCP server is registered once by an admin. Each person then authorizes their own account.
  • People and seatsWorkspace members from your identity providerSign-in moves to your IdP over SAML or OIDC, and SCIM 2.0 provisions and removes people, so nobody is invited by hand.

Rebuilt by our team, by hand

  • PluginsSkills, connectors and agentsA Cowork plugin bundles skills, connectors and sub-agents. The skills upload as above, the connectors are set up once, and the sub-agents are rebuilt as Context agents with your team.
  • Project instructionsAgent instructions or a skillInstructions are copied into the agent that will do the work, or into a skill when several agents need them.
  • Scheduled tasksAutomationsRebuilt from your list as automations (hourly, daily, weekdays or weekly) and left paused until the owner approves each one.

Before you start

Some things do not move. These are the ones to plan around.

What stays in Claude

  • Chat history stays in ClaudeContext does not import conversations. A Primary Owner can export the organization's conversation data from Claude; if you want it on hand, we keep the export as files in a Drive folder your agents can read.
  • Local Cowork sessions stay on each computerAnthropic's page says admins cannot centrally manage or delete local session data, so there is nothing central to collect. Work that matters is re-run in Context from the moved skills.
  • Claude models do not go anywhereClaude is one of the models in Context's catalog. Agents that work well on Claude today keep running on Claude after the move.

Bring to the first call

  • An organization data export, requested by your Claude Primary Owner, if you want past conversations kept as files.
  • The source folders or zips of your custom skills, and a list of the plugins each team uses.
  • The project knowledge files your teams rely on, or the Drive and SharePoint folders they came from.
  • A list of connectors and MCP servers in use, and who owns each one.
  • Your scheduled tasks: what each one does, when it runs and who reads the result.

Move into your own environment

Context runs in your own cloud or on your own hardware, so the skills, files and runs you move stay inside your deployment.

  • Files in your S3 or MinIO bucket
  • Self-hosted through KOTS
  • SAML and OIDC sign-in with SCIM
  • Air-gapped installation
How deployment works
  • Your cloud or hardwareFiles are stored in your S3 or MinIO bucket, in your cloud or on your own hardware.
  • Self-hosted through KOTSInstall Context in your own environment with KOTS self-hosting.
  • Air-gapped installationInstall without internet access, with the air-gapped installation tested in CI.
  • Your identity providerSign people in with SAML or OIDC and provision them with SCIM.

Context runs in production at Qualcomm. Read the case study

  • Amazon S3
  • MinIO
  • Your own hardware
  • Air-gapped

Questions

Can Context import our Claude skills directly?

Yes. Both products use a folder with a SKILL.md file whose frontmatter carries a name and description. context-cli skill create uploads the folder and its scripts, and every later change is a numbered version. We check each skill runs as expected before your team relies on it.

Do our Claude conversations come over?

No. Context has no conversation importer. Your Primary Owner can export the organization's conversation data from Claude's settings, and we can keep that export in a Drive folder so agents and people can refer to it.

Can we keep using Claude models?

Yes. Claude is a first-class model in Context alongside GPT, Gemini and open-weight models. Which endpoints you use depends on your deployment and is set during implementation.

Do people have to reconnect their tools?

Yes, once. An admin turns on catalog connectors or registers your MCP servers for the organization, and each person authorizes their own account so agents act with that person's access.

Can we run both during the move?

Yes, and we recommend it. Teams keep Claude while the moved skills run on real tasks in Context and are scored against rubrics your experts write. Seats switch when the results satisfy your owners.

Sources, last verified September 2026:

Compare first: Context vs Claude and Claude Cowork · Context Code vs Claude Code

Plan your move from Claude

Book a migration callCompare first

Moving from something else: ChatGPT · Claude Code, Codex or Cursor