---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Migrate data from Release Management v2 to Digital Product Release

# Migrate data from Release Management v2 to Digital Product Release {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
If you have the Release Management v2 (RM v2) application installed, you can migrate your data from RM v2 to Digital Product Release.

## Before you begin

Role required: admin

To provide access to additional roles, you can add comma-separated values of other roles installed with DPR in the system property sn_dpr_model.rmv2.migration_roles. For more information, see [Digital Product Release properties](https://servicenow-prod.fluidtopics.net/HMls1U1Ze5_88wJH6Giesg "Configure the system properties to customize various features of Digital Product Release according to your organization's needs.").

## About this task

The migration utility performs the following tasks:

* Migrate RM v2 product to Digital product: Copies data from rm_product into newly created Application Product Models.
* Create Release Template from RM v2 Release: Creates a DPR Release Template by leveraging the Phases and Tasks from an existing RM v2 Release record.
{#dpr-rmv2-product-migration__ul_kgz_22y_dcc}

For more information about migrating data from Release Management V2 to Digital Product Release, see the [RMV2 Product Migration \[KB1644412\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1644412) article in the Now Support Knowledge Base.

## Procedure

1. Define your custom field mappings as needed.
2. Add any additional post-processing instructions after the creation of the cmdb_application_product_model record.
3. Perform the migration either from the rm_product list view or running the migration script from the sn_dpr_model app scope.
{#dpr-rmv2-product-migration__steps_tlf_b41_ccc}