> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/deployment-and-licensing/share-vs-enterprise/migrating-between-share-and-enterprise.md). # Migrating between Share and Enterprise ### When migration is required You may need to migrate between Share and Enterprise when: * Moving from trial to production * Changing hosting models * Adopting new security or compliance requirements * Migrating Tableau Server to Tableau Cloud (or vice versa) *** ### What changes during migration * Extension hosting URL * Extension configuration references * Deployment responsibility *** ### What stays the same * Core product functionality * Workbook logic * User experience *** ### Important note on extension URLs Tableau stores the extension URL inside the workbook.\ When environments change, the extension URL must be updated. See **Tableau Platform Support → Environment changes & URL migration** for details. *** ### Summary * Share and Enterprise offer the same features * The choice depends on hosting, control, and compliance needs * Migration is supported and does not require rebuilding workbooks --- # 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://docs.infotopics.com/deployment-and-licensing/share-vs-enterprise/migrating-between-share-and-enterprise.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.