Salesforce Deployment Checklist: What Developers Should Verify Before Production

A Salesforce deployment is more than moving code from one org to another. A small missing dependency can cause a Flow, Apex class, integration, or user process to fail after release.

A simple pre-deployment checklist can reduce these problems.

1. Check Dependencies

Before deployment, identify everything the change depends on.

For example, an Apex class may depend on:

Custom objects
Custom fields
Permission sets
Flows
Custom metadata
Other Apex classes

Missing dependencies are a common reason deployments need additional fixes.

1. Test the Complete Process

Do not test only the component you changed.

If you modified an Opportunity Flow, test the complete Opportunity process and check related automation, validation rules, and integrations.

This helps catch unexpected side effects.

1. Verify Apex Tests

Run relevant Apex tests and make sure they cover both normal and edge-case scenarios.

Tests should also use realistic data volumes where appropriate, especially for code that processes multiple records.

1. Review Configuration

Code is only part of a Salesforce deployment.

Check configuration such as:

Permission sets
Profiles
Custom settings or metadata
Lightning pages
Flows
Record types
Validation rules

A technically correct deployment can still cause issues if users do not have the required access.

1. Check Integrations

If the release affects an integration, verify endpoints, authentication configuration, field mappings, and error handling.

Test the integration separately when possible rather than assuming that a successful Salesforce deployment means the complete process will work.

1. Have a Rollback Plan

Before releasing an important change, understand how the team will respond if something goes wrong.

Document the affected components and the steps required to restore the previous behavior.

For larger Salesforce projects, Salesforce development services can support development, testing, deployment, and ongoing maintenance.

Final Checklist

Before production deployment, ask:

Dependencies checked?
Tests passed?
User access verified?
Automation tested?
Integrations checked?
Rollback approach understood?

A structured deployment process does not eliminate every production issue, but it can make releases more predictable and easier to manage.