--- sourceDocument: Australia Sales Customer Relationship Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/order-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia Sales Customer Relationship Management ft:clusterId : - omgmt bundleId : - omgmt workflow : - Customer and Industry --- # Migrate a blueprint between environments # Migrate a blueprint between environments {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Move blueprints between ServiceNow CPQ environments to maintain consistent configuration management. Export, update, and import blueprint packages using the Matrix Loader to promote tested configurations from development to production. ## Before you begin Review ServiceNow CPQ upgrade windows, described in [ServiceNow CPQ Upgrade Schedule](https://www.servicenow.com/docs/io8YrNExZ2xV4rSwkeBLiA "ServiceNow 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, contact your customer Support team. Role required: admin ## About this task Understand the following terms: * 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. {#cpq-migrating-env-to-env__ul_g3l_v2h_2jc} ## Procedure 1. Export the blueprint from the source environment. 1. In the source environment, select the blueprint to move. 2. Select Export. The first notification indicates that the export process has started. After the export completes, a second notification indicates that the blueprint is ready for download. Watch for notifications on the bell icon in the lower-left corner. 3. In the bell icon menu, select the Download link. 4. Save the blueprint to your local machine or a central repository such as Git. If your environment is integrated with Salesforce and you are migrating the blueprint for the first time, verify the prerequisites. Then perform step 1 in [Migrate a blueprint to an SFDC-integrated destination](https://www.servicenow.com/docs/UNq868sWH1aia4BLhWFHeQ "Migrate a CPQ blueprint to a Salesforce-integrated ServiceNow CPQ environment. Recreate configurable products, update Product2 IDs, and verify connections for accurate data mapping and integration between Salesforce and ServiceNow 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 with an earlier version, add the following line to the bottom of the file to avoid conflicts: 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://www.servicenow.com/docs/eLn2CRu8kbAK52rjoJdQBg "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."). 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://www.servicenow.com/docs/UNq868sWH1aia4BLhWFHeQ "Migrate a CPQ blueprint to a Salesforce-integrated ServiceNow CPQ environment. Recreate configurable products, update Product2 IDs, and verify connections for accurate data mapping and integration between Salesforce and ServiceNow CPQ."). 3. 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 to a new ZIP file. Include blueprint.yaml, the blueprints folder, the fields folder, the rules folder, and any other artifacts from the migration package. Do not include the parent folder. Warning: When compressing, select only the contents of the unzipped blueprint export, not the parent folder itself. If the parent folder is selected, you receive an error when uploading to the ServiceNow CPQ Admin. 4. Migrate components related to the blueprint to the production tenant. For example, migrate managed tables and external connections used by the blueprint. 5. Import the blueprint to the destination environment. 1. Log in to the administration area of the ServiceNow CPQ destination environment. 2. Open the Matrix Loader. 3. Drag the edited migration package ZIP file into the Matrix Loader drop area. 4. Select Next, then select 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://www.servicenow.com/docs/UNq868sWH1aia4BLhWFHeQ "Migrate a CPQ blueprint to a Salesforce-integrated ServiceNow CPQ environment. Recreate configurable products, update Product2 IDs, and verify connections for accurate data mapping and integration between Salesforce and ServiceNow CPQ."). 2. Review your migrated blueprint from the end-user UI in the destination ServiceNow CPQ environment. {#cpq-migrating-env-to-env__substeps_ajr_3t2_rgc} {#cpq-migrating-env-to-env__steps_uqd_gdh_2jc} **Related concepts** * [ServiceNow CPQ Upgrade Schedule](https://www.servicenow.com/docs/io8YrNExZ2xV4rSwkeBLiA "ServiceNow 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.") **Related tasks** * [Migrate a blueprint to an SFDC-integrated destination](https://www.servicenow.com/docs/UNq868sWH1aia4BLhWFHeQ "Migrate a CPQ blueprint to a Salesforce-integrated ServiceNow CPQ environment. Recreate configurable products, update Product2 IDs, and verify connections for accurate data mapping and integration between Salesforce and ServiceNow CPQ.")