> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/guides/pricing-changes-for-organizations-on-business-or-team-plans.md). # Pricing changes for organizations on Business or Team plans ### What’s changing We’re deprecating outdated Team and Business plans on **26 June 2025**. Organizations still using those plans on that date will be automatically switched to our new core and site plans, and will be able to view a new invoice in GitBook that includes the updated billing. Find out more about the new plans — and the new features they’ll unlock for your organization — below. ### Why are we making this change? We’re focussed on being the best tool for creating and maintaining incredible product documentation. And over the last few months, we’ve added a ton of new features that help you build unbeatable documentation — from new customization options and site sections, to upgraded insights and reusable content. To reflect this focus, we recently introduced site-based pricing plans alongside our core plans. That means organizations will now pay for each site they publish, depending on the features they need — bringing our pricing closer to our competitors’ offerings. ### How does it affect you? If your organization is on an outdated Team or Business plan, the plan will no longer be supported after **26 June 2025**. On that day, your plan will be switched over to new pricing automatically, using the following process: #### If you’re on a **Team** plan * We will convert all the members in your organization to our **Plus** plan. * We will convert your docs site with the highest traffic into a **Premium** site, which will be added to your bill. * All your other sites will be downgraded to Basic sites, which are free. * You can check your updated bill by visiting your GitBook organization after the deadline, choosing **Settings** > **Organization settings** and clicking the **Billing** option. #### If you’re on a **Business** plan: * We will convert all the members in your organization to our **Pro** plan. * We will convert your docs site with the highest traffic into an **Ultimate** site, which will be added to your bill. * All your other sites will be downgraded to Basic sites, which are free. * You can check your updated bill by visiting your GitBook organization after the deadline, choosing **Settings** > **Organization settings** and clicking the **Billing** option. {% hint style="info" %} If your site setup is very complex and has multiple sites with authenticated access or share links, our support team can help with your migration. [Get in touch](mailto:support@gitbook.com) and they’ll walk you through your options and help you find the right setup. {% endhint %} ### What is a docs site plan, and what are the differences between the plans? Previously, our Team and Business plans included unlimited publishing with certain docs site features and a minimum number of member seats for a single set price. Our new pricing uses a per-site pricing model, as well as a per-seat model for members. That means that if you’ve published multiple sites, you can choose a plan for each one with just the features you need. Our new plans also [include exclusive features](#what-extra-features-will-i-get-when-i-migrate), so upgrading will unlock more tools to make your documentation even better. And with an Ultimate site, you can combine the content of multiple sites into one using [site sections](/docs/manage-your-site/site-structure/site-sections.md). So a single docs site could hold your product docs, API reference, help center, guides and more — with global search across them all. There are three types of docs site plans, each offering different levels of features — and you can add as many users as you like too:
Site typePrice annually/monthlyFeatures
BasicFreeBasic customization, gitbook.io domain, basic user search
Premium$65/$79Everything in Basic, plus: advanced site customization, custom domain, site insights, PDF export, AI-powered answers
Ultimate$249/$299Everything in Premium, plus: site sections to centralize content in a single site, global search, authenticated user access
Add users$12/$15 eachAdd as many member seats to your organization as you need.
Still not totally clear on what this means for you? Our migration wizard will walk you through the whole process and show all your options for the members and sites in your organization — including specific plan and pricing information. [Head to the GitBook app](https://app.gitbook.com/) to start your migration. ### What extra features will I get when I migrate? If you’re on a Team plan, switching to our new plans will unlock the following features, depending on the docs site plan you choose: * [Site sections](/docs/manage-your-site/site-structure/site-sections.md) that let you combine multiple docs sites into a single centralized experience * [Advanced customization](/docs/manage-your-site/customization.md) options * [Site insights](/docs/analytics/insights.md) * [Site redirects](/docs/publish/site-redirects.md) * [AI-powered answers](/docs/create-content/searching-your-content/gitbook-ai.md#for-published-content) for readers If you’re on a Business plan, you already have some of these features. But switching to our new plans will unlock the following features, depending on the docs site plan you choose: * [Site sections](/docs/manage-your-site/site-structure/site-sections.md) that let you combine multiple docs sites into a single centralized experience and unlocks global search * [Improved site insights](/docs/analytics/insights.md) for Ask AI and OpenAPI usage * [Site redirects](/docs/publish/site-redirects.md) ### Can I complete the process early and control what happens to my members and sites? Absolutely — you have total control over what happens with your members and sites if you complete the process before **26 June 2025**. You can use our migration tool to switch over to our new plans and make choices about which members and docs site features you want to keep. [Head to the GitBook app](https://app.gitbook.com/) to get started — you’ll be guided through your options at each step. If you choose to do nothing, that’s fine — we’ll follow the automatic migration process we detailed above on the deadline date. ### Is there any discount for migrating before the deadline? Yes. We’re offering a discount if you switch over to the new pricing manually before the deadline date. * You’ll get **15% off** for **6 months** if you choose monthly billing * You’ll get **15% off** for **12 months** if you choose annual billing — on top of the existing annual saving. This discount will be applied automatically when you complete the migration, as long as it’s before **26 June 2025**. ### When will I get the first bill with the new plans? If you are billed monthly, the new pricing will begin on your next bill date. If you are billed annually, you will receive a new, prorated bill on the day you complete the migration — whether you do it manually, or it’s completed automatically on the deadline. You can check your updated bill by visiting your GitBook organization after the deadline, choosing **Settings** > **Organization settings** and clicking the **Billing** section. [Head to the GitBook app](https://app.gitbook.com/) to start your migration manually, and be guided through the process. ### I’ve just recently paid my monthly/annual bill for my existing plan. What happens if I migrate? Any payment you’ve made will be counted towards your new bill. For example, if you paid your $500 annual bill on 1 May, that amount will be counted towards any new bill when you migrate to new pricing. If your new bill is higher than $500, that amount will be deducted from your new bill. If your bill is less than $500, your bill will show credit on your account which you can use towards your next bill. ### How can I optimize pricing to reduce my bill? One great way to optimize your pricing is by [combining the content of multiple sites](/docs/manage-your-site/site-structure/site-sections.md) into a single Ultimate site using site sections. By doing this, you can build a single, centralized docs site with all your published content in one place — such as product docs, API reference, help center, guides, changelog and more. Combining multiple Premium sites into a single Ultimate site will work out cheaper than publishing them all separately. [Read the site section docs](/docs/manage-your-site/site-structure/site-sections.md), then [reach out to our support team](mailto:support@gitbook.com) who can help with the switch. And don’t forget — you don’t have to pay for every site you publish. Switching some of your sites to our free Basic site plan will reduce your overall costs. You have complete control over the plans you want to choose when you complete your switch early. ### Still have questions? If your question wasn’t answered here or you have more questions about these details, please [reach out to our support team](mailto:support@gitbook.com) — they’ll be happy to help. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://gitbook.com/docs/guides/pricing-changes-for-organizations-on-business-or-team-plans.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.