---
schema_version: "1"
id: 73512c8c3e011f8f00d50b14021419d2482352c3eafe8e3b4a610e2b31e04d3f
title: Best Practices for Cloning On-Demand Sandboxes
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/commerce-cloud/b2c-commerce/guides/control_center/b2c_cc_clone_best_practices.md
canonical_url: https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/b2c_cc_clone_best_practices.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 0fb50e7e3da365f19812d5d9d660ff4735f9e318ce7927638526090007b6ec29
products:
  - Composable Storefront
  - Salesforce APIs
---
# Best Practices for Cloning On-Demand Sandboxes

Follow these recommendations to optimize your sandbox cloning workflow.

| Best Practice                        | Description                                                                                                                                                                               |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Choose Appropriate Resource Profiles | Select the profile that meets your requirements. For cloning, the target profile should be the same size or larger than the source sandbox profile.                                       |
| Review Custom Configurations         | After cloning completes, test all integrations and custom configurations. Update third-party endpoints, keystores, and Business Manager customizations that reference the source sandbox. |
| Manage Cloned Sandboxes              | Delete cloned sandboxes when no longer needed to reduce credit consumption.                                                                                                               |
| Plan Clone Operations                | Where feasible, execute large clone operations during times when sandbox usage is low.                                                                                                    |
| Save Your Work                       | During the clone process, the source sandbox is stopped. Make sure to save any open work before triggering the clone operation.                                                           |
| Monitor Clone Progress               | Monitor the progress of a clone using the Monitor Clone Progress API. Poll the API every 30–60 seconds to check status, but avoid excessive polling, which can trigger rate limits.       |
| Set Time-to-Live Values              | Configure the TTL parameter to automatically clean up temporary clones and avoid consuming unnecessary credits.                                                                           |