When upgrading from a Team plan to an Enterprise plan, we recommend you keep the same Team organization and follow the upgrade path to change it to Enterprise. This way your data (memberships/roles, conversations and projects) and settings will be preserved. If a you create a brand new Enterprise organization, then you'll need to set up everything from scratch.
What's retained (same organization upgrade)
All chat history and conversations
Projects and shared content
User memberships and roles
Migrate from Team to Enterprise
You can migrate from a Team plan to a self-serve Enterprise plan by following these steps:
Navigate to claude.ai/upgrade and click "Get Enterprise plan."
When prompted, choose "Upgrade an existing organization" and select your Team plan organization.
Add the number of seats needed for all your team members (Enterprise organizations have a 20 seat minimum).
Set a per-user spend limit and a starting usage balance for the whole team.
Your payment information will be saved from previous Team plan payments, but you can click the pencil icon to change it if needed.
We only support credit card payments for self-serve Enterprise plans. For more information, see Self-serve vs. sales-assisted Enterprise.
Review your order summary and click "Confirm upgrade."
Important: Migrating an organization from Team to Enterprise via this pathway is not reversible; please ensure that an Enterprise plan is the right fit for your organization before initiating this change.
After upgrading to an Enterprise plan, we recommend reviewing your organization's settings to confirm all desired features and capabilities are enabled. Some features that are turned on by default on Team plans may be turned off by default on Enterprise plans, so it's worth checking that your configuration matches your preferences.
Seat assignment
During migration, some users may appear as "Unassigned" rather than being automatically mapped to seat tiers. Admins should verify all users have correct seat assignments after the cutover.
For detailed guidance, refer to Purchasing and managing seats on Enterprise plans.
SSO and identity setup timeline
Domain verification (DNS): Allow 24–48 hours for DNS changes to propagate globally, though many changes take effect within 10 minutes.
SCIM provisioning sync: Microsoft Entra ID pushes changes approximately every 40 minutes. Okta syncs more frequently.
For detailed setup instructions, refer to Setting up single sign-on (SSO) and Setting up JIT or SCIM provisioning.
Note: Once you turn on SSO, existing users will be forced to log out and log back in.
Billing and usage configuration
For usage-based Enterprise plans, usage is billed based on actual consumption. For more detailed information, refer to How am I billed for my Enterprise plan?
If you had purchased extra usage for your Team plan, any unused credits will roll over and become available on your new usage-based Enterprise plan.
Provisioning process
On the start date, you'll be provisioned and able to use the new features by the end of the day. After initial setup, Owners and Primary Owners can self-serve additional seats by navigating to Organization settings > Organization and clicking "Manage" under Total seats.