---
schema_version: "1"
id: 108803f52643e2693a2a13a234efa753ec0e8253ebce98c37ebdeab1fc47b214
title: Deploying Components
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform/salesforce-migration-guide/guides/daas/forcemigrationtool-deploy-components.md
canonical_url: https://developer.salesforce.com/docs/platform/salesforce-migration-guide/guide/forcemigrationtool-deploy-components.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: cc196ba767763621248b793f414063da1c5c596c0dda232b46aac80e6af1d970
products:
  - Ant Migration Tool Guide
  - Platform Developer Content
---

# Deploying Components

**note:** The Ant Migration Tool is retired with Spring ’24. The tool continues to function as-is for future API versions but isn’t updated with new functionality and isn’t supported. If Salesforce adds a new feature that is incompatible with Ant, the Ant Migration Tool won't be updated to support it. To manage metadata changes, switch to Salesforce CLI for a modern, supported developer experience.

You can deploy any set of components as a package or into your organization directly in the unpackaged package. The package used is not determined by the build.xml target, but by the project manifest (package.xml). A sample deployment target follows:

```xml
<target name="deployUnpackaged">
  <sf:deploy 
      username="${sf.username}" 
      password="${sf.password}" 
      sessionId="${sf.sessionId}"
      serverurl="${sf.serverurl}" 
      deployroot="projectFolder"/>
</target>
```