Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Full Development Environment entry
How-to guide

How to pick the right Development Environment for the work

The pattern: match the environment to the work, name per convention, refresh deliberately, promote through the pipeline. The discipline pays back in operational clarity and reduced production incidents over years.

By Dipojjal Chakrabarti · Founder & Editor, Salesforce DictionaryLast updated May 18, 2026

The pattern: match the environment to the work, name per convention, refresh deliberately, promote through the pipeline. The discipline pays back in operational clarity and reduced production incidents over years.

  1. Identify the work scope and required fidelity

    Individual learning: Developer Edition or Trailhead Playground. Code dev: scratch or Developer sandbox. Integration testing: Partial Copy. UAT or performance testing: Full Copy.

  2. Check sandbox quota in Setup, Company Information

    Confirm the org has the sandbox tier available before assuming you can spin one.

  3. Create the environment with a convention-based name

    DEV-feature-name, INT, UAT, STAGE-2026Q1. The name carries purpose.

  4. Apply the Sandbox Template for Partial Copy

    Partial Copy uses a Sandbox Template to scope which data subset to copy.

  5. Establish the promotion path through Change Sets or DevOps Center

    The path from DEV to production drives the deployment workflow.

  6. Schedule refreshes around release cycles

    Full Copy refresh is disruptive; schedule for between releases and communicate to UAT users.

  7. Retire unused environments to reclaim quota

    Sandboxes accumulate. Quarterly audit identifies retirement candidates.

Key options
Environment typeremember

Developer Edition, Developer/Developer Pro/Partial Copy/Full Copy sandbox, Scratch Org, Trailhead Playground.

Naming conventionremember

Purpose-driven naming (DEV, INT, UAT, STAGE) drives operational clarity.

Refresh cadenceremember

Per-tier refresh interval; plan around release cycles.

Sandbox Templateremember

Configuration for Partial Copy sandbox data subset.

Promotion pathremember

Documented flow from DEV through INT, UAT, STAGE, production.

Gotchas
  • Full Copy sandboxes are expensive. Budget deliberately; one Full Copy is usually enough for UAT.
  • Sandbox refresh is destructive of in-sandbox work. Coordinate before refreshing.
  • Scratch orgs require Dev Hub configuration. The setup is one-time; ongoing scratch org lifecycle is automated through CLI.
  • Naming conventions are easy to skip and impossible to retrofit cleanly. Establish at the first sandbox creation.
  • Stale unused sandboxes consume quota. Quarterly retirement audit keeps quota available for active work.

See the full Development Environment entry

Development Environment includes the definition, worked example, deep dive, related terms, and a quiz.