1. What this document is for

This document is the entry point for the MC Upgrade documentation set.

Use it to understand the upgrade flow and choose the right detailed document for each phase.

2. Upgrade flow and document parts

Use the following documents in order:

1. Part 1 – Prerequisites and readiness
   • Confirm system requirements, access, backups, SQL connectivity, and required values.
2. Part 2 – Execute MC Upgrade
   • Run DPInstaller.exe, gather variables, validate inputs, and deploy.
3. Part 3 – Post-upgrade validation and troubleshooting
   • Validate application/services and collect logs if any step fails.

3. When to use each part

• Use Part 1 before opening the installer.
• Use Part 2 during the upgrade execution window.
• Use Part 3 immediately after deployment completes, or during incident handling.

4. Scope and guardrails

This document set is for upgrading an existing on-prem MC environment.

It does not cover:

• New greenfield MC installation design.
• SaaS migration licensing workflow.
• Custom package engineering changes.

5. Quick handoff checklist

Before handoff to testers or business users, confirm:

• Part 1 readiness items are complete.
• Part 2 deployment completed without failed steps.
• Part 3 validation checks passed.
• Logs are archived for change record.

Once all boxes are checked, the environment is ready for functional and user acceptance testing.