Change Sets vs Modern Deployment
By the end of this lesson, you'll be able to:
- Explain what a change set is and its real limitations
- Compare it against a source-driven, DX-based deployment
- Recognize why most professional teams have moved away from change sets
Prerequisites: "Packaging: Unlocked and Managed (Overview)"
What a change set is
A change set is a point-and-click way to select specific metadata components in one org's Setup UI and deploy them to a directly connected org (like a sandbox to production) — no command line, no local files, entirely manual selection through clicking.
Where change sets fall short
- No real version control. A change set isn't a Git-trackable artifact — there's no meaningful diff, no branch, no code review process (Module 14) built around it.
- No automated testing integration. Nothing about a change set naturally connects to running Module 31's test suite before deploying.
- Manual, error-prone selection. Forgetting to include one dependent component is a common, real mistake — there's no equivalent of
git statusshowing exactly what's about to move.
The modern, source-driven alternative
sf project deploy start --target-org production --manifest package.xmlThis module's entire arc — scratch orgs, source tracking, packaging — exists specifically to enable this: deployments driven by version-controlled source files, reviewable through Module 14's pull-request process, testable automatically (a later lesson covers CI/CD), and reproducible exactly the same way every time. Most professional Salesforce teams have moved to this model specifically because it closes every gap change sets leave open.
Exercise
As a comment, name the specific gap in change sets that this course's entire testing discipline (Module 31) can't connect to.
Show hint
Think about what would need to happen automatically before a deployment for tests to actually matter.
Change Sets vs Modern Deployment Quiz
My Notes
Log in to keep private notes on this lesson.
Questions about this lesson
No questions yet — be the first to ask.
Log in to ask a question about this lesson.
Summary
Change sets are Salesforce's original, UI-based deployment mechanism — this lesson compares them directly against the source-driven approach this module has built toward, and explains why most teams have moved on.