What method is recommended to bring MST in sync with production when upgrading to a newer Epic version?

• A. Upgrade
• B. Use Data Courier and manual build to bring MST in sync with production
• C. Refresh
• D. Rebuild

Answer: (B)

Synchronizing the master system data (MST) during an Epic upgrade hinges on applying the exact set of production changes to the new version and building them in the correct order. MST holds foundational configuration and master data that Epic applications rely on, so any mismatch between environments can lead to inconsistent behavior, missing codes, or security/access discrepancies.

Using Data Courier to pull the MST changes from production ensures you capture the real, approved updates that are already in use. Following that with a manual build in the target environment guarantees those changes are applied correctly, with all dependencies and sequencing verified. This combination provides a controlled, auditable path to parity between production and the upgraded environment, reducing risk of post-upgrade issues.

Relying solely on an upgrade, a refresh, or a rebuild alone can leave MST out of sync or skip necessary steps. The Data Courier plus manual build approach is the reliable way to align MST with production after an Epic version upgrade.