---
schema_version: "1"
id: 8a58880e68ebc8b2ae78375ed820200a6a08a325b20b98c9ed7fdb3d6e5e9385
title: Considerations for Migrating Calculation Matrices and Procedures
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/considerations_migrating_calc_matrix_calc_procd.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.considerations_migrating_calc_matrix_calc_procd.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 366278536e9d14b917bdfdd664d743ae89b8956c7a58ef52d0ead11667d5fb36
description: Before you migrate your calculation matrices and calculation procedures as decision matrices and expression sets respectively, review these migration recommendations and the post-migration behavior of these components.
products:
  - Industry Solutions
  - Cross Cloud
release: "264"
---
# Considerations for Migrating Calculation Matrices and Procedures

Before you migrate your calculation matrices and calculation procedures as decision matrices and expression sets respectively, review these migration recommendations and the post-migration behavior of these components.

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

## Migration Recommendations

- If a calculation matrix is used in a calculation procedure, avoid changing the matrix name and the matrix column names. Modifying a matrix that’s referenced in a calculation procedure results in a variable name mismatch between the matrix and the procedure.
- Ensure that you don’t change the matrix column data types when the matrix is referenced in a calculation procedure.
- Ensure that the matrix’s column names don’t have spaces and special characters.
- Ensure that the variable names in the calculation procedure don’t have spaces and special characters.
- Migrate calculation procedures and matrices as expression sets and decision matrices respectively to a sandbox environment first. If everything works as expected, deploy the expression sets and decision matrices from the sandbox environment to the production environment.
- If a calculation procedure references a calculation matrix, first migrate the calculation matrix. For more information, see [Migration Scenarios and Workflow](https://help.salesforce.com/s/articleView?id=ind.migration_scenarios_and_workflow.htm&release=264.0.0&type=5 "Let’s look at a few scenarios for migrating calculation matrices as decision matrices and calculation procedures as expression sets. Let’s also review the migration workflow for various states of the calculation matrices and calculation procedures.").

## Post-Migration Behavior

- The migrated expression set and decision matrix versions are inactive.
- When a calculation procedure from a managed package is migrated as an expression set, the expression set is an unmanaged component.
- When a calculation matrix from a managed package is migrated as a decision matrix, the decision matrix is an unmanaged component.
- The calculation procedures and calculation matrices in the managed packages remain unchanged.