--- schema_version: "1" id: d5ec4be0581c0f6856efc80a86258c40c25768cfae74698d07e5ce5a4e5a4360 title: Try Salesforce Voice in Your Sandbox collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/voice_sandbox.md canonical_url: https://help.salesforce.com/s/articleView?id=service.voice_sandbox.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 8a06f1dc6cdc2f59c23194a013f5c1549a5c3042e03e3b35591a653a4d044e3b description: You can test out Salesforce Voice (formerly Service Cloud Voice) with your telephony provider in your sandbox. Before you set up Voice in a sandbox, follow these best practices to prepare the environment and to migrate data. products: - Service Cloud - Digital Engagement release: "264" --- # Try Salesforce Voice in Your Sandbox You can test out Salesforce Voice (formerly Service Cloud Voice) with your telephony provider in your sandbox. Before you set up Voice in a sandbox, follow these best practices to prepare the environment and to migrate data. ### Required Editions This article applies to: - Salesforce Voice with Amazon Connect - Salesforce Voice with Partner Telephony - Salesforce Voice with Partner Telephony from Amazon Connect
View supported editions.
Instructions and guidelines for using Salesforce Voice in a sandbox vary based on your telephony provider. Work with your telephony provider to request this content. This information applies to the Amazon Connect telephony provider only. To learn how to refresh your Salesforce Voice with Amazon Connect sandbox, go to the [Salesforce Voice with Telephony Providers Implementation Guide](https://developer.salesforce.com/docs/atlas.en-us.voice_developer_guide.meta/voice_developer_guide/voice_intro.htm). When you set up Voice in a sandbox, Salesforce creates an Amazon Web Services (AWS) subaccount and an Amazon Connect instance for you. When you create a contact center in Service Cloud Voice in your sandbox, Salesforce creates an Amazon Connect instance for you. Charges for your Amazon usage in the sandbox are charged to the production org. To access Amazon Web Services documentation, go to [https://docs.aws.amazon.com](https://docs.aws.amazon.com). If Voice is set up in a sandbox, only do a [Partial Copy sandbox refresh](https://help.salesforce.com/articleView?id=platform.data_sandbox_refresh.htm&type=5&language=en_US). If you do a full refresh, you have to set up Voice again. When you’re finished using Voice in your sandbox, delete your Amazon Connect instance, so your org doesn’t incur more charges for Amazon Connect usage. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_channels-264-0-0-production-enus/f3c4b3d2-ff86-4f7c-9fe2-3d8b23d35109/images/icon_note.png) Note When Salesforce Voice and Conversation Insights are both turned on in the same production org, copying the production org to a sandbox turns off Conversation Insights and breaks the flow of data to the Salesforce Voice CRM Analytics app. To restore the data flow, turn on Conversation Insights in the sandbox. ## Delete Existing Contact Centers If you already have a contact center set up in your Salesforce production org, follow these steps before setting up Voice in your sandbox: 1. Copy the data from your production org to the sandbox. 2. Delete the call center information from the sandbox. 3. Disable the identity provider. 4. Delete the contact center. When you delete the contact center, the external client app and external client app data are also deleted. For contact centers created before the Summer '26 release, Salesforce uses connected apps for single sign-on (SSO). For such contact centers, when you delete the contact center, the connected app and connected app data are also deleted. ## Migrate Data from Amazon Web Services Migrate this data from AWS from your production org to your sandbox. Alternatively, if you’re ready to use Voice in production, you can migrate the data from your sandbox to your production org. 1. Import Voice sample contact flows into Amazon Connect. 2. Salesforce creates an Amazon Connect instance when you create a contact center in Voice. If you have other Connect instance configurations, you must manually reconfigure them. 3. By default, Salesforce makes the Voice Lambda functions available in your Connect instance when you create your contact center. If you have other Lambda functions, migrate them to the new Connect instance. ## Migrate Data from Salesforce Migrate this data from your Salesforce production org to the sandbox. Alternatively, if you’re ready to use Voice in production, you can migrate the data from your sandbox to your production org. 1. Migrate the contact center information. 2. Migrate users associated with the contact center. Use the Data Loader to migrate users. 3. Export and deploy the configuration files from the external client app. For contact centers created before the Summer '26 release, Salesforce uses connected apps for single sign-on (SSO). For such contact centers, export and deploy the configuration files from the connected app. ## Delete Instance and Close AWS Account Refer to Amazon documentation to [delete your Amazon Connect instance](https://docs.aws.amazon.com/connect/latest/adminguide/delete-connect-instance.html) and [close your AWS account](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts_close.html). #### See Also - [Manage Call Centers](https://help.salesforce.com/s/articleView?id=service.cti_admin_managecc.htm&type=5&language=en_US) - [Delete a Connected App](https://help.salesforce.com/s/articleView?id=xcloud.connected_app_delete.htm&type=5&language=en_US) - [_Amazon Connect Administrator Guide_: Delete your instance](https://docs.aws.amazon.com/connect/latest/adminguide/delete-connect-instance.html) - [_AWS User Guide_: Closing an AWS account](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts_close.html)