When you use our CPQ add-on solution, you may notice that the filter for CPQ config data objects doesn't include SSBQ__ContractedPrice__c object.

This is an expected behaviour.
​
​SSBQ__ContractedPrice__c (Contracted Pricing) is treated as transactional data, which is data that gets created when using the system. For example, when a Sales rep makes a sale. This type of data requires an Account to already exist.

Because our CPQ solution is designed to retrieve and deploy specifically CPQ config data, which in other words is metadata that's being stored as data (this type of data would be created by developers).

Therefore, it isn't possible to use our 'Compare and deploy' feature to retrieve and deploy these data records.

But you'd still be able to retrieve SSBQ__ContractedPrice__c Custom object metadata in the comparison and deploy it between environments:

The main thing that determines if we support data of CPQ objects is whether or not they're created during a transaction with a customer, or created to configure the system.

If they're created as system config data, 'Compare and deploy' will support its retrieval and deployment.

However, it's important to note the answer may not always be as straightforward when it comes to objects in CPQ where there's a mix of transaction and configuration data stored i them.

You can use Gearset's other add on called Sandbox seeding to migrate data records of SSBQ__ContractedPrice__c object.
​
Find out more about the Sandbox seeding solution in our documentation collection:
​Gearset for data sandbox seeding