Deployment from Sandbox to Production using Change Sets

Sandbox :

Outbound Change Sets

An outbound change set contains customizations that you want to send from this organization to another organization. These customizations can include new components or modifications to existing components, such as apps, objects, reports, or Apex classes and triggers. An outbound change set can't be used to delete or rename components in another organization.

Example uses:

• Deploy Apex classes and triggers developed in sandbox to production

• Copy custom objects and other customizations to a sandbox without refreshing it

• Migrate changes across environments, e.g. dev sandbox to QA sandbox to production

We need to create change sets in sandbox environment using below steps:

Step 1:

Deploy > Outbound Change Sets > New

Name : Apex and Visualforce

Step 2: 

Create new Components like (VF, Apex Class, Objects, Triggers, App, Reports, etc...) Using Add Button.

'Upload' button is disabled in the Change Set Details section. once added the component using Step 3 and 'Upload' button also enabled.

Step 3: 

Choose the component mention below screen and finally click 'Add To Change Set' button.

Step 4:

once component added, then we need to upload the component from sandbox to production using 'UPLOAD' button.

Step 5:

Once finished Step 4, It will be available shortly in Production, so that an administrator can deploy it in Production 'Inbound Change Sets'.

Production

Deploy > Inbound Change Sets > New

Inbound Change Sets

An inbound change set contains customizations sent from another organization to this one. These customizations can include new components or modifications to existing components, such as apps, objects, reports, or Apex classes and triggers. An inbound change set can't delete or rename components in this organization.Example uses:

•     Deploy Apex classes and triggers developed in sandbox to production

•     Apply changes from other environments to this organization, such as new objects and fields

•     When planning to deploy on a schedule, validate pending changes ahead of time

Finally we need to Validate and Deploy it.