---
schema_version: "1"
id: 391da329492b4ec11f8fe927934544490fd56eb09714aa0a5ef99211d52bd0e8
title: Move Metadata for Production-Level Changes
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_use_cases_prod_level_changes.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_use_cases_prod_level_changes.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 8ba3eb5b932583c792df74f74b5c01c67f5e2b303cc2da579166f8d32bb5371d
description: Use Metadata API to move metadata during large changes, such as merging or splitting Salesforce orgs.
---
# Move Metadata for Production-Level Changes

Use Metadata API to move metadata during large changes, such as merging or splitting Salesforce orgs.

To split an org, first retrieve the metadata to be moved. Then, use a deploy call to push those configurations to the new org. Similarly, to merge two orgs, retrieve existing metadata from one org. Next, use a deploy call to migrate metadata from one org to another.

#### See Also

- [retrieve()](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_retrieve.htm "The retrieve() call retrieves XML file representations of components in an organization.")
- [deploy()](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy.htm "Uses file representations of components to create, update, or delete those components in a Salesforce org.")