Audience: Faculty, staff, and other academic appointees who used Claude or ChatGPT before receiving a UChicago Claude Enterprise account.
Summary: This article explains what you can bring into your UChicago Claude Enterprise account from an existing AI account, and how.
You need a UChicago Claude Enterprise account before anything can move. If you have not been provisioned yet, request access through the UChicago MySailPoint portal at https://uchicago.identitynow.com and wait for your activation confirmation. None of the steps below work until you can sign in to the UChicago workspace at claude.ai with your CNetID and password.
One rule that applies everywhere: moving content into the Enterprise workspace is one-way. Once your chats and projects are in UChicago Claude Enterprise, they cannot be moved back to a personal account.
All paths beginning with a personal account rely on data exports. An export gives you a ZIP file containing your conversation text. It does not include attached files or images, does not preserve formatting such as tables and code blocks, and cannot be imported back into any Claude account. Treat an export as an archive for your records, not as a moving truck.
There is no automatic migration for these accounts. Anthropic does not support migrating a personal Claude account into an Enterprise account with HIPAA compliance as an option, such as the one UChicago offers. This applies to any account covered by the Enterprise agreement — whether it's the full version of Claude Enterprise or the HIPAA-compliant version.
Your UChicago Claude Enterprise identity is your CNetID@uchicago.edu, and Anthropic cannot merge an account under a different email address into it. This is a vendor limitation, not a university policy choice.
What we recommend instead:
The export contains your conversation text in a technical format (JSONL). It does not include attachments or formatting. Keep it as a record.
b. Keep the account as a free archive. You do not have to close the account. Downgrade to the Free plan (cancel any paid subscription) and keep it as a searchable, read-only reference for your old conversations. Important tip: do NOT delete your account if it is using your cnetid@uchicago.edu email address: doing so will deny you from claiming your UChicago Claude Enterprise account for 30 days.
c. Move active work by hand. For projects you are still working on, copy the important content — key documents, project instructions, reference files — into new Projects in your UChicago Enterprise account. This is a manual process, so prioritize what you will use.
d. Move your memory. Claude's learned context about you (preferences, working style, ongoing projects) can be transferred manually. In your old account, ask Claude to write out its memory of you; in your Enterprise account, use the memory import option to paste it in.
If your department or lab bought its own Claude Team plan, that organization is separate from UChicago Claude Enterprise and will not be absorbed automatically by any university process.
Do not use the "Upgrade an existing organization" option at claude.ai/upgrade. This converts your Team plan into a new, standalone Enterprise organization that is still not connected to UChicago's instance — and it creates a new billing commitment. It does not accomplish the consolidation.
Follow the consolidation process below.
Transparency note for owners and members: an organization export includes every member's conversations and projects, and the owner can read all of it. Owners should tell members this before exporting; members should know it before the export runs.
Your account and its content belong to the Team organization. When the owner cancels the plan, you lose access to everything in it. Before that happens:
There is no per-user migration from a Team org into UChicago Enterprise. Content moves by export and manual rebuild only.
Claude cannot import ChatGPT conversations. Two things are worth doing anyway:
a. Transfer your memory (recommended)
Claude has a built-in import for the context another AI has learned about you — your preferences, projects, and working style.
The import carries preferences and context, not conversations. It can take up to 24 hours to fully apply.
b. Export your ChatGPT history (for your records)
The ZIP contains your full conversation history (conversations.json and chat.html). You cannot import it into Claude, but you can upload individual conversations or extracts into a Claude Project as reference material when a specific piece of past work is relevant. Project file limits apply, so upload selectively.
If you are in a ChatGPT Team or Enterprise workspace: data export may be controlled by your workspace administrator. If the export option is missing, ask your admin.
c. Recreate custom GPTs
Custom GPT instructions are not included in any export or import. To recreate one in Claude, copy its instructions from the GPT editor and paste them into the Project instructions of a new Claude Project, along with any knowledge files the GPT used.
To switch between accounts by clicking your username, both accounts must use the same email address (e.g., CNetID@uchicago.edu). If your additional account uses a different email address, you will not be able to add it via this method.
To access multiple accounts simultaneously, please use one of the following options:
This approach allows you to work with more than one account at the same time, even if they use different email addresses.
After importing, check that your chats and projects appear in the UChicago workspace before assuming the transfer is complete.
Visit Claude's Support Center.