The fullBlueprintMigration parameter

  • Release version: Australia
  • Updated March 12, 2026
  • 1 minute to read

    • Learn the effects of enabling or disabling the fullBlueprintMigration parameter on sources in various configurations. The fullBlueprintMigration parameter controls how thoroughly a blueprint is updated during migration.

    The fullBlueprintMigration parameter

    When migrating an edited blueprint from a source environment to a destination environment where an earlier version of the same blueprint exists, fullBlueprintMigration: true instructs the destination environment to perform the migration more aggressively than it otherwise would. In the matrix below, common scenarios performed on the source environment blueprint are noted in the first column. The destination environment performs the corresponding migration task according to the true or false setting of fullBlueprintMigration, corresponding to the rightmost columns.

    Table 1. Effects of the fullBlueprintMigration parameterThe effect of the fullBlueprintMigration parameter when set to true or false
    Activity on source before migration Parameter = false Parameter = true
    Picklist option deleted Picklist option retained on destination Picklist option deleted on destination
    Rule removed from blueprint [see Note below] The rule remains associated to blueprint on destination Rule removed from blueprint on destination
    Note:
    If the rule is not associated with any other blueprint on the destination, the rule is removed from the global rule list on the destination,
    Rule action removed from rule Rule Action retained on destination Rule Action deleted on destination
    Product is removed from ProductList on Simple Product Action Product remains in ProductList on destination Product is removed from ProductList on destination

    Notes

    CPQ administrators do not directly associate or remove rules to or from blueprints. Instead, a rule is associated with a blueprint only if all its referenced fields are associated with the blueprint. Therefore, the admin manipulates a rule's association with a blueprint by associating or removing (deassociating) its fields. A rule will be removed from a blueprint in several circumstances, including:

    • A field referenced by the rule is removed from the blueprint.
    • In the rule, the admin adds a reference to a field that is not associated with the blueprint.
    • A new rule action that references a field not associated with the blueprint, is added to the rule.
    • The rule condition is modified to include a reference to a field that is not associated with the blueprint.