---
schema_version: "1"
id: 576e32ac422a324c02ea94d498754cc54dfcb238fd8ebc03e6b7c5be2b200964
title: Upload Change Sets During Staggered Salesforce Service Upgrades
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/changesets_outbound_server_upgrade.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.changesets_outbound_server_upgrade.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 05449d6b46a83be937c48e3dc7e5ef600b5864f3b23b35228c9fc22c382b2015
description: During Salesforce service upgrades, production and sandbox environments don't always run the same version of the platform because the upgrades are staggered. Some components may have new functionality that prevents you from deploying that type of component. You can deploy such components after the production org runs the same version as sandbox.
products:
  - Salesforce Platform
release: "264"
---
# Upload Change Sets During Staggered Salesforce Service Upgrades

During Salesforce service upgrades, production and sandbox environments don't always run the same version of the platform because the upgrades are staggered. Some components may have new functionality that prevents you from deploying that type of component. You can deploy such components after the production org runs the same version as sandbox.

If you upload a change set with components that can't be deployed because of incompatible versions, the system detects which components can't be deployed. Salesforce gives you the option of uploading the remaining components.

#### See Also

- [Upload an Outbound Change Set](https://help.salesforce.com/s/articleView?id=platform.changesets_outbound_init_deploy.htm&release=264.0.0&type=5 "When you've assembled the components in a change set, you can upload it to another Salesforce org. After you upload a change set, you can't edit it or recall it.")