Practical guide
The 7R modernization decisions
Use VERTEX's explicit Retain, Rehost, Replatform, Refactor, Rearchitect, Replace and Retire vocabulary.
Page purpose
Use The 7R modernization decisions to resolve a specific decision, not as a generic information list.
This guide uses VERTEX's defined vocabulary: Retain, Rehost, Replatform, Refactor, Rearchitect, Replace, and Retire. It is one working taxonomy, not a claim that the industry has one universal 7R standard; other organizations use different labels, counts, and meanings.
An R label is a decision summary, not the analysis itself. Apply it at an explicit level—whole system, component, data store, interface, or capability—and record conditions, evidence, trade-offs, and the expected next review.
Decision trap
The ambiguity this guide is designed to remove.
- Teams use the same R label for materially different changes.
- One disposition is assigned to an application that needs several component-level decisions.
- Labels are selected from preference rather than operating and technical evidence.
- Temporary rehosting is recorded as if it completed modernization.
Comparison criteria
Comparison criteria that should be recorded.
- What exact asset or capability does the disposition cover?
- Which constraints eliminate or condition otherwise feasible options?
- Is the selected R a destination, an interim transition, or a risk-containment action?
- What event or date requires the decision to be reviewed?
Apply the framework
Apply the framework to a real situation.
- Agree the local meanings of all seven labels before classifying anything.
- Choose the decision level and separate mixed dispositions within a system.
- Collect lifecycle, dependency, cost, change, data, control, and service evidence.
- Compare feasible options and document why alternatives were rejected.
- Record transition conditions and revisit the label when its assumptions change.
Reader output
The output the reader should produce.
- Portfolio-specific 7R definition sheet
- Decision criteria and evidence checklist
- System and component disposition register
- Option comparison with constraints and trade-offs
- Decision expiry, dependency, and review-trigger log
Decision clarity
A clearer decision, not merely more information.
- A shared project vocabulary with definitions documented for the specific portfolio.
- Disposition decisions made at an explicit and useful level.
- Conditions, trade-offs, and evidence attached to every label.
- Review triggers that prevent temporary decisions from becoming invisible permanence.
Misapplication
When can the framework create false confidence?
- Treating this seven-label vocabulary as a universal external standard.
- Using labels to create portfolio certainty unsupported by evidence.
- Underestimating data, integration, testing, and operating work in a rehost or replatform.
- Allowing retain to mean indefinite inaction without lifecycle review.
Decision questions
Test the interpretation before applying the guide.
Is there one universally accepted 7R model?
Industry lists vary in count, labels, and definitions. This guide states its vocabulary explicitly so participants can make consistent decisions within the engagement.
Can one application have more than one R?
Yes. A stable core might be retained while an interface is refactored, a runtime replatformed, and an obsolete module retired.
Is rehosting considered modernization?
It may be a useful migration or risk-containment step, but it does not by itself change application architecture, data quality, delivery practice, or operating ownership.