> For the complete documentation index, see [llms.txt](https://docs.zingg.ai/zingg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingg.ai/zingg/community-and-enterprise-editions/community-vs-enterprise/migrating-from-community-to-enterprise-content-to-be-added.md).

# Migrating from Community to Enterprise

What changes when you move from Zingg Community to Enterprise imports, class names, and new features unlocked.

Zingg Enterprise is a near drop in replacement to Zingg Community. The same models can be migrated from the Community to the Enterprise if you prefer, or you can tune them, or build newer faster and more accurate ones. Zingg Enterprise on Snowflake even comes with utilities to copy over models to Snowflake Tables.\
\
The configuration JSON and Python API are designed to be similar to reduce migration effort. Most of the time in the migration would be in using the new set of features available in Zingg Enterprise.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zingg.ai/zingg/community-and-enterprise-editions/community-vs-enterprise/migrating-from-community-to-enterprise-content-to-be-added.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.