Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
The 7R strategy helps technology leaders choose a distinct path for each application: retire it, retain it, move it, replace it, or invest in deeper change. The right answer is not always a rewrite—or even a move to the cloud. Treat the 7Rs as a portfolio decision framework, then weigh business value, technical condition, dependencies, risk, cost, and the organization’s ability to run the result.
What the 7R strategy is—and what it is not
The 7Rs are a set of options for rationalizing applications during a cloud migration or modernization program. AWS uses seven strategies: retire, retain, rehost, relocate, repurchase, replatform, and refactor or re-architect. The framework is widely used, particularly in AWS-oriented planning, but it is not a universal standard with identical definitions everywhere. Microsoft’s Azure modernization guidance, for example, presents a six-R model that includes rebuild and omits relocate and repurchase as separate categories. See AWS’s migration-strategy definitions and Microsoft’s Azure App Modernization Guidance.
Migration means moving a workload to a different hosting environment. Modernization is broader: it can improve architecture, platform, delivery, security, operations, data practices, or user experience. Cloud migration may include modernization, but does not require it. Refactoring is one modernization technique, not a synonym for modernization.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteA rehost can be a sensible first step, especially when there is a data-center deadline, but moving an application unchanged does not make its architecture cloud-native. The 7Rs also are not a mandatory sequence: a workload might be retained, rehosted, and later retired, while another might move directly to SaaS or be refactored in increments.
#1 Best Overall
- MODEL P74439-005: Compact and affordable HPE ProLiant MicroServer Gen11 powered by Intel Pentium Gold G7400 3.7GHz processor, ideal for file sharing, NAS, and basic business workloads
- READY OUT OF THE BOX: Includes 16GB DDR5 UDIMM memory (expandable to 128GB), one 1TB SATA 6G Business Critical HDD, embedded Intel VROC SATA, dedicated iLO-M.2 port kit, 180w external power adapter and 1/1/1 warranty for dependable plug-and-play server operation
- WHISPER-QUIET & SPACE-SAVING: Ultra-compact mini tower design fits easily in small office spaces; supports wall, flat, or vertical placement for deployment flexibility
- INTEGRATED REMOTE MANAGEMENT: Comes with HPE iLO 6 and embedded TPM 2.0 for secure, license-free remote server administration through shared port access
- EXPANDABLE DESIGN: Two PCIe slots (including PCIe 5.0) and four LFF-NHP drive bays provide robust options for storage and component scalability. Features new MR408i-p controller support for enhanced storage performance
The seven strategies at a glance
| Strategy | What changes | Typical fit | Main trade-off |
|---|---|---|---|
| Retire | Decommission the application and its infrastructure, with appropriate handling of data and dependencies. | Unused, duplicate, obsolete, or low-value systems. | Removes cost and risk, but missed users, processes, or records can make shutdown disruptive. |
| Retain | No material change for now. | Hardware-bound, constrained, stable, or soon-to-be-replaced systems. | Avoids premature work, while leaving technical debt and support risks in place. |
| Rehost | Move the application to new infrastructure with minimal application changes. | Stable workloads, time-sensitive moves, or applications with low tolerance for code change. | Can be faster and less complex than redesign, but often carries existing inefficiency and fragility forward. |
| Relocate | Move infrastructure, often at the hypervisor or platform level, without materially changing the application. | Virtualized workloads where preserving much of the operating model matters. | Can simplify the transition, but application-level benefits may be limited and platform terms still need validation. |
| Repurchase | Replace the existing product with a different commercial product or SaaS service. | Commodity capabilities or costly custom systems without meaningful differentiation. | Reduces some ownership burden, but adds vendor, integration, subscription, and exit considerations. |
| Replatform | Move the application with limited changes to gain platform or operational benefits. | Workloads suited to a managed database, runtime, container platform, or PaaS with controlled changes. | Can improve operations without a rewrite, but scope can creep into one. |
| Refactor / re-architect | Substantially change code, architecture, data access, or operating model. | Strategic systems that need greater agility, resilience, scalability, or delivery speed. | Offers the greatest transformation potential, with the highest delivery demands and risk. |
AWS’s terminology describes rehost as “lift and shift,” relocate as a hypervisor-level move, replatform as “lift and reshape,” and refactor or re-architect as changing the architecture to use cloud capabilities. The distinctions are useful, but the implementation details depend on the workload and target environment. See AWS’s cloud-path descriptions.
Assess the application, not just the server
Assign a strategy to an application or meaningful workload boundary—not indiscriminately to a data center, business unit, or server. In some cases, the right unit is a component or capability: for instance, rehost an application server, replatform its database, retire a reporting module, and refactor a customer-facing API. AWS recommends portfolio discovery and rationalization before migration-wave planning; its detailed portfolio-discovery guidance describes the role of that work.
Build a decision record around evidence
- Business value: revenue contribution, customer or employee impact, strategic differentiation, process criticality, contractual or regulatory importance, and expected lifespan.
- Technical condition: support status for operating system, runtime, database, and middleware; architecture and maintainability; test coverage; release frequency; obsolete protocols or hardware dependencies; and available skills.
- Operations: availability and recovery objectives, peak behavior, batch windows, latency, data residency, observability, incidents, manual effort, backups, and disaster recovery.
- Economics: current infrastructure, license, and labor costs; migration and testing effort; expected target cost; data-transfer and network costs; SaaS and integration charges; dual-running costs; and the cost of delay or failure.
- Risk and compliance: data classification, identity and access, encryption, audit duties, vendor concentration, support commitments, and change constraints.
- Strategic fit and readiness: platform standards, product-delivery needs, elasticity or geographic plans, cloud operating model, replacement options, executive sponsorship, product ownership, skills, and funding.
Record the selected R, rejected alternatives, evidence, assumptions, target platform, one-time and recurring cost estimates, expected benefits, dependencies, security actions, complexity, rollback plan, accountable owner, planned wave, review date, and confidence. A 1-to-5 score for value, urgency, complexity, benefit, risk, cost pressure, dependency complexity, and readiness can help compare workloads, but it should support rather than replace judgment. Low confidence is a signal to improve discovery, not a reason to assign an arbitrary strategy.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesInventory and map dependencies
Capture the application owner, business capability, users and locations, production and nonproduction instances, hosting location, runtime, operating system, database, middleware, interfaces, data classification, service objectives, utilization, license terms, run cost, incident and change history, support status, and planned replacement date. Reconcile CMDB records with infrastructure discovery, identity and network data, billing, backups, repositories, and interviews; no single inventory source is likely to reveal everything.
Map databases, file shares, queues, batch schedulers, authentication, payments and ERP interfaces, mainframe links, DNS, certificates, network rules, reporting feeds, and manual procedures. A nominally simple move may be difficult because of a hidden batch dependency, obsolete database, or hardware appliance.
When each R fits
Retire: remove systems that no longer earn their keep
Retirement is often the best economic and risk decision when an application is unused, duplicated, obsolete, or has little business value. Confirm usage with logs, reports, scheduled jobs, downstream consumers, and business owners; investigate legal or audit retention needs; and identify any read-only archive or export requirement. Shutdown should include communication, dependency validation, access removal, and documentation—not just deleting infrastructure. AWS’s guidance on assessing applications for retirement emphasizes portfolio and dependency information.
Do not retire a system solely because usage appears low: a rare process may be critical. Preserve data that must remain available, and verify that replacements cover edge cases before decommissioning.
Retain: make a deliberate, time-bound exception
Retain when a physical dependency lacks a practical equivalent, regulation or latency favors the current location, a replacement is near, the business case is negative, or the organization lacks the evidence and capability to migrate safely. A stable, inexpensive system can be a rational exception.
Rank #2
- HIGH-EFFICIENCY SERVER FOR BUSINESS-CRITICAL AND VIRTUALIZED WORKLOADS: HPE ProLiant ML350 Gen11 (P69313-005) powered by Intel Xeon Gold 5416S (16 cores, 2.0GHz) with 64GB DDR5 memory and 8 SFF drive bays, delivering improved performance for virtualization, databases, and application consolidation
- PROCESSOR – XEON GOLD FOR HIGHER PERFORMANCE AND EFFICIENCY: Intel Xeon Gold 5416S (16 cores, 2.0GHz) delivers improved performance, cache optimization, and workload efficiency compared to entry-level CPUs, enabling virtualization clusters, database environments, and application consolidation with greater reliability.
- MEMORY – 64GB DDR5 WITH ENTERPRISE-LEVEL SCALABILITY: Includes 64GB DDR5 HPE SmartMemory (2×32GB RDIMM), expandable up to 8TB across 32 DIMM slots, delivering high bandwidth, improved efficiency, and scalability for memory-intensive workloads and long-term infrastructure growth.
- STORAGE – SSD PERFORMANCE WITH FLEXIBLE 8SFF EXPANSION: Configured with 2×480GB SATA SSDs and 8 SFF drive bays, paired with HPE MR408i-o RAID controller (4GB cache) supporting RAID 0/1/10, enabling fast data access, reliable protection, and scalable storage for business-critical applications.
- EXPANSION – PCIe GEN5 PLATFORM FOR I/O AND ACCELERATION: Supports PCIe Gen5 expansion and OCP 3.0 connectivity, enabling upgrades for high-speed networking, storage, and GPU acceleration to support workloads such as VDI, analytics, and compute-intensive applications
Retention needs an owner, risk treatment, funding status, review date, and triggers for reassessment. Otherwise, a temporary decision can become unattended technical debt as support expires and specialist skills disappear.
Rehost: prioritize a low-change move
Rehost when speed matters, the stack is supported in the destination, the application is understood, and code-change risk is unwelcome. It can support a data-center exit or create a landing point for later modernization. Define whether rehost is an accepted end state—with cost, security, and reliability criteria—or a temporary step with a dated backlog and follow-on decision.
Watch for oversized resources, always-on nonproduction systems, licensing changes, latency to dependencies that remain on premises, and unchanged backup, monitoring, or security gaps. A cloud bill higher than the source environment may indicate that the workload was moved without rightsizing or cost controls.
Free tools Windows power users keep installed
One-click scans. No signup required.
Relocate: move the platform with the workload
Relocate can suit virtualized estates where a compatible target allows infrastructure to move with little application alteration and continuity of operating practices has value. Validate platform support, licensing, storage and network behavior, backup and recovery, performance, and future exit options. Infrastructure compatibility alone does not prove application compatibility.
Replatform: make bounded improvements during the move
Replatform when limited changes—such as adopting a managed database, runtime, or container platform—can deliver measurable operational benefit without a full redesign. Specify the boundary between platform change and application rewrite, test compatibility and performance with a pilot, and set rollback criteria. Managed services can reveal assumptions in the existing application, while database behavior or team operating skills may differ from expectations.
Repurchase: replace ownership with a product decision
Repurchase fits a commodity capability better served by a commercial product or SaaS than by continued custom maintenance. Evaluate functional fit, integration, identity, security controls, regulatory suitability, data export and portability, vendor viability, contract terms, subscription escalation, customization limits, process change, and exit cost. SaaS can reduce infrastructure and maintenance work but may increase total cost or constrain the business. AWS likewise advises evaluating business requirements, security, and compliance when selecting a replacement; see its strategy guidance.
Refactor or re-architect: invest where the value justifies the risk
Consider deeper change when a strategically differentiating system cannot meet future product needs, release speed, scale, or resilience in its current form—and when there is a credible target architecture, executive sponsor, funded product team, testing plan, and operating capability. Old code alone is not a business case. AWS notes that refactoring during a large migration is complex; depending on context, moving or replatforming first and modernizing later may be more practical. See AWS’s migration strategies.
Prefer controlled increments over an all-at-once rewrite. A modular monolith may be a better target than microservices if independent deployment is not valuable. Where useful, a strangler approach can route selected capabilities to new components while the legacy system remains available. Establish API and data boundaries, contract tests, observability, automated deployment, domain ownership, and an explicit plan for retiring parallel components. Cloud-native services may improve agility, but they can also add operational complexity, skills demands, platform dependence, and cost.
Rank #3
- HPE ProLiant ML30 G10 Plus Tower Server, perfect for small businesses and remote offices
- Xeon E-2314 4-Core 2.8GHz 8MB CPU, Turbo up to 4.5GHz
- Memory: 32GB (2 x 16GB) DDR4 PC4-25600 3200MHz Unbuffered Memory
- Hard Drive: 4TB (4 x 1TB) SATA III 6Gb/s SSD for Ultra Fast Storage
- Hard drives installation required
Rehost, relocate, or replatform?
These choices differ in what changes, even when all involve moving a workload. AWS distinguishes relocation as a hypervisor-level infrastructure move, while replatforming includes some optimization for cloud capabilities. Use the decision below as a starting point, then confirm the target provider’s technical and licensing specifics.
| Question | Rehost | Relocate | Replatform |
|---|---|---|---|
| What changes first? | Hosting infrastructure; application changes are minimal. | Underlying virtualization or infrastructure platform. | Hosting plus limited application or platform adjustments. |
| Best reason to choose it | Move quickly with low code-change risk. | Preserve an existing virtualized operating model during a platform move. | Gain specific operational benefits without funding a full redesign. |
| Key validation | Rightsizing, licensing, dependencies, security, recovery, and cost. | Compatibility, licensing, storage/network behavior, recovery, and exit options. | Compatibility, performance, scope boundary, skills, and rollback. |
Do not let a “minor changes” label conceal a rewrite. If the application needs material architectural redesign to meet the goal, assess it as refactoring rather than allowing scope to grow informally during replatforming.
Turn application decisions into a modernization roadmap
- Set the business case. State why the workload is under review, what measurable outcome matters, what happens if no action is taken, and whether a deadline is external. Outcomes might include fewer outages, faster recovery, faster releases, less infrastructure labor, removal of unsupported software, lower cost per transaction, or improved customer response.
- Inventory and map dependencies. Establish ownership, technology, cost, usage, criticality, data, and interface evidence. Mark unknowns instead of treating assumptions as facts.
- Decide retire and retain candidates early. This can shrink the estate and avoid funding migrations without value. Apply shutdown controls and time-bound review to these decisions.
- Compare alternatives and economics. Include engineering, testing, data transfer, network redesign, security, training, support, SaaS integration, dual running, license changes, and eventual exit—not only target compute cost.
- Record the R, rationale, and confidence. Document assumptions, risks, dependencies, target architecture, rollback, owner, and review date. Provider tools can inform the decision, not own it.
- Pilot a representative workload. Choose one controlled enough to manage, but representative enough to expose real constraints. Do not begin only with trivial applications or the most business-critical one.
- Build waves around dependencies and readiness. Group by business process, shared dependencies, data pattern, target platform, risk, skills, test environment, business calendar, and contractual or regulatory timing.
- Operate, measure, and reassess. Validate service performance and cost after each wave, close security and operational gaps, optimize the target, and revisit decisions when business strategy, technology, regulation, or economics change.
Make the target operating model part of the decision
A modern architecture without the people and practices to operate it may simply shift risk. For each target, assign ownership for platform engineering, incident response, infrastructure as code, CI/CD, observability, FinOps, security engineering, data governance, and developer enablement. A replatform or refactor is not ready merely because the service exists in the chosen cloud; the team must be able to secure, monitor, recover, and control its cost.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Track portfolio coverage and realized results: verified application owners, applications assessed and retired, distribution by R, wave completion, availability and recovery, change-failure rate, release frequency, cloud cost against a comparable baseline, security findings, technical-debt reduction, and benefits achieved against the business case. Define a baseline and measurement period for each metric so a lower bill or faster release is not claimed without comparable evidence.
Assessment tools and provider-specific considerations
Assessment products can speed discovery, cost modeling, and migration planning, but provider-specific tools may naturally frame results around that provider’s destination. Use them as evidence, retain ownership of the decision, and evaluate discovery depth, dependency mapping, application-level analysis, hybrid support, privacy, exportability, cost assumptions, and human review. A complimentary assessment is not the same as neutral consulting.
| Option | Useful for | Important qualification |
|---|---|---|
| AWS Migration Evaluator | AWS describes it as a complimentary service for data-driven AWS planning and business cases. | Provider-specific; assumptions and destination costs still require review. |
| AWS Transform strategy recommendations | Can analyze discovered inventory and suggest a 7R, target service, confidence score, and reasoning. | Recommendations depend on discovery evidence and do not replace business and architecture approval. |
| Azure Migrate | Discovery, assessment, cost estimation, migration planning, and modernization for Azure. | Microsoft says it is free to use with an Azure subscription; partner tools and resulting Azure resources may incur charges. |
| Azure Migrate cost estimation | Models Azure VM costs using workload and pricing assumptions. | Estimates depend on region rates, offers, licensing, uptime, discounts, and Azure Hybrid Benefit. Microsoft’s default monthly estimate assumes 744 hours for a continuously running VM. |
| Google Cloud Migration Center | Cost estimation, business-case development, assessment, and planning. | Its default pricing track uses a three-year committed-use discount assumption; estimates are not guarantees of actual cost. See the cost-estimation overview and pricing timeline. |
| Google Cloud Migrate to Virtual Machines | Rehosting virtual machines into Google Cloud. | Google says the migration service itself is provided at no charge for migrations into Google Cloud; testing, validation, storage, networking, and resulting workloads can incur normal infrastructure charges. |
Cloud runtime prices should be modeled for the region, workload profile, license terms, discounts, and commitment choices that apply; an assessment estimate is not a quote. Include migration labor and post-migration operations. Provider professional services, partners, systems integrators, modernization specialists, managed platforms, SaaS vendors, and FinOps tools may be relevant, but compare them on scope, references, security, delivery model, data handling, and exit terms rather than assuming a provider recommendation is neutral.
When not to modernize yet
Do not modernize simply because an application is old or because a cloud program needs a large project list. If the system is stable and inexpensive, has no compelling product or risk problem, and would cost more to change than the expected benefit, retain it with a managed risk plan. If evidence is incomplete, make discovery the next decision rather than guessing an R. If a SaaS replacement or business retirement is imminent, an interim move may create waste. If the organization lacks tests, ownership, or operating skills, address that readiness gap before promising a high-risk transformation.
Recommended Free Tools
The defensible choice is the one that solves a defined business problem at acceptable total cost and risk—not the one that sounds most technically ambitious.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
