At a Glance

Sloan Fellows students moving from the MIT Sloan Fellows Pilot Team Claude workspace to the Massachusetts Institute of Technology Enterprise workspace will need to manually preserve and recreate any Claude content they want to continue using.

The two workspaces are separate. Your existing chats, Projects, instructions, files, memory, Skills, code, artifacts, and connected apps will not automatically move to MIT Enterprise.

The Sloan Fellows workspace will be decommissioned after Sunday, October 4, 2026, and access will end. Complete the steps in this guide before then, and confirm that anything important to you has been saved or recreated in MIT Enterprise.

IMPORTANT: Nothing moves automatically, and there is no way to merge the two workspaces. MIT Enterprise starts out empty—whatever you want there, you will need to save and add yourself. Claude-generated handoffs can help you carry context forward, but they do not contain your files and should not be treated as a complete backup.

DISCLAIMER: This guide is provided as general guidance to help you preserve and recreate your Claude work when moving between workspaces. Claude features, interfaces, and available migration options may change, and the steps described here may not capture every type of content or configuration in your account.

You are responsible for identifying and saving the information, files, and other content you want to retain and for confirming that your saved copies are complete and accessible before your Sloan Fellows workspace access ends. MIT Sloan Technology Services cannot guarantee that all content can be preserved, transferred, recreated, or recovered after access to the original workspace ends.

Before You Start

If you have not signed in to MIT Enterprise yet, sign in with your MIT email address and choose Continue with SSO. You can do this at claude.ai or in the Claude desktop app—either way, it is the same account, and both workspaces will be available once you are signed in.

Once you have signed in, both workspaces will be available under the same email:

  • MIT Sloan Fellows Pilot Team
  • Massachusetts Institute of Technology Enterprise

Switch between them by clicking your initials or name in the lower left corner and selecting the workspace you want. A checkmark shows which one you are currently using.

Complete this process while you still have access to the Sloan Fellows workspace.

You do not need to save everything you have ever done in Claude. Focus on information, files, instructions, and work that you expect to use again or that would be difficult to recreate.

Start using MIT Enterprise for all new work right away. There is no reason to wait until October 4, and anything new you create in Sloan Fellows between now and then is one more thing to move.

While you are working through these steps, do not delete chats, Projects, Skills, or artifacts in the Sloan Fellows workspace, even if you think you have already saved them. Wait until you have confirmed everything you need is available in MIT Enterprise.

1. Save Your Settings and Instructions

System Instructions

If you have added standing instructions that tell Claude how you prefer it to work with you:

  1. Open Settings > Account in the Sloan Fellows workspace.
  2. Find Instructions for Claude under Profile.
  3. Copy the text into a document or text file, and save it as Sloan_Fellows_Claude_System_Instructions.md.

These may include writing preferences, terminology, formatting preferences, recurring instructions, or other information you regularly want Claude to consider.

Your instructions may or may not appear automatically in MIT Enterprise. Check after you switch. Either way, keep your own copy: this is a single text field with no version history, so if it is cleared or overwritten there is no way to recover it. Paste your saved text back in if anything is missing.

Skills

Skills do not move between Claude workspaces automatically. You can, however, download each Skill you created and upload it again in MIT Enterprise.

For each Skill you created:

  1. Open Settings > Skills in the Sloan Fellows workspace.
  2. Click on the name of the Skill you want to keep.
  3. Click the ⋮ menu in the upper right, and click Download.
  4. Save the downloaded file somewhere outside Claude.
  5. Repeat these steps for each Skill you want to bring with you.

In MIT Enterprise, add your downloaded Skills again using the Add button under Settings > Skills.

Connected Apps and Connectors

Connections to external apps and services do not carry over to MIT Enterprise. You will need to reconnect and sign in again there.

Before leaving the Sloan Fellows workspace:

  1. Open Settings > Connectors and look at the Connectors list.
  2. Take a screenshot or make a note of which ones you have connected. The list shows each connector’s name, type, and status.

The apps and connectors available in MIT Enterprise may differ from those in the Sloan Fellows workspace. If something you rely on is missing there, contact the STS Help Desk at stshelp@mit.edu.

Code and Claude Code

Code you wrote with Claude can live in several places: inside conversations, inside artifacts, in Claude-created files, in Project knowledge, and in folders on your computer. Handle it deliberately.

Put any codebase you want to keep working on into a Git repository before you switch. Commit and push it to GitHub. A repository gives you a clean handoff: the code, its history, and its documentation all travel with you and do not depend on either Claude workspace. GitHub is available at MIT (https://github.mit.edu) and Github directly (https://github.com/education/students).

Do not commit secrets, API keys, .env files, credentials, or course or research data that should not be in a repository. Add a .gitignore before your first commit.

Copy code out of chats and artifacts. A snippet that exists only in a Sloan Fellows conversation goes away with the workspace. Move it into a file in your repository, or into a folder you back up.

If you use Claude Code in your terminal or IDE:

  • Your repositories, CLAUDE.md files, .claude/ directories (custom commands, agents, and Skills), and local settings are stored on your computer, not in the Claude workspace. They stay where they are.
  • Your CLI session transcripts are also local, under ~/.claude/projects/. Sessions in Claude Code on the web and in the desktop app’s Code tab are tied to your workspace, so save anything from those you need.
  • Commit and push your work before you switch, so nothing important depends on a session you may not be able to resume.
  • After you switch, type /logout at the Claude Code prompt, then /login, and sign in again. When asked which organization to use, choose Massachusetts Institute of Technology Enterprise.
  • Settings your administrator manages are configured per organization, so permissions, available models, and similar settings may differ in MIT Enterprise.
  • Confirm Claude Code is available to you there before you rely on it.
  • Reconnect any MCP servers you configured for Claude Code and sign in to them again.

2. Save Your Claude Memory

Claude’s memory is separate in each workspace. What Claude remembers about you in Sloan Fellows will not appear in MIT Enterprise, and the reverse is also true.

To save a copy of what Claude remembers in Sloan Fellows:

  1. Open Settings > Memory and review what is listed under Preferences, Profile, Topics, and Areas. Keep this open (or note it down) so you can confirm later that nothing was dropped.
  2. Open a new chat in the MIT Sloan Fellows workspace—not inside a Project—and paste the memory export prompt below.
  3. Claude will give you two copies of the same thing: a file to download and a code block you can copy. Download Sloan_Fellows_Claude_Memory.md and save it somewhere you can find it—you will need it when you set up MIT Enterprise in Step 7. If no file appears, copy the code block into a text file and save it under that name yourself.
  4. Review the file and make sure any important context you want to preserve is included. Compare it against the Memory panel in Settings, which is the authoritative record.

Memory export prompt

I’m moving from a Claude Team workspace to a separate Claude Enterprise workspace and need to export my memory. List every memory you have stored about me, as well as any context you’ve learned about me from past conversations. Output everything in a single code block so I can easily copy it. Also create a Markdown (.md) file named Sloan_Fellows_Claude_Memory.md containing the same complete memory so I can save it as a backup. If you cannot create a file, the code block on its own is fine. Format each entry as: [date saved, if available]—memory content. Make sure to cover all of the following—preserve my words verbatim where possible: Instructions I’ve given you about how to respond (tone, format, style, ‘always do X’, ‘never do Y’). Personal details: name, location, job, family, interests. Projects, goals, and recurring topics. Tools, languages, and frameworks I use. Preferences and corrections I’ve made to your behavior. Any other stored context not covered above. Do not summarize, group, or omit any entries. After the code block, confirm whether that is the complete set or if any remain.

This export includes your account-level memory and the separate memory kept for each Project. It does not include your chat transcripts, which are a separate history and are covered by the handoffs later in this guide.

Do not reset memory at any point during this process. Resetting deletes your Project memories along with everything else.

3. Review Your Important Chats

Chat History

Your Sloan Fellows chat history will not appear in MIT Enterprise.

You do not need to save every conversation. Focus on chats containing information you will need again, such as:

  • Research or analysis
  • Important decisions
  • Drafts you are still developing
  • Reusable prompts
  • Useful workflows
  • Code
  • Planning
  • Information that would be difficult to recreate

You can save important content manually or use the handoff process later in this guide to summarize it.

If you are not sure which conversations matter, ask Claude to help you review them. Open a new chat in the MIT Sloan Fellows workspace—not inside a Project, since a chat started in a Project can only search that Project—and paste the prompt below.

Chat review prompt

Search my past chats and list the ones most worth carrying forward: long or detailed exchanges, chats where I worked something out or reached a decision, drafts I was still developing, and prompts or approaches I would use again.

For each one, give me the topic, roughly when it happened, one line on why it might be worth saving, and a label for what I would need to do with it:

  • Prompt or approach worth keeping to reuse
  • Draft or analysis worth copying out before it is gone
  • Decision or conclusion worth writing down in a few lines
  • Unsure

One line each, not summaries. Keep the list short enough for me to review in one sitting. Tell me which chats you could not search.

This search covers your conversations outside of Projects only. Treat the result as a starting point and check your chat history yourself for anything it missed.

Note that incognito chats were never saved to your history and cannot be recovered or summarized.

4. Save Your Projects

Projects do not move to MIT Enterprise. You will recreate each one and add its content again in the new workspace.

For each Project you want to continue, save these yourself:

  • Project knowledge and source files
  • Claude-created files you want to keep
  • A note of any Skills or connectors the Project uses, so you can set them up again

Work from your own originals for anything used as Project knowledge, such as documents, PDFs, spreadsheets, presentations, notes, images, or data. Do not count on being able to download these back out of a Project later.

Check all tabs on your Projects page (Your projects, Organization, and Shared with you) plus archived projects, so you don’t miss anything. Projects that someone else shared with you belong to their creator and are not yours to recreate.

A general handoff cannot reach the conversations inside your Projects. Those can only be searched from inside the Project itself.

For each Project you want to continue, open that Project in the Sloan Fellows workspace, start a new conversation inside the Project, and paste the prompt below.

Project handoff prompt

I am transitioning from this Sloan Fellows Claude Team workspace to a separate MIT Enterprise workspace. Create a handoff for this Project so I can recreate it and continue the work in the new workspace. Use the information available within this Project, including its conversations and knowledge. Output the entire handoff in a single code block so I can copy it in one action. Also create a Markdown (.md) file containing the same handoff so I can save it as a backup. Name the file Sloan_Fellows_Project_[project name].md, using this Project’s actual name.

Capture:

  • What this Project is for
  • Its current status
  • Important decisions and context, with dates where the Project shows them
  • Unfinished work and next steps
  • Recurring workflows or processes
  • Working preferences and conventions for this Project, quoting my exact wording for any standing rule I have given you, such as always do X or never do Y
  • Reusable prompts, templates, or approaches, reproduced in full rather than described
  • Important files, source materials, links, or references, with exact filenames and complete URLs
  • Anything else I would need to recreate the Project

Create a separate section called Move or Recreate Manually. Begin that section by reproducing the Project instructions exactly as written, with no edits, summarizing, or improvements. If you cannot access them, say so rather than reconstructing them. Then identify knowledge files, generated files, Skills, connectors, or other items I should preserve separately.

Create another section called Outside What I Can See and identify anything that may require my review.

Do not invent missing information or make assumptions about information you cannot access.

Do not modify or delete anything in this Project.

This is a handoff, not a complete backup of the Project.

After the code block, tell me whether this is everything you could find in this Project or whether anything remains, and name anything you were unable to reach.

Claude can search the conversations inside this Project, but context does not carry between Project chats automatically. Read the handoff and add anything important it missed.

Review and save each Project handoff outside Claude. Include the Project name in the filename, such as Sloan_Fellows_Project_Thesis_Handoff.md, so you can tell them apart later.

5. Download Your Files and Artifacts

Artifacts

Artifacts created in Claude are associated with your Claude workspace. They are not automatically saved as files on your laptop.

You can find everything you have made in the Artifacts section of the sidebar.

For each artifact you want to keep:

  1. Open the artifact.
  2. Use the controls in the lower right corner to download the file or copy the content and underlying code.
  3. Save it somewhere outside Claude that you regularly use and back up.

Slide decks can be exported to PowerPoint or PDF. Individual files are limited to 30 MB.

Do not assume an artifact will be available in MIT Enterprise simply because it is available in the Sloan Fellows workspace.

Artifacts You Shared with Others

Pay particular attention to artifacts you shared with other people.

In the Sloan Fellows workspace, artifacts are shared inside the organization. The people you shared with must be signed in to the Sloan Fellows workspace to open them. When you lose access to that workspace, those links will stop working for you, and your colleagues will lose access as well when their own access ends.

Before you leave:

  • Save your own copy of anything you shared.
  • Make a note of who you shared each item with, so you can reshare from MIT Enterprise if needed.
  • Let collaborators know the link will stop working, and send them a copy if they need one.

If an artifact stores information that people enter into it, such as a tracker or a form, save that content separately. It is not included when you download the artifact.

Files Claude Made in a Conversation

Some files Claude creates appear as a download in the conversation rather than in the Artifacts section—spreadsheets and PDFs most often. There is no single place to find these later, so you need to download them from the conversation itself.

Download them before you lose access to the Sloan Fellows workspace. Once it is gone, you cannot reopen the conversation to retrieve them.

Cowork and Local Files

In the Sloan Fellows workspace, Cowork runs on your computer rather than in the cloud. That means your Cowork sessions, their history, and the files they produced are stored locally and stay on your machine when you lose access to the workspace.

You still need to confirm a few things:

  • Check that you can find the outputs you care about, and that they are in a folder you will keep using.
  • If Claude created or edited files directly in a folder on your computer, those files are already local. You do not need to duplicate everything Claude has touched, but confirm the important ones are somewhere you back up.
  • Cowork settings differ between workspaces, so Cowork may behave differently in MIT Enterprise. Check Settings > Cowork after you switch.

Do not try to copy Claude’s application or system folders as a migration method. Preserve the actual documents and outputs you want to keep.

6. Create a General Handoff Document

After saving the content above, ask Claude to create a handoff document summarizing useful context from your Sloan Fellows workspace.

A handoff can help you continue your work, but it is not a complete backup or migration.

From the MIT Sloan Fellows workspace, start a New Chat—not inside a Project, since a chat started in a Project can only search that Project— and paste the prompt below.

General handoff prompt

I am transitioning from this Sloan Fellows Claude Team workspace to a separate MIT Enterprise workspace. Create a handoff document containing the useful information you can access that will help me continue my work in the new workspace. Output the entire handoff in a single code block so I can copy it in one action. Also create a Markdown (.md) file named Sloan_Fellows_Claude_Handoff.md containing the same handoff so I can save it as a backup.

Do not rely only on your current memory or this conversation. Search my past chats for relevant information. Note that this search covers my conversations outside of Projects only—it cannot reach conversations inside a Project.

Capture, when available:

  • My ongoing projects and work, including their current status
  • Important decisions, conclusions, and context
  • Open questions, unfinished work, next steps, and commitments
  • Recurring workflows and processes I use
  • Reusable prompts, templates, formats, or approaches I regularly use
  • My preferences and standing instructions for how Claude should work with me
  • Important terminology, conventions, or definitions I use
  • References, links, tools, or external services I mention relying on
  • Anything I describe as a file, Skill, or connector I depend on, so I can check it myself

For each major project or area of work, include:

  • Purpose
  • Current state
  • Important context and decisions
  • Instructions or preferences specific to that work
  • Key resources or files
  • Unfinished work and next steps

Create a separate section called Items I Need to Move or Recreate Manually listing anything you can identify that will not be preserved just by saving this handoff.

Create another section called Outside What I Can See. Explain plainly which parts of my workspace you have no access to from this conversation—for example, my Projects and their contents, my Skills, my connected apps, my account settings, and my files—so I know to check those myself.

Do not invent, infer, or fill in missing information. Clearly distinguish confirmed information from anything that is uncertain.

Do not modify or delete anything in my current workspace.

This handoff is not intended to be a complete backup or migration. Tell me what I should review separately before I lose access to this workspace.

Review the handoff carefully and save it outside Claude.

Claude can only report what it finds in the conversations it searched. It cannot see your Projects, Skills, connected apps, settings, or files, and it cannot confirm that its summary is complete. Use the checklist in Step 8 as your record of what to preserve.

7. Recreate Your Work in MIT Enterprise

After you have preserved the information you need:

  1. Click your initials or name in the lower left corner.
  2. Select Massachusetts Institute of Technology Enterprise.
  3. Confirm that MIT Enterprise is active.
  4. Check Settings > Account and add any standing Instructions for Claude that are missing.
  5. Import your saved memory at Settings > Memory > Start import. Open your saved memory file, copy its contents, and paste them into the box. Review the result afterward.
  6. Recreate the Projects you still need.
  7. Add your saved Project instructions and knowledge files.
  8. Upload your Skills at Settings > Skills.
  9. Reconnect the apps and connectors you use at Settings > Connectors.
  10. Upload your handoff documents or use them as context when continuing your work.

For your general handoff:

  1. Start a New Chat in MIT Enterprise.
  2. Select the + or attachment option in the message box.
  3. Choose your saved handoff file.
  4. Wait for the file to appear as an attachment before sending.
  5. Paste the prompt below and send.

Handoff review prompt

Use the attached handoff document as context to help me continue my work from my previous Claude Team workspace.

Summarize the information available in the handoff and identify any original files, instructions, or other information I still need to provide.

Do not invent information that is not in the handoff document.

For an individual Project, recreate the Project first, restore its instructions and source files, and then provide the Project-specific handoff.

8. Migration Checklist

Before you finish, confirm that you have preserved or recreated anything important:

  • Instructions for Claude
  • Skills you created, including any original files you want to preserve
  • Connected apps and custom connectors
  • Code committed and pushed to a repository
  • Claude Code configuration and local session files
  • Claude Memory backup
  • Important chats, prompts, decisions, or workflows
  • Project instructions
  • Project knowledge and original source files
  • Handoffs for important Projects
  • Important chat artifacts
  • Artifacts you shared with other people, and a note of who you shared them with
  • Claude-created files
  • Cowork outputs on your computer
  • General Claude handoff
  • Anything else that would be difficult to recreate

Keep your saved copies until you have confirmed that you can successfully continue your work in MIT Enterprise.

Do this before October 4, 2026. After that date the Sloan Fellows workspace is decommissioned and its contents cannot be retrieved.

Important to Know

This process does not migrate or merge your Sloan Fellows Claude workspace with MIT Enterprise.

The two environments remain separate.

The purpose of these steps is to help you preserve the information and work you need and manually re-establish it in MIT Enterprise.

A Claude-generated handoff should not be treated as a complete backup of your account. Important files, instructions, Skills, Project content, artifacts, memory, and other information you want to retain should be preserved separately.

Do not delete anything in the Sloan Fellows workspace until you have confirmed your work is available in MIT Enterprise.

You do not need to do anything to close or leave the Sloan Fellows workspace. Your access ends on its own. In particular, do not use Close your personal account in Settings—that affects a different account and is not part of this process.

If Something Does Not Work

If a step does not work as described, or you cannot find or save something you need, stop and contact the Sloan Technology Services Help Desk at stshelp@mit.edu before you lose access to the Sloan Fellows workspace.