# The Sanity Hub: what to know before you choose, migrate to or scale Sanity Reviewed by Martin Dejnicki · facts verified 25 October 2026 · canonical: https://deploi.ca/sanity ## Short answer The Sanity Hub is Deploi's guide to choosing, migrating to and scaling Sanity, a hosted content platform. Each page answers one question about Sanity, with a dated source for every fact, so you can verify each answer. Deploi, a Toronto-based web development agency, runs four deploi.ca sections on Sanity: 4,642 documents, counted 24 October 2026. - **Deploi's Sanity footprint:** 4,642 documents in two datasets. Deploi's own read-only count on 24 October 2026: 3,773 and 869 documents in two datasets, image assets included, across deploi.ca's Shopify FAQ, Build vs. Buy, Builds and Data sections in one Sanity project. ([Deploi, Build vs. Buy on Shopify](https://deploi.ca/shopify/build-vs-buy); [Deploi, Shopify data and statistics, every source shown](https://deploi.ca/shopify/data); [Deploi, Shopify FAQ for Mid-Market and Enterprise Brands](https://deploi.ca/shopify/faq); [Deploi, Shopify Builds](https://deploi.ca/shopify/builds)) - **Sanity's entry price:** $0 on Free, $15 per seat a month on Growth. Growth is billed monthly in US dollars and Enterprise is custom pricing, per Sanity's pricing page as of October 2026. ([Sanity, Plans that scale with you](https://www.sanity.io/pricing); [Sanity, Sanity for Startups](https://www.sanity.io/startups)) - **Public template:** FAQ Hub with AI Chatbot. Published by Martin Dejnicki on Sanity Exchange and listed as built by Deploi: a Sanity FAQ model with AI search and a chatbot, on Next.js. ([Sanity Exchange, FAQ Hub with AI Chatbot template](https://www.sanity.io/templates/faq-hub-with-ai-chatbot)) ## Where should you start on the Sanity Hub? Start with the decision in front of you, because each page on the Sanity Hub answers one question about Sanity, the hosted content platform, and links to the next one. Seven starting points cover most readers: - **Deciding whether Sanity fits:** read [our overall review of Sanity](https://deploi.ca/sanity/review), which scores it on 10 criteria, or [what Sanity is and who it suits](https://deploi.ca/sanity/faq/what-is-sanity) if the product is new to you. - **Starting without paying:** read [whether Sanity's Free plan is enough to launch on](https://deploi.ca/sanity/faq/is-sanity-free). - **Facing an end-of-support date:** start with [the content management system (CMS) end-of-life calendar](https://deploi.ca/sanity/migration/leaving-a-legacy-cms/cms-end-of-life-calendar), which says what each date forces. - **Moving to Sanity:** start with [the plan for a CMS migration to Sanity, from content audit to cutover](https://deploi.ca/sanity/migration/cms-to-sanity). - **Choosing between products:** start with [the alternatives to Sanity and when each one wins](https://deploi.ca/sanity/compare/sanity-alternatives). - **Already running Sanity:** start with [how Sanity and Next.js work together](https://deploi.ca/sanity/integrations/nextjs), or a feature review such as [Content Releases](https://deploi.ca/sanity/features/content-releases). - **Budgeting or hiring:** start with [what a Sanity build costs](https://deploi.ca/sanity/cost), [how to choose a Sanity development agency](https://deploi.ca/sanity/agency/how-to-choose) or [what Deploi builds and fixes on Sanity](https://deploi.ca/sanity/agency). Short questions have their own index: [the Sanity FAQ](https://deploi.ca/sanity/faq) says which ones a short answer settles. ## Which replatform decision covers the CMS you run today? Twelve replatform decision pages are in this first release as of October 2026, each for a content management system (CMS) whose deadline, owner or fit is forcing a choice: upgrade it, move to Sanity, move elsewhere or wait. - **Drupal 10:** [upgrade to Drupal 11 or replatform to Sanity](https://deploi.ca/sanity/migration/leaving-drupal). - **Adobe Experience Manager (AEM) 6.5:** [upgrade in place, move to AEM as a Cloud Service or replatform](https://deploi.ca/sanity/migration/leaving-aem), with a follow-up on [whether AEM as a Cloud Service is a replatform](https://deploi.ca/sanity/migration/leaving-aem/aem-cloud-service). - **Sitecore, Kentico Xperience 13 and Umbraco 13:** [Sitecore's new support terms](https://deploi.ca/sanity/migration/leaving-sitecore), [Kentico's end of support](https://deploi.ca/sanity/migration/leaving-kentico) and [Umbraco's end of life](https://deploi.ca/sanity/migration/leaving-umbraco). - **Contentful under Salesforce:** [renew, renegotiate or leave for Sanity](https://deploi.ca/sanity/migration/leaving-contentful), with follow-ups on [what the acquisition changes](https://deploi.ca/sanity/migration/leaving-contentful/salesforce-ownership) and [the exit checklist](https://deploi.ca/sanity/migration/leaving-contentful/exit-checklist). - **WordPress, with no deadline:** [whether to leave at all](https://deploi.ca/sanity/migration/leaving-wordpress). - **Any other legacy CMS:** [upgrade, replatform or rebuild the front end](https://deploi.ca/sanity/migration/leaving-a-legacy-cms), with the end-of-life calendar as its follow-up. Two dates send many readers here: Drupal 10 reaches end of life on 9 December 2026 ([Drupal core release schedule](https://www.drupal.org/about/core/policies/core-release-cycles/schedule); [Drupal.org policy issue](https://www.drupal.org/project/drupal/issues/3524111), October 2026), and Salesforce says it completed its purchase of Contentful on 1 September 2026 ([Salesforce](https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-contentful/), October 2026). The Drupal and Contentful decision pages each say when to upgrade or stay and when to move: Drupal's deadline forces a version upgrade first, and the Contentful choice falls at your renewal. ## Which migration playbook covers your move to Sanity? Seven source-specific migration playbooks are in this first release as of October 2026, one per content management system (CMS): [WordPress](https://deploi.ca/sanity/migration/wordpress-to-sanity), [Contentful](https://deploi.ca/sanity/migration/contentful-to-sanity), [Drupal](https://deploi.ca/sanity/migration/drupal-to-sanity), [Adobe Experience Manager (AEM)](https://deploi.ca/sanity/migration/aem-to-sanity), [Sitecore](https://deploi.ca/sanity/migration/sitecore-to-sanity), [Kentico Xperience](https://deploi.ca/sanity/migration/kentico-to-sanity) and [Umbraco](https://deploi.ca/sanity/migration/umbraco-to-sanity). Each maps that CMS's content types to Sanity documents, converts its rich text to Portable Text, Sanity's structured rich-text format, and gives Deploi's call: move at once, move in phases, or stay. Any other CMS starts from the general playbook for a CMS migration to Sanity. Four follow-ups each take one risk of the move, so each can go to the person who owns that risk: - [The migration checklist](https://deploi.ca/sanity/migration/cms-to-sanity/migration-checklist): one owner and one proof per item. - [Cutover and rollback](https://deploi.ca/sanity/migration/cms-to-sanity/cutover-and-rollback): one switch or a parallel run. - [Safe imports](https://deploi.ca/sanity/migration/cms-to-sanity/safe-import): dry runs, draft prefixes and rollback. - [Keeping SEO through the move](https://deploi.ca/sanity/migration/cms-to-sanity/seo-preservation): URLs, redirects and dates. If search engine optimization (SEO) is your main worry, [what breaks for SEO when you go headless](https://deploi.ca/sanity/faq/what-breaks-for-seo-when-going-headless) names the plugin jobs a new front end must rebuild. [Deploi's Sanity migration service](https://deploi.ca/sanity/migration) links every guide here, the playbooks by source platform and the follow-ups by migration step, with Deploi's migration estimates. ## Which comparison covers the product you're weighing against Sanity? Twelve comparison pages and seven category pages are in this first release as of October 2026, and [the comparison index](https://deploi.ca/sanity/compare) groups them by rival and names the question that decides each matchup. Each comparison puts Sanity against one product and gives Deploi's call on when each wins. Each category page matches a shortlist to the condition each option wins and names where Sanity is not the pick, so you can rule Sanity out as quickly as in. - **A suite you already license:** Sanity against [Adobe Experience Manager (AEM)](https://deploi.ca/sanity/compare/sanity-vs-aem) or [Sitecore](https://deploi.ca/sanity/compare/sanity-vs-sitecore). - **Another headless content management system (CMS):** start with [Sanity against Contentful](https://deploi.ca/sanity/compare/sanity-vs-contentful), and [what the two cost as seats, locales and content grow](https://deploi.ca/sanity/compare/sanity-vs-contentful/pricing). - **A Shopify store:** [Shopify metaobjects or Sanity for your store's content](https://deploi.ca/sanity/compare/sanity-vs-shopify-metaobjects). ## Which Sanity features has Deploi reviewed, and on what evidence? Deploi has reviewed two Sanity features as of 24 October 2026, and both verdicts rest on Sanity's documentation, not production use: [whether Content Releases is worth the add-on](https://deploi.ca/sanity/features/content-releases) and [Visual Editing for marketing teams](https://deploi.ca/sanity/features/visual-editing). Content Releases schedules many documents to publish as one release; Visual Editing lets editors click from a page preview to the field behind it. Each review says whether to adopt now, on which plan and with what limits, and dates every plan gate, because Sanity moves them: Content Releases changed plans on 6 November 2025 ([Sanity's Content Releases post](https://www.sanity.io/blog/introducing-content-releases), October 2026). Every feature, review, use case and integration page carries one of three experience labels: - **Production:** Deploi runs the feature on deploi.ca, and the page shows the evidence. - **Tested:** Deploi built and ran it outside production, and the page says where. - **Documentation:** the verdict rests on Sanity's documentation and public sources. [How well Sanity handles localization](https://deploi.ca/sanity/review/localization) also carries the documentation label: its score rests on Sanity's documentation, its pricing page and the translation connectors' pages. ## Which Sanity use cases has Deploi written up, and on what evidence? Three Sanity use cases are in this first release as of October 2026, and only the knowledge base with AI answers rests on first-hand evidence. Each combines several Sanity capabilities to solve one operational problem and gives Deploi's build, buy or depends call. - **Production label:** [the knowledge base with AI answers](https://deploi.ca/sanity/use-cases/knowledge-base-with-ai-answers), because deploi.ca's Shopify FAQ assistant runs that pattern with semantic search in GROQ (Graph-Relational Object Queries) and a keyword fallback. - **Documentation label:** the use cases on running several brands from one Sanity setup and on consolidating several content management systems (CMSs) into Sanity, because their verdicts rest on Sanity's documentation and public sources. [The use-case index](https://deploi.ca/sanity/use-cases) matches each content problem to its use case, says when a point tool is the better buy and names the plan gates two of the three turn on. ## Which Deploi builds on Sanity can you read in full? Two build write-ups are in this first release as of October 2026, and both describe Deploi's own Sanity systems on deploi.ca. Each one shows what was built and why, the mechanism, real counts with their date, and what went wrong, so you can judge the pattern before you reuse it. - [Semantic search with GROQ (Graph-Relational Object Queries) and no vector database](https://deploi.ca/sanity/builds/semantic-search-in-groq): the search behind the assistant on Deploi's Shopify FAQ hub, with a keyword fallback. - [Publishing 701 decision pages at agent scale](https://deploi.ca/sanity/builds/agent-scale-publishing): how the Build vs. Buy pages reach Sanity in waves, including the wave that shipped with dangling references and how it was fixed. Both builds come from Deploi's Sanity footprint on deploi.ca: four sections and 4,642 documents across two datasets in one Sanity project, image assets included, counted 24 October 2026. A third Deploi build is public: the FAQ Hub with AI Chatbot template, which Martin Dejnicki published on Sanity Exchange, where it is listed as built by Deploi ([Sanity Exchange](https://www.sanity.io/templates/faq-hub-with-ai-chatbot), October 2026). ## How does Deploi check the facts on these pages? Every fact on the Sanity Hub carries its source and the date we checked it, and a script matches each quote from sanity.io against a snapshot of Sanity's site taken when the page was checked. Plan, price and availability claims need a second source. A reviewer who didn't write the page checks every claim and scores every passage before the page publishes. When Sanity's own pages disagree, the page names both sides instead of picking one. Sanity's pricing page lists Enterprise unique attributes as "Custom", for example, while its attribute-limit page says moving from Growth to Enterprise doesn't raise the 10,000-attribute limit ([Sanity pricing](https://www.sanity.io/pricing); [Sanity Docs, Attribute limit](https://www.sanity.io/docs/content-lake/attribute-limit), October 2026). > **Who we are, and who we aren't** > > Deploi is not a Sanity partner, it is not affiliated with Sanity, and Sanity did not review these pages. Deploi earns money when teams hire it for Sanity work, so each answer page lists the events that would change our answer, and you can check the reasoning yourself. ## Deploi's point of view **Our take.** Sanity is the strongest default we know for teams whose developers will own the content model, and the wrong choice for a team that wants a finished editing tool with no code to maintain. **What we've seen.** Deploi's own Sanity project holds 4,642 documents across two datasets, image assets included, counted 24 October 2026. Among them are 701 Build vs. Buy decision pages, 256 FAQ answers, 53 data pages and 96 Shopify build records, edited in one Sanity Studio with three workspaces. **Who reviews these pages.** Martin Dejnicki has worked with content management systems for more than 20 years and built and managed hundreds of WordPress sites between 2005 and 2017. He reviews every page on the Sanity Hub before it publishes. ## Ready to plan your move to Sanity? Contact us today to talk through your current content management system, its deadlines and whether Sanity fits, before anything moves. [Contact us](https://deploi.ca/contact) ## Sources 1. [Deploi, Build vs. Buy on Shopify](https://deploi.ca/shopify/build-vs-buy), checked 24 October 2026 2. [Deploi, Shopify data and statistics, every source shown](https://deploi.ca/shopify/data), checked 24 October 2026 3. [Deploi, Shopify FAQ for Mid-Market and Enterprise Brands](https://deploi.ca/shopify/faq), checked 24 October 2026 4. [Deploi, Shopify Builds](https://deploi.ca/shopify/builds), checked 24 October 2026 5. [Sanity Exchange, FAQ Hub with AI Chatbot template](https://www.sanity.io/templates/faq-hub-with-ai-chatbot), checked 24 October 2026 6. [Drupal.org, Drupal core release schedule](https://www.drupal.org/about/core/policies/core-release-cycles/schedule), checked 24 October 2026 7. [Salesforce, Salesforce Signs Definitive Agreement to Acquire Contentful](https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-contentful/), checked 24 October 2026 8. [Sanity, Plans that scale with you](https://www.sanity.io/pricing), checked 24 October 2026 9. [Sanity Docs, Attribute limit](https://www.sanity.io/docs/content-lake/attribute-limit), checked 24 October 2026 10. [Sanity, No More 'DO NOT PUBLISH': Introducing Content Releases](https://www.sanity.io/blog/introducing-content-releases), checked 24 October 2026 11. [Sanity, Sanity for Startups](https://www.sanity.io/startups), checked 24 October 2026 12. [Drupal.org, Define explicit Drupal 10 end of life date](https://www.drupal.org/project/drupal/issues/3524111), checked 24 October 2026