Setting up in a sandbox
A Salesforce sandbox is a copy of your production environment that you can use for testing, training, and development without affecting live data. Setting up MoveData in a sandbox lets you safely validate customisations, test new integrations, and train users before making changes in production.
How sandboxes work with MoveData#
When you create a sandbox from your production Salesforce environment, Salesforce copies your installed packages — including MoveData and its extensions — along with your configuration.
However, authentication does not carry over. You must re-authenticate MoveData in the sandbox before it can process data.
Re-authentication is required
Your production MoveData authentication does not transfer to a sandbox. MoveData will not process any notifications in the sandbox until you complete the re-authentication steps below.
Sandbox login URLs
Salesforce sandboxes use test.salesforce.com instead of login.salesforce.com.
When authenticating MoveData in a sandbox, ensure you are logging in through the correct URL.
Setup checklist#
Follow these steps to configure MoveData in your sandbox:
- Create or refresh your sandbox — follow the Salesforce sandbox documentation to create a new sandbox or refresh an existing one.
- Log in to the sandbox — use your sandbox credentials at
test.salesforce.com. Salesforce typically appends the sandbox name to your username (for example,user@org.com.sandboxname). - Re-authenticate MoveData — open MoveData in the sandbox and complete the authentication process. Authorise under a user with the necessary permissions. See The MoveData Authorised User for guidance on choosing the right user.
- Verify permission sets — confirm that the MoveData Authorised User and any other users who need access have the correct permission sets assigned.
- Review duplicate rules — check that your duplicate rules are appropriate for the sandbox. Production duplicate rules carry over, but you may want to adjust them for testing.
- Update Salesforce IDs — if your configuration references specific Salesforce record IDs (for example, campaign IDs or record type IDs in flows), update these to match the sandbox. Salesforce generates new IDs for records in each sandbox.
- Configure integrations — set up your integrations following the same process as production. Connect your fundraising platform to the sandbox instance of MoveData.
- Test the integration — send a test notification through the integration and verify it processes successfully. See Testing your integration for a detailed testing guide.
Sandbox-specific considerations#
- Data volume — depending on your sandbox type (Developer, Developer Pro, Partial Copy, or Full Copy), you may have limited data. This can affect duplicate matching and other data-dependent features.
- Sandbox refreshes — when you refresh a sandbox, you need to re-authenticate MoveData again. Any configuration changes made only in the sandbox will be overwritten.