---
schema_version: "1"
id: 708162d9f80f98a58549a74ad30076816fb12383047bac41716801942820000d
title: Make Large Metadata Configuration Changes
collection: legacydeveloper
version: current
locale: en-us
portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_use_cases_large_config_changes.md
canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_use_cases_large_config_changes.htm
source_site: developer.salesforce.com
content_type: documentation
content_hash: 7c4880d2dbbb0fc8b5351ee6f8ca49b9756527c55e97f33d0f0b8ede91076064
description: Metadata API is better suited than other APIs for deploying large changes to your Salesforce org.
---
# Make Large Metadata Configuration Changes

Metadata API is better suited than other APIs for deploying large changes to your Salesforce org.

Metadata API deploy() and retrieve() calls are file-based and therefore asynchronous. With synchronous commands, large configuration changes require unreasonably long load times. Instead, deploy and retrieve calls begin an asynchronous process that notifies you when it’s complete. Because file-based calls are asynchronous, Metadata API can also handle a queue of deploy requests.

#### See Also

- [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.")
- [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.")