Migration

Move your team from ChatGPT to Context

Custom GPTs become skills and agents your whole workspace can use, project files move into Drive, and GPT models stay available inside Context.

Book a migration callCompare first
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.

@Atlas can we have the review deck from this, flagged companies up front?
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.

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

Why teams move from ChatGPT

A custom GPT answers one person at a time. In Context the same instructions become a skill, the agent joins your channels, and its writes wait for a person.

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

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 ChatGPT, where it lands in Context, and who moves it.

Moves with a tool Context ships today

  • Custom GPT knowledge filesThe skill's reference files, or a Drive folderFiles a GPT always needs travel inside the skill folder; larger libraries go into a Drive folder the agent reads from.
  • Project filesDrive foldersUpload the source files as folders or zip archives; Drive keeps the folder tree and agents read from it.
  • Apps and connectorsConnectors 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

  • Custom GPT instructionsA skill, versionedEach GPT's instructions are written into a SKILL.md with a name and a description of when to use it, then uploaded with context-cli skill create.
  • Custom GPT actionsA catalog connector, or your own MCP serverAn action is an OpenAPI schema plus authentication. Where a catalog connector covers the same system we use it; otherwise the API is exposed as a remote MCP server and registered as a connector.
  • 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 ChatGPT

  • Chat history stays in ChatGPTContext does not import conversations. OpenAI's help center says self-service export is not available in Business or Enterprise workspaces and points Enterprise owners to organization-managed data access. If your owner exports records, we keep them as files in a Drive folder.
  • GPT models do not go anywhereGPT models are in Context's catalog. Work that runs well on GPT today can keep running on it, and you can compare it with other models on the same task.

Bring to the first call

  • The list of custom GPTs your teams use, with the owner of each one.
  • Each GPT's instructions, knowledge files and any actions, with the API each action calls.
  • The project files your teams rely on, or the folders they came from.
  • A list of connected apps in use.
  • 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

What happens to our custom GPTs?

OpenAI's help center says custom GPTs are scheduled to retire on December 11, 2026, with a path to migrate them to plugins. Moving them to Context instead, each GPT's instructions become a skill, its files become the skill's references or a Drive folder, and its actions become connectors. Our team does this by hand with the GPT's owner.

Do our ChatGPT conversations come over?

No. Context has no conversation importer, and OpenAI says self-service export is not available in Business or Enterprise workspaces. If your workspace owner exports records through OpenAI, we can keep them in a Drive folder.

Can we keep using OpenAI models?

Yes. GPT models are part of Context's model catalog alongside Claude, Gemini and open-weight models. Which endpoints you use depends on your deployment and is set during implementation.

Can we run both during the move?

Yes. Teams keep ChatGPT 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 ChatGPT Enterprise

Plan your move from ChatGPT

Book a migration callCompare first

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