Common Admin Tools for Development Operations in Salesforce

Written By Gary Elbaum

Salesforce DevOps is the controlled movement of changes from idea to production with safety, repeatability, and visibility. The tooling ranges from basic admin tools to fully automated, source-driven pipelines.

1. Entry-Level: Native Admin Tools (UI-Based)

Best for small teams and infrequent releases.

  • Sandboxes: Isolated environments for development and testing (Developer → Partial/Full for UAT)

  • Change Sets: Manual deployment of metadata between orgs

  • Setup Audit Trail / Field History: Visibility into changes

  • Data Loader / Import Wizard: Data alignment during releases

Characteristics

  • No external tools required

  • Manual deployments

  • Limited version control

  • Higher risk as complexity grows

2. Mid-Level: Structured Release Management

Transition toward DevOps maturity.

  • Salesforce DevOps Center: UI-based pipeline management connected to Git

  • Git: Version control and collaboration

  • Salesforce CLI: Scripted deployments, automation, scratch orgs

Characteristics

  • Introduces source control

  • Visual pipeline management

  • Reduced manual error

  • Accessible for admins transitioning to DevOps

3. Advanced: Developer-Centric Tooling

Best for complex orgs and frequent releases.

  • Visual Studio Code with Salesforce extensions

  • Git-based branching strategies

  • CI/CD pipelines (GitHub Actions, Azure DevOps, etc.)

  • Scratch org development

Characteristics

  • Fully source-driven development

  • Automated testing and deployment

  • High speed and consistency

  • Requires engineering discipline

4. Ecosystem & AppExchange Solutions

Extends DevOps capabilities.

  • AppExchange tools (e.g., Copado, Gearset, Flosum)

  • Advanced release orchestration, rollback, and compliance tracking

Characteristics

  • Faster enterprise adoption

  • Built-in governance and visibility

  • Less need to build custom pipelines

Operational Foundations (All Levels)

  • Use Permission Sets instead of Profiles

  • Enforce Flow versioning and fault handling

  • Understand dependencies (objects, fields, automation)

  • Monitor post-release (errors, jobs, usage)

  • Back up data before bulk changes

Bottom Line

Change Sets → DevOps Center → CLI + Git → CI/CD + AppExchange

Maturity progresses from manual to automated. Stability comes from disciplined process, not just tools.

Written with the help of ChatGPT

Gary Elbaum
Previous

Renaming picklist values in Salesforce.com
Next

How to Set Up a Simple Salesforce Support Case Process (Step-by-Step Guide)