Run a metadata comparison

Compare a Salesforce org with a Git branch, two orgs, or two branches in four guided steps, then manage your comparison jobs from the Comparisons list.

Overview

A comparison retrieves metadata from two sources and tells you, component by component, what matches and what has drifted. MetaLens360 supports three kinds:

Type	Use it to
Org vs Git Branch	Check whether an org matches what is in source control.
Org vs Org	Compare two Salesforce environments (e.g. SIT vs STAGE).
Git vs Git	Compare two Git branches (e.g. STAGE vs release branch).

Every comparison runs as a background job. You can leave the page and come back; results appear on the job's detail page when it finishes.

Before you start

Connect the orgs and repositories you want to compare. See Connect a Salesforce org and Connect a Git repository.
Expect the first retrieval from an org to take a while. As the wizard says: "First-time retrieval fetches from Salesforce and takes 5–15 min. Subsequent comparisons within 4 hours are served instantly from local cache."

Steps

Open Drift Detection → Comparisons and click New Comparison (or use the button on Drift Overview).
On Comparison Type, optionally enter a Comparison Name (optional). If you leave it blank, MetaLens360 names the job after the comparison type and today's date.
Pick Org vs Git Branch, Org vs Org or Git vs Git, then click Next.
On Configure Sources, choose the Source and Target:
- For an org, click its card. If you have orgs in more than one Salesforce cloud, use the cloud filter chips (for example All Clouds) to narrow the list.
- For Git, click the repository card, then pick a branch. Type part of a branch name to filter long lists. Use the refresh icon (Refresh branch list from GitHub) if a new branch is missing.
Click Next. The button stays disabled until both sides are complete.
On Metadata Types, choose what to compare. Start with a preset — All Types, Code Only, Automation, Data Schema or Access — and click individual type chips to fine-tune. Each group also has select all / deselect all.
Click Next, check the summary on Review & Run, and click Run Comparison.

MetaLens360 opens the comparison's detail page, where you can watch progress.

Manage your comparisons

The Comparisons list shows every job with Name, Type, Status (Completed, Running, Queued, Failed or Cancelled), Drift, Duration and Started. Drift is shown as "{n}% drift": red above 20%, amber above 5%, green otherwise. The list refreshes every 10 seconds.

Click a row, or the View details icon, to open a job.
Click the Delete icon to remove one job, or tick several rows and click Delete {n} in the bar that appears. Deletion asks for confirmation and cannot be undone.

Example

Priya wants to know whether acme-uat matches the release/2026-11 branch of acme/salesforce-core. She chooses Org vs Git Branch, picks acme-uat as Source and the release branch as Target, applies the Automation preset, and clicks Run Comparison. Twelve minutes later the job is Completed with "3% drift".

FAQs

Can I compare orgs in different Salesforce clouds?

Yes. The cloud chips only filter the cards; you can choose any connected org on either side.

Should I select fewer metadata types?

Fewer types finish faster and give a more focused result. Use All Types for a full health check and a preset when you are investigating one area.

Why was my second comparison so fast?

Org metadata retrieved within the last 4 hours is reused from the local cache.

Troubleshooting

"Failed to create comparison. Check your connections."

The job could not be created. Open Connections and test both sides — an expired org session or Git token is the usual cause. See Fix expired org credentials.

"No branches cached. Click refresh to fetch from GitHub."

MetaLens360 has not loaded this repository's branches yet. Click Fetch. If it fails, see Fix Git repository access.

The Next button stays disabled on Configure Sources

Both Source and Target need an org selected, or a repository and a branch selected.