Treat an upgrade as a change to an operating service
Fortra migration and upgrades is an MMC service enquiry for moving an existing deployment to a supported target state. The first task is to establish the source version, current configuration and manufacturer-supported path. Do not assume a direct upgrade is available simply because both versions share a product name.
Inventory policies, integrations, retained data, licences and dependent platforms. Identify what must be preserved and what can be retired. Confirm prerequisites and any intermediate steps with current documentation. A migration across hosting models may require different identity, network and data-handling decisions from an in-place software update.
Rehearse cutover and a realistic recovery decision
A controlled trial should validate configuration conversion, representative data and the integrations the service depends on. Agree backups, the maintenance window and a rollback decision before production work. Recovery may become more complicated after live data is written in the new environment, so identify that boundary explicitly.
Handover should document target settings, migration evidence, outstanding differences and the support route. UAE access approvals and business deadlines should shape the schedule. MMC can scope the agreed migration and tests; application redesign, indefinite parallel operation and unrelated platform remediation should be separate items rather than hidden assumptions.
Evidence to request for this scope
- Obtain the supported source-to-target path and verify backups or exports before cutover.
- Rehearse representative policy, data and integration behaviour on the target configuration.
- Define rollback triggers, the last straightforward recovery point and customer acceptance roles.