Working with Salesforce Sandboxes – Formstack

Optimize your use of Formstack Forms for Salesforce & Documents for Salesforce with Salesforce Sandboxes with the following considerations:

Formstack - Forms for Salesforce Sandbox:

Most Forms for Salesforce plans (Native Standard, Native Essentials, Native Professional, Pro & NativeCloud Pro) include tools to Add Managed Sandboxes connected to your Production Org, which will then allow you to migrate forms between your various Salesforce organizations.
After migrating forms using our form migration tools or copying over forms as part of a Sandbox copy or refresh, all Formstack Forms need to be republished. This is described in the Publish Your Migrated Form in the Destination Org section of the above form migration help article.
If you are auto-generating prefill links, you will also need to set up the auto-generate pre-fill process specific to the Sandbox.
Experience Cloud Forms (Previously known as Community Forms) need to be updated to point to the correct form in the Lightning Component.
This article includes notes on adding remote sites in a Sandbox.
This article includes further details on refreshing a Sandbox with NativeCloud installed

Your Formstack Documents sandbox environment can be connected to multiple Salesforce orgs by following the API key process outlined in our setup guide.
If you are creating a UAT Sandbox this is typically a full copy which means your Formstack Documents mapping will carry over.
If you are creating a Dev or Partial Sandbox, in these cases customers typically don’t bring over mappings, and instead, use the export/import feature to copy and paste JSON from one org to the other. This is described here .
If you are using Formstack Documents deliveries back to Salesforce, this will need to be updated for any new Sandbox. You should use conditional deliveries to deliver documents to the correct Salesforce org.
For more comprehensive deployments, view how to use Data Loader to export mappings from Sandbox to Production.