Deployments
Compare Salesforce orgs and deploy with confidence
Pick a source and a target org and get a classified diff. Every component marked new, changed, unchanged, or deleted with side-by-side differences. Then select exactly what to ship, validate it, and deploy it with the test level you choose.
The decision-reason fields, the service that writes them, and the banner on the Opportunity page. Validated against production on 1 Sep.
| Status | Component | Object | Type | Modified by | Source modified | Target modified | |
|---|---|---|---|---|---|---|---|
Changes | Filter name… | All | All | Any | Filter… | Filter… | |
| New | Opportunity.Credit_Decision_At__c | Opportunity | Custom fields | Alex Rivera | 31 Aug 2026, 12:29 | — | |
| New | Credit_Assessment__c.Decision_Reason__c | Credit_Assessment__c | Custom fields | Alex Rivera | 31 Aug 2026, 12:29 | — | |
| Changed | CreditDecisionService | — | Apex classes | Alex Rivera | 1 Sep 2026, 09:04 | 14 Jul 2026, 16:22 | |
| Changed | CreditDecisionServiceTest | — | Apex classes | Alex Rivera | 1 Sep 2026, 09:04 | 14 Jul 2026, 16:22 | |
| New | creditDecisionBanner | — | Lightning Web Components | Alex Rivera | 1 Sep 2026, 08:51 | — | |
| Only in target | Account.Last_Outbound_Call_At__c | Account | Custom fields | Priya Nair | — | 17 Aug 2026, 21:36 | |
| Only in target | Account.Last_Outbound_SMS_At__c | Account | Custom fields | Priya Nair | — | 17 Aug 2026, 21:36 |
What you can do
- Source vs target comparison across the metadata types you choose — Apex, LWC, fields, record types, validation rules and more
- Every component classified new / changed / unchanged / deleted, most recently modified first
- Side-by-side content diffs for any component
- Runs as a background job: start it, leave, come back
- Select a subset from the diff and deploy it with your chosen test level
- Validate first, then quick-deploy the passed validation without re-running tests
- A package.xml manifest and content hash stored for every run
How it works
Pick source, target, and types
Sandbox → production, dev → UAT, any pair of connected orgs.
Read the classified diff
Colour-coded status per component with side-by-side changes — know exactly what drifted.
Validate, then deploy
Run a check-only validation to prove the package works, then deploy your selection. Production requires an explicit confirmation.
Why it's different
Deploy only what you ticked
Comparisons only ever read, so you can diff production all day without a second thought. Deploying is the opposite by design: owner/admin only, off entirely unless your deployment enables writes, every component checked against the comparison’s allowlist, a lock so two runs can’t hit the same target at once, and an explicit confirmation for production. The expensive DevOps suite behaviours, without the expensive DevOps suite.
Try asking
- Verify a sandbox matches production before UAT starts
- Find what changed in dev since the last release
- Promote a reviewed set of components without a full DevOps platform
- Validate a release against production, then ship the validation that passed
- Keep an auditable manifest of everything that shipped
Deployments — questions
Works even better with
Development Studio
Writes Apex, LWC and Flows, reads the compile errors, tries again.
Learn morePermissions Workbench
Every profile and permission set in one matrix. Bulk-edit straight from it.
Learn moreMetadata Explorer
Fifty-plus metadata types, searchable, with a relationship map you can follow.
Learn moreReplacing something?
- orgadmin.ai vs Gearset
The most mature comparison-and-deploy tool in the ecosystem, with git and CI. Compare when deployment is only one of the jobs you need done.
- orgadmin.ai vs Copado
An enterprise DevOps platform with pipelines, branching and compliance evidence. Compare when the question is whether your team needs that much process.
- orgadmin.ai vs Flosum
Native DevOps that never lets metadata leave Salesforce. Compare when that platform boundary is a compliance requirement rather than a preference.
- orgadmin.ai vs AutoRABIT
An enterprise toolchain with CI/CD, static analysis and backup, from ten licences up. Compare when your team is smaller than its entry package.
- orgadmin.ai vs The whole market
Copado, Gearset, Flosum, AutoRABIT, Salto, Blue Canvas and Hutte — who each one is genuinely for, in one table.
Read next
- Why Salesforce deployments fail — and how to read the errors
Metadata API errors are famously unhelpful. A field-by-field guide to the failures that actually recur, and what each one is really telling you.
- Change sets vs the Metadata API: what actually differs
A change set is not an alternative to the Metadata API — it is a UI on top of it. Once you know which frustrations come from the wrapper and which come from the engine, the upgrade decision gets much simpler.
- Salesforce CI/CD: do you actually need a pipeline?
Every Salesforce DevOps vendor sells you a pipeline. Most small teams deploy twice a month and need something far simpler. Here is how to tell which one you are.
- Salesforce quick deploy: validate first, then ship to production in minutes
Validate against production days before the release, then quick deploy without re-running a single test. How it works, why the button disappears, and a routine that fits the rules.
- Overwrote a teammate's Salesforce changes? How to stop deployments undoing each other's work
Salesforce has no merge and no lock for metadata, so the last deployment wins and a colleague's work can vanish without an error. Here is why it happens, the habits that prevent it, and how orgadmin.ai's team conflict detection flags overlapping work across sandboxes before anyone deploys.
Put Deployments to work on your org
Every AI feature on your own provider key, from A$14.99 per user per month.
- 14-day free trial
- No credit card required
- Cancel any time