> For the complete documentation index, see [llms.txt](https://helpdocs.yoxel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.yoxel.com/yoxel-sync/migrating-yoxel-to-another-salesforce-instance.md).

# Migrating Yoxel to another Salesforce instance

When you do any kind of Salesforce migration (moving from one org to another, upgrading to another edition of Salesforce, etc.), you will be given a new Organization ID. When that occurs, you will need to re-install Yoxel and we need to transfer your subscription information to the new org.

Please submit a support case by emailing us at [support@yoxel.com ](<mailto:support@yoxel.com >)and let us know the migration is happening. We will leave Yoxel turned on in your old org for a couple of weeks to allow you time to compare/transfer data sets and settings before transferring all subscription information to the new org.


---

# 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://helpdocs.yoxel.com/yoxel-sync/migrating-yoxel-to-another-salesforce-instance.md?ask=<question>&goal=<endgoal>
```

`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.