---
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


---

# Migrating a blueprint from test to production

# Migrating a blueprint from test to production {#ariaid-title1}

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

You can migrate a blueprint from a test environment to a production environment by using the Matrix Loader or by automating the migration using REST API calls.

CPQ Administrators have two ways to migrate a blueprint from test to production migration: by using the Matrix Loader, and by using REST API automation.

* Matrix Loader migration: From CPQ Admin, an admin can export a blueprint or blueprints to a ZIP file. The admin can then import these artifacts into the production environment. A new configurable product must be created and associated with the blueprint in the production environment. This can be done afterward or by creating the product and editing the blueprint yaml file with the new SFDC product2 id, product code, or partner id before deployment.
* REST API automation: Robust REST API capabilities let implementers and customers automate test-to-production migration in a CI/CD process.
{#how_can_i_accomplish_test-to-production_migration__ul_zbq_fpw_2hc}
**Zugehörige Konzepte**   

* [Testing in non-production environments before migration](https://servicenow-prod.fluidtopics.net/qm4RCohBRYftPKDJZ~seYw "Test configurators in a non-production environment before migrating them to production. The configurators support revenue-critical processes, validate all changes outside production and promote them using controlled environment-to-environment migrations.")