---
schema_version: "1"
id: 601472cf2490ea0b098d261a033ff9737337afcaf0760d6081fe07295d023ae7
title: Sandboxes for Omnistudio Migration
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_migrate_prepare_sandbox_orgs.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_prepare_sandbox_orgs.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 0e012522795147f2655512ff41e317e9d849e9ef51ef22da117df9e1a81fbf08
description: "Create two dedicated sandboxes: a migration development sandbox for converting your Omnistudio components to work with the standard runtime, and a migration testing sandbox for thoroughly testing migrated Omnistudio components before you deploy to production."
products:
  - Omnistudio
release: "264"
---
# Sandboxes for Omnistudio Migration

Create two dedicated sandboxes: a migration development sandbox for converting your Omnistudio components to work with the standard runtime, and a migration testing sandbox for thoroughly testing migrated Omnistudio components before you deploy to production.

Before you begin, review [About the Migration Process](https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_about_migration.htm&release=264.0.0&type=5 "The migration process uses the Omnistudio Migration Assistant to move components such as Flexcards, Omniscripts, Data Mappers, Integration Procedures, custom labels, Omni Global Auto Numbers, and related objects such as Apex classes, FlexiPages, Experience Cloud site pages, Lightning web components (LWCs), and custom labels from managed package runtime and Omnistudio Foundation package to the Omnistudio standard runtime. This makes sure that the components from industry packages such as Insurance (INS), Communications, Media, and Energy (CME), and Public Sector (PS) match the standard runtime, easing maintenance and upgrades.").

When choosing a sandbox environment, consider the sandbox storage limits. A good principle is about 30% extra space for the migration. For more information about sandboxes, see [Sandbox Licenses and Storage Limits by Type](https://help.salesforce.com/s/articleView?id=platform.data_sandbox_environments.htm&language=en_US).

Create the migration development sandbox and migration testing sandbox by making a copy of your production org or refreshing an existing sandbox. We recommend creating or refreshing the sandboxes at the same time. Any differences between the migration development sandbox and migration testing sandbox can cause problems during deployment.

## Migration Development Sandbox

Use this sandbox to evaluate your migration readiness, make necessary changes before migration, and then convert your Omnistudio components to work with the Omnistudio standard runtime.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_important.png)

Important Don’t run the Omnistudio Migration Assistant in other orgs, especially in your production environment. Run the tool in Migrate mode only for Omni Global Auto Numbers in your production org.

## Migration Testing Sandbox

Use this sandbox to test the components you converted in the development sandbox.