---
schema_version: "1"
id: b047cc4f06c112027ffe0c567c6a4a1b838d72854fae3b3795351ecc421b34e3
title: Deploy and Retrieve
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/salesforcedx/codebuilder/guides/files/deploy-retrieve/codebuilder-deploy-retrieve.md
canonical_url: https://developer.salesforce.com/docs/platform/code-builder/guide/codebuilder-deploy-retrieve.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: c5873989dbb01df56a312a02a3ea72f19bf7222eb9051c04c90f4ee1cbe548aa
products:
  - Agentforce Vibes IDE
  - salesforcedx
---
# Deploy and Retrieve

Retrieve and deploy org metadata by using the Command Palette or the Org Browser.

Say you want to change an existing Apex class or add a custom object to your production org. You first make and test these changes in a scratch org, check for conflicts, and then deploy the changes to another org for your team to access them. This ability to move changes between different Salesforce development environments, such as scratch orgs and sandboxes, for various stages of testing before production, is key to Salesforce development.

We support different deployment options based on your role and needs as a customer, system integrator, or independent software vendor (ISV) partner. For more information on deployment options, see [Build and Release Your App](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_build_and_release_your_app.htm) in the _Salesforce DX Developer Guide_.

After testing your code, retrieve it to your local Salesforce project so that you can keep a single source of truth in source control.

With conflict detection turned on, you don't have to worry about accidentally overwriting changes from other developers in the org. Track changes by easily viewing changes between your local files and your default org at any time.