Skip to main content

Standard VS Express compare and deploy

This article compares the Standard VS Express compare and deploy workflows and provides guidance on which one to choose for your deployment.

C
Written by Charlotte Gill
Updated today

Standard vs Express Compare and deploy

Which workflow should I pick for the change I'm about to ship?

Gearset's Compare and deploy page now offers two workflows: Standard Compare and deploy and Express Deploy. The right one depends on what you're shipping and how much context you need before clicking Deploy. This page gives you the decision at a glance.

How each one works

⚡ Express Deploy

A streamlined simple, quick workflow for developers and admins who know exactly what they've changed (including dependencies). Add metadata types as you need them and deploy straight from the comparison screen. This means you can get changes deployed quickly without waiting for large comparisons to finish.

🔍 Standard Compare and deploy

Gearset's flagship deployment workflow, built for breadth, depth and safety. Configure a metadata filter up front, run a full comparison, explore changes in detail, and run Problem Analysers before deploying. Whilst this process will take longer, it provides confidence on larger and more complex deployments.

At a glance: which one should I pick?

⚡ Pick Express Deploy when…

🔍 Pick Standard Compare and deploy when…

You know exactly has changed including dependencies (you could have made these changes yourself recently, or be working closely with the team that did)

You need to explore what's changed before deploying

You're deploying a small batch typically 15 items or fewer

You're deploying a large or complex set of changes

You're shipping a hotfix and every extra step is friction

You rely on Problem Analysers as a pre-deploy safety net

You're deploying Sales Cloud metadata only

You're deploying Vlocity, CPQ, RCA, or Config Data

💡 The fast test: Do you know exactly what has changed, including dependencies? Do you just need it out quickly? If yes to all → Express Deploy. Anything else → Standard.

Feature support

Express Deploy is in open pilot and there are several known limitations. Refer to the feature support table in the article What is Express deploy to learn more.

Need to switch mid-session?

If you realise mid-way through an Express deployment that you need the full Standard workflow (for Problem Analysers, tickets, or more complex exploration), use Switch to standard comparison in the overflow menu (⋯, top right). Your comparison and selections will carry over, no need to start again. Please let us know in Chat what is missing, we’re continuously improve the Express deploy workflow.

The bottom line

Most teams will use both. Standard Compare and deploy (and Pipelines) will continue to handle the majority of your work larger deploys, structured releases, and anything requiring safety nets or non-Sales Cloud metadata. Express Deploy is the fast lane for the smaller, frequent deploys in between: a quick hotfix, a small config change, or a metadata type you know you've just updated.


Express Deploy is in open pilot available to all Compare and deploy users at no extra cost. For more detail see What is Express Deploy? Feedback welcome via in-app chat.

Did this answer your question?