The Gearset External ID acts as a unique identifier. Much like a unique API name allows Gearset to track a metadata component across environments, the External ID

allows Gearset to recognize the same record as it moves through your orgs, even though the underlying Salesforce Record ID changes upon insertion into a new org.

External IDs falling out of sync isn't unheard of, it can happen for a few reasons although most common is the same record being created in more than one environment, or being moved using a non Gearset tool.

Gearset derives the External ID from the Salesforce Record ID, the same record created in two different orgs (by hand or by a non-Gearset deployment) will have a different Salesforce Record ID, and therefore different Gearset IDs.

If your comparison looks like this, you may have out of sync External IDs.

Before you begin, start by deciding which of your orgs is the "source of truth" for your IDs. Syncing the IDs requires one orgs IDs to be overwritten by the other, so choose one of your orgs as the source. This would typically be the org in which you create your RCA configuration.

Once you're ready to start, you can navigate to the Salesforce org page and click on Run external Id set up under your RCA org to open the External ID setup wizard.

Then select on the third option to Align RCA IDs between orgs:

Select your source org and target org and click on Align external IDs at the bottom:

You'll then see that Gearset will start to generate a deployment to align the External IDs:

And once the page finishes loading you'll be given the option to Disable rules and automations. If needed you click on Deactivate or if not you can Skip this step:

When you're ready to proceed, Gearset will then show you a summary of the records that will be updated in the target org. Once you've checked that everything looks as expected, you can click on Deploy data to start the data deployment.

Once your data deployment is completed you'll be able to also find it in the Data deployment history tab.