Gearset's data loader can deploy custom settings as well as custom objects.
Before you deploy custom settings data, you'll need to make sure the metadata is the same in the source and target orgs.
Deploying list custom settings
We have a Support Tier list custom setting with two fields.
Within that custom setting, we have 3 records.
To deploy these records with Gearset's data loader, we select SupportTier__c from the list of objects and click NEXT.
We don't need to include any related objects because the custom setting doesn't reference any other objects, so we can continue through the configuration. In this case, we don't want data masking, so we'll leave it turned off.
We go ahead with the deployment which creates the 3 records.
Salesforce recommends you use custom metadata types instead of list custom settings, because the data can then be migrated as a metadata deployment.
Deploying hierarchy custom settings
We have an Authorized Discount Level hierarchy custom setting with one field.
Within that custom setting, we have 3 records on Profile and 1 record on User, and the organization default.
To deploy these records with Gearset's data loader, we select AuthorizedDiscountLevel__c from the list of objects and click NEXT.
We include Organization, Profile and User in the deployment with the deployment method set to Reference existing records and continue through the configuration. In this case, we're don't want data masking, so we'll leave it turned off.
We go ahead with the deployment, which creates the 5 records.
