---
schema_version: "1"
id: 1c9fbf46356172542b18550eea78b99c5958ae2f5c039f5491f610582b5613d1
title: Decision Matrix Migration Considerations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/decision_matrix_migration_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.decision_matrix_migration_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 2447e959cb087db2aa7aa571029e88624d1a2d369f14fde754dda9911c3423ed
description: Here are a few typical migration scenarios and recommendations on how to maintain decision matrices in your target org for a successful migration.
products:
  - Industry Solutions
  - Cross Cloud
release: "264"
---
# Decision Matrix Migration Considerations

Here are a few typical migration scenarios and recommendations on how to maintain decision matrices in your target org for a successful migration.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions for clouds that have Business Rules Engine enabled</td></tr></tbody></table>

The result of decision matrix migration depends on whether the decision matrix and its versions exist in the target org and on the status of such versions.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-business_rules_engine-264-0-0-production-enus/b2d6dd5c-c231-428b-abbf-3dd2cd51a11f/images/icon_note.png)

Note

When you migrate a decision matrix version, only the column headers of the version migrate to the target org. Row data isn’t migrated.

Before you migrate a decision matrix version, specify a rank and activate the version in the source org. Then, migrate the version or the entire decision matrix to the target org. The migrated decision matrix version is invoked in the target org based on the specified rank. Migration fails if the target org already contains a decision matrix version of the specified rank.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:33.33333333333333%">
          <col style="width:33.33333333333333%">
          <col style="width:33.33333333333333%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d33573e89">Decision Matrix Configuration</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d33573e92">Migration Behavior</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d33573e95">Migration Recommendations</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Decision Matrix Configuration" class="slds-cell-wrap" style="vertical-align:top;" headers="d33573e89 ">The target org doesn’t have the decision matrix.</td>

            <td data-label="Migration Behavior" class="slds-cell-wrap" style="vertical-align:top;" headers="d33573e92 ">The decision matrix and its versions migrate successfully.</td>

            <td data-label="Migration Recommendations" class="slds-cell-wrap" style="vertical-align:top;" headers="d33573e95 "><a name="decision_matrix_migration_considerations__ul_psp_brh_2fc"><!-- --></a>
              <ul id="decision_matrix_migration_considerations__ul_psp_brh_2fc">
                <li>Deploy the decision matrix in the target org.</li>

                <li>Migrate the decision matrix versions independently.</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Decision Matrix Configuration" class="slds-cell-wrap" style="vertical-align:top;" headers="d33573e89 ">The target org has the decision matrix with one or more versions, where some or all
              the versions are active.</td>

            <td data-label="Migration Behavior" class="slds-cell-wrap" style="vertical-align:top;" headers="d33573e92 ">The migration fails.</td>

            <td data-label="Migration Recommendations" class="slds-cell-wrap" style="vertical-align:top;" headers="d33573e95 ">Deactivate active decision matrix versions in the target org and then try
              again.</td>

          </tr>
          <tr class="">
            <td data-label="Decision Matrix Configuration" class="slds-cell-wrap" style="vertical-align:top;" headers="d33573e89 ">The target org has the decision matrix but all matrix versions are inactive.</td>

            <td data-label="Migration Behavior" class="slds-cell-wrap" style="vertical-align:top;" headers="d33573e92 ">The decision matrix migrates successfully and all the versions from the source org
              replace the versions in the target org.</td>

            <td data-label="Migration Recommendations" class="slds-cell-wrap" rowspan="2" style="vertical-align:top;" headers="d33573e95 ">
              <p>Migrate individual decision matrix versions separately, rather than
                migrating an entire decision matrix with its versions together. </p>
              <p style="margin-bottom:0;">This approach gives you
                more flexibility to evaluate what a decision matrix version contains and change your
                migration approach accordingly.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Decision Matrix Configuration" class="slds-cell-wrap" style="vertical-align:top;" headers="d33573e89 ">The target org has the decision matrix with only a subset of the versions from the
              source org, and all the versions are inactive.</td>

            <td data-label="Migration Behavior" class="slds-cell-wrap" style="vertical-align:top;" headers="d33573e92 ">
              <ul>
                <li>The decision matrix migrates successfully and all the versions from the source org
                  replace the inactive versions in the target org.</li>

                <li>The versions that didn’t exist in the target org are added to the target org under the
                  parent decision matrix.</li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>

## Scenario 2: Migrate a Decision Matrix Version

Here, you’re migrating a decision matrix version independently, and not the entire decision matrix to which the version belongs.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-business_rules_engine-264-0-0-production-enus/b2d6dd5c-c231-428b-abbf-3dd2cd51a11f/images/icon_note.png)

Note

When you migrate a decision matrix version, only the column headers of the version migrate to the target org. Row data isn’t migrated.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:33.33333333333333%">
          <col style="width:33.33333333333333%">
          <col style="width:33.33333333333333%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d33573e199">Decision Matrix Configuration</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d33573e202">Migration Behavior</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d33573e205">Migration Recommendations</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Decision Matrix Configuration" class="slds-cell-wrap" style="vertical-align:top;" headers="d33573e199 ">The target org has the same decision matrix version in active state.</td>

            <td data-label="Migration Behavior" class="slds-cell-wrap" style="vertical-align:top;" headers="d33573e202 ">The migration fails.</td>

            <td data-label="Migration Recommendations" class="slds-cell-wrap" style="vertical-align:top;" headers="d33573e205 ">
              <p>Deactivate the decision matrix version in the target org and then try again.</p>
              <p style="margin-bottom:0;">The
                migrated decision matrix version from the source org overwrites the inactive decision
                matrix version in the target org.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Decision Matrix Configuration" class="slds-cell-wrap" style="vertical-align:top;" headers="d33573e199 ">The target org the same decision matrix version, but in inactive state.</td>

            <td data-label="Migration Behavior" class="slds-cell-wrap" style="vertical-align:top;" headers="d33573e202 ">The version from the source org migrates successfully and overwrites the inactive
              version in the target org.</td>

            <td data-label="Migration Recommendations" class="slds-cell-wrap" style="vertical-align:top;" headers="d33573e205 ">We recommend this migration approach.</td>

          </tr>
          <tr class="">
            <td data-label="Decision Matrix Configuration" class="slds-cell-wrap" style="vertical-align:top;" headers="d33573e199 ">The target org doesn’t have the decision matrix to which the version from the source
              org belongs.</td>

            <td data-label="Migration Behavior" class="slds-cell-wrap" style="vertical-align:top;" headers="d33573e202 ">The migration fails.</td>

            <td data-label="Migration Recommendations" class="slds-cell-wrap" style="vertical-align:top;" headers="d33573e205 ">Deploy the decision matrix in the target org and then migrate the version
              again.</td>

          </tr>
        </tbody>
      </table>