---
sourceDocument: Australia Sales and Order Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/order-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Sales and Order Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Migrate a blueprint from environment to environment

# Migrate a blueprint from environment to environment {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 Minuten Lesedauer

Migrate blueprints between CPQ environments to ensure consistent configuration management. Export, update, and import blueprint packages safely using the Matrix Loader to promote tested configurations from development to
production.

## Vorbereitungen

Understand CPQ upgrade windows, described in [CPQ Upgrade Schedule](https://servicenow-prod.fluidtopics.net/2Ml5BMYmj2WB0591ILiWHw "CPQ updates customer environments on a predictable bi-weekly schedule to deliver new features, enhancements, and fixes. Test environments are upgraded first, with production updates following after at least 14 days to ensure stability. You can identify your environment’s sector from its URL and refer to the Upgrade Calendar to see which version your instance is currently running."). Schedule your migration to avoid published upgrade windows. If you have questions regarding this topic, reach out to your Customer Success Manager.

The following terms are used in this task:

Source
:   The environment from which functionality is migrated.

Destination
:   The environment to which functionality is migrated.

Migration package
:   The file or files exported from the source environment to be imported to the destination environment.

This task assumes that migration is performed on one or more blueprints at a time.

Role required: (unknown)

## Prozedur

1. Export the blueprint from the source.
   1. In the source environment, select the blueprint you want to move by clicking the check box next to its name.
   2. Click Export.  
      Watch for notifications on the bell icon located in the lower-left corner. The first notification indicates that the export process has started. After the export is complete, a second notification indicates that the blueprint is ready for download.
   3. To download the blueprint, click the Download link in the bell icon menu.
   4. Save the blueprint to your local machine or a central repository such as Git.
   5. If your environment is integrated with Salesforce and you are migrating the blueprint for the first time, confirm the prerequisites and perform step 1 in [Migrate a blueprint to an SFDC-integrated destination](https://servicenow-prod.fluidtopics.net/getNFuobzGBkiEhqtYEBbQ "Learn how to migrate a CPQ blueprint to a Salesforce-integrated CPQ environment. Recreate configurable products, update Product2 IDs, and verify connections to ensure accurate data mapping and seamless integration between Salesforce and CPQ.").
   {#cpq-migrating-env-to-env__substeps_s4x_4q2_rgc}
2. Modify the migration package.
   1. Unzip the blueprint ZIP file you downloaded in step 1.  
      The file unzips to a blueprint.yaml file.

   2. Open the blueprint.yaml file in a text editor.  
      When migrating a blueprint to a destination in which an earlier version of the blueprint resides, we recommend adding the following line to the bottom of the file:

          fullBlueprintMigration: true

      Sample edited blueprint.yaml file:

          ---
          blueprints:
          - variableName: someBlueprint
            related Fields:
            - field1
            - field2
            - field3
            lastModifiedBy: dev5@dev.logik.io
            name: someBlueprintName
            description: BP description goes here
            relatedSets: null
            scripts: null
            layouts: null
            products: null
          productPickers: /fields/productPickers.yaml
          sets: null
          fieldOptions: /fields/fieldOptions.csv
          rules: /rules/rules.csv
          fields: /fields/fields.csv
          fullBlueprintMigration: true

      For a description of how this parameter affects the blueprint migration, see [The fullBlueprintMigration parameter](https://servicenow-prod.fluidtopics.net/Lm3mQr_0x8Li402vU3wJAw "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.").
   3. If your environment is integrated with Salesforce and you are migrating the blueprint for the first time, perform step 2 in [Migrate a blueprint to an SFDC-integrated destination](https://servicenow-prod.fluidtopics.net/getNFuobzGBkiEhqtYEBbQ "Learn how to migrate a CPQ blueprint to a Salesforce-integrated CPQ environment. Recreate configurable products, update Product2 IDs, and verify connections to ensure accurate data mapping and seamless integration between Salesforce and CPQ.").
   4. Save your edits and close the blueprint.yaml file.
   {#cpq-migrating-env-to-env__substeps_ohq_mr2_rgc}
3. Compress all components of the migration package (including blueprint.yaml, the blueprints folder, the fields folder, the rules folder, and any other artifacts that may have been present in the migration package, but not the parent folder) to a new ZIP file.  
   Wichtig:  
   When compressing, make sure to select only the contents of the unzipped blueprint export, and not the parent folder itself. If the parent folder is selected, you will receive an error when you upload it to the CPQ Admin.


4. Migrate components related to the blueprint you are migrating (for example, managed tables and external connections used by the blueprint) to the production tenant.
5. Import the blueprint to the destination.
   1. Log into the administration area of the CPQ destination environment.
   2. Open the Matrix Loader.
   3. Drag the edited migration package ZIP file into the Matrix Loader drop area.
   4. Click Next, and then click Import.

   {#cpq-migrating-env-to-env__substeps_hvy_1t2_rgc}  
   If you encounter errors after the import, follow the on-screen instructions to review the error logs.
6. Test the migration.
   1. If your environment is integrated with Salesforce and you are migrating the blueprint for the first time, perform steps 3 and 4 in [Migrate a blueprint to an SFDC-integrated destination](https://servicenow-prod.fluidtopics.net/getNFuobzGBkiEhqtYEBbQ "Learn how to migrate a CPQ blueprint to a Salesforce-integrated CPQ environment. Recreate configurable products, update Product2 IDs, and verify connections to ensure accurate data mapping and seamless integration between Salesforce and CPQ.").
   2. Review your migrated blueprint from the end-user UI in the destination CPQ environment.
   {#cpq-migrating-env-to-env__substeps_ajr_3t2_rgc}
**Zugehörige Konzepte**   

* [CPQ Upgrade Schedule](https://servicenow-prod.fluidtopics.net/2Ml5BMYmj2WB0591ILiWHw "CPQ updates customer environments on a predictable bi-weekly schedule to deliver new features, enhancements, and fixes. Test environments are upgraded first, with production updates following after at least 14 days to ensure stability. You can identify your environment’s sector from its URL and refer to the Upgrade Calendar to see which version your instance is currently running.")  
**Zugehörige Tasks**   

* [Migrate a blueprint to an SFDC-integrated destination](https://servicenow-prod.fluidtopics.net/getNFuobzGBkiEhqtYEBbQ "Learn how to migrate a CPQ blueprint to a Salesforce-integrated CPQ environment. Recreate configurable products, update Product2 IDs, and verify connections to ensure accurate data mapping and seamless integration between Salesforce and CPQ.")