> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/forms/salesforce-integration/form-template-deployment-or-migration.md). # Form Template Deployment (or Migration) [SharinPix Form Templates](/forms/form-elements/sharinpix-form-template-editor.md) can be migrated from one Salesforce org (for example, a sandbox) to another Salesforce org (for example, a production org). This is useful when a Form Template has been built and tested in a sandbox and needs to be deployed to production. There are two ways to deploy a Form Template between Salesforce orgs: * [Deploy Using the SharinPix Salesforce CLI Plugin](#migrate-using-the-sharinpix-salesforce-cli-plugin) * [Deploy Manually](#migrate-manually) ### Deploy Using the SharinPix Salesforce CLI Plugin The SharinPix Salesforce CLI Plugin syncs SharinPix forms between a Salesforce org and files on your computer. Use it to pull a Form Template from your sandbox and push it to production. This method is recommended when deploying multiple Form Templates or repeating the migration as part of a deployment process. For step-by-step instructions, see [SharinPix Salesforce CLI Plugin](https://docs.sharinpix.com/documentation/cookbook/sharinpix-salesforce-cli-plugin). ### Deploy Manually For a single Form Template, copy the JSON from the Advanced Settings in the source org and paste it into a new Form Template record in the target org. 1. Open the Form Template in your Sandbox and go to Advanced Settings. 2. Copy the Form Template JSON. 3. In Production, create a new Form Template record. You can keep the same name for the template. 4. Paste the same JSON into the new Form Template.
{% hint style="info" %} The manual method works well for a single, occasional deployment. If you need to migrate multiple Form Templates or repeat the migration regularly, use the SharinPix Salesforce CLI Plugin instead. {% endhint %} --- # 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.sharinpix.com/forms/salesforce-integration/form-template-deployment-or-migration.md?ask=&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.