Compare and deploy
See every difference. Deploy only what you select.
Metacaliper retrieves the metadata from both sides, lists each component that differs, and shows the change line by line. You pick the components, validate them against the target, and deploy.
Comparisons are on every plan, Free included. Deployments start on Solo.
Compare any two sources
A comparison has four steps: Select components, Retrieve, Differences and Review. Each one is saved, so you can leave and come back to the step you left.
- Environment to environment: production, sandbox, scratch and Developer Edition orgs.
- A git branch to an environment, or an environment to a repository.
- Two snapshots of an environment, or a snapshot and the environment as it is now.
- Each component is marked Added, Changed or Only in target.
Review and merge, line by line
Source and target sit side by side. Copy a single change across, or edit the result yourself before you deploy it.
- Profiles and permission sets open in a grid of their entries, not as raw XML.
- A merge is marked out of date when the target changes after it.
- Missing component suggestions name what a selection depends on (Business and above).
Validate, then deploy
- Validate only is on by default: the first run changes nothing in the target.
- A validation that passed can be deployed for 10 days, as a Salesforce quick deploy when tests ran.
- Test levels: no tests, specified tests, local tests or all tests (Solo and above). Production defaults to local tests.
- A deployment to Production asks for the environment's name before it starts.
- If the target changed since the comparison, the deployment stops and says what changed.
Delete and roll back
- Deletions check what still uses each component before anything is removed.
- Before each deployment, a snapshot of the components it changes is stored.
- A deployment or deletion can be rolled back, validated first, and the rollback undone (Team and above).
- Every validation, deployment, deletion and rollback keeps its own record.
Step-by-step help: Compare two environments,Missing component suggestions,Deploy from a comparison, Roll back a deployment.
Questions about comparing and deploying
What can Metacaliper compare?
Two environments (a production org, a sandbox, a scratch org or a Developer Edition org), a git branch and an environment, an environment and a repository, and two snapshots of the same environment.
How does a deployment from a comparison work?
You select the components to deploy on the Review step. Validate only is on by default, so the first run checks the deployment without changing the target. A successful validation can then be deployed for 10 days without running the tests again.
What happens if the target changed after the comparison?
The deployment stops and lists the components that changed in the target since the comparison. You can compare again, or deploy anyway.
Can Metacaliper delete metadata?
Yes. You select the components to delete, Metacaliper checks what still uses them, and you validate or run the deletion. A comparison can also delete components that exist only in the target.
Compare your first two environments today
Every new workspace has the Team plan for 14 days, without a card. Then the Free plan keeps comparing two environments, with no time limit, until the team starts a paid plan.