6R Application Treatment

6R Application Treatment

Overview

The 6R Application Treatment Overview provides a comprehensive dashboard for managing application migration strategies using the 6R methodology (Rehost, Replatform/Refactor, Replace, Re‑Architect, Retire and Retain). This interface allows you to view your entire application portfolio, assign treatments at both application and server levels, and leverage AI assistance for initial treatment planning. Avoid leaving workloads without a treatment—every application needs a defined path to the cloud.

ℹ️
Why assign 6R treatments? These decisions drive migration cost, effort, timing and sequencing. Assigning a treatment to every application ensures no workload is overlooked and allows accurate planning for resources, timelines and costs.

Estate Overview

The Estate Overview tab provides a comprehensive rollup view of your application portfolio, organized by 6R treatment categories.

AI Assistant: Initial Treatment Plans

ℹ️

AI Assistant

Treatments are applied using available data. If no strategy or target is set, servers default to Rehost. You can customize or recalculate treatments anytime; user-assigned treatments are preserved.

AI Assistant Actions

  • Recalculate Treatment Plans: Regenerates AI recommendations based on current data
  • Undo Treatment Plans: Reverts to previous treatment assignments

AI Assistant Capabilities

The AI Assistant provides automated recommendations for 6R strategies based on application insights, helping quickly generate initial treatment plans.

AI Assistant Capabilities

  • Automated Analysis: Evaluates application characteristics and infrastructure
  • Treatment Recommendations: Suggests appropriate 6R treatments based on technical analysis
  • Preservation of User Input: Maintains manually assigned treatments when recalculating
  • Continuous Learning: Improves recommendations based on user feedback and decisions

When to Use AI Assistant

  • Initial Planning: Generate baseline treatment plans for new assessments
  • Portfolio Updates: Recalculate treatments after infrastructure changes
  • Validation: Verify manual assignments against AI recommendations
  • Bulk Operations: Apply consistent treatment logic across large portfolios
⚠️
Important: AI-generated treatments are recommendations only. Always review and validate against your business requirements, technical constraints, and migration strategy before finalizing assignments.

Application Treatment Rollup

The rollup provides an overview of your assigned treatments at an application level, organized into seven treatment categories:

Diagram showing the 6R cloud migration strategies: Rehost, Replatform/Refactor, Re-Architect, Replace, Retain, and Retire with color-coded bars and descriptions

The 6R migration strategies provide different approaches for cloud migration, from simple lift-and-shift to complete re-architecture

⚠️
Don’t leave workloads unassigned. Any applications or servers appearing in the Needs Assignment category require immediate attention. Assign a treatment before moving on to wave planning – unassigned workloads will disrupt cost estimates and scheduling.

Rollup Features

  • Search Functionality: Use “Q Search Application” to filter applications across all categories
  • Application Counts: View total applications and VMs assigned to each treatment category
  • Real-time Updates: Counts update automatically as treatments are assigned or modified
  • Category Descriptions: Each category includes a brief description of the treatment approach

Applications

The Applications tab provides detailed management capabilities for individual applications, allowing you to assign treatments, review modernization insights, and manage infrastructure details.

Application Selection and Filtering

Selection Options

  • Select Application: Choose from available applications in your portfolio
  • Select Filter(s): Apply additional filters to narrow down application selection

Application Overview Tab

The Application Overview tab displays comprehensive information about the selected application:

Modernization Insights Tab

The Modernization Insights tab provides comprehensive visibility into the software inventory and modernization opportunities across all servers associated with the selected application.

Modernization Targets

The system identifies modernization targets running on VMs related to the selected application:

Column Description Purpose
Discovered Technology Technology name with category icon Identify modernization candidates
Category Technology classification Group similar technologies
Server Count Number of servers using this technology Understand scope of modernization
Suggested Destination Recommended Azure PaaS service Target platform for migration
Key Benefits Advantages of the suggested destination Justify modernization decisions
Assessment Tooling Tools and methods for deeper analysis Guide next steps for modernization planning
PaaS Suitability Cloud readiness assessment Evaluate modernization complexity
Est. Modernization Effort Effort estimation for migration Plan resource allocation and timelines
ℹ️

The Assessment Tooling column provides critical guidance for customers to understand their next steps in gathering more contextual information about the modernization path and target for each discovered technology. This information helps you:

  • Plan Assessment Activities: Identify which tools and methods to use for deeper analysis
  • Understand Modernization Complexity: Determine the level of effort required for each technology
  • Prioritize Modernization Efforts: Focus on technologies with clear migration paths and lower complexity
  • Resource Planning: Allocate appropriate time and expertise for assessment and migration activities

Software Inventory Search

Below the modernization targets table, you can search and filter through the comprehensive software inventory of all servers associated with the application. This detailed view includes:

Column Description Purpose
VM_ID Virtual machine identifier Identify specific servers
Application Name Software application name Identify installed software
Version Application version number Assess version-specific modernization needs
Vendor Software provider company Understand licensing and support considerations

Software Inventory Benefits

  • Comprehensive Discovery: View all software across all servers in the application
  • Version Analysis: Identify outdated versions that may have better modernization paths
  • Vendor Assessment: Understand software provider relationships and migration support
  • Dependency Mapping: Identify software dependencies that may affect modernization decisions

Tip

Use the Assessment Tooling information to prioritize your modernization planning. Focus first on technologies with clear assessment paths and lower estimated effort, then work on more complex migrations that may require additional analysis or specialized tools.

Migration Treatment Tab

The Migration Treatment tab provides comprehensive tools for managing migration treatments at both the application and server levels.

Bulk Assignment Section

ℹ️
Bulk Assignment for Individual Applications: This section provides bulk assignment capabilities for all servers within the selected application. For bulk operations across multiple applications, see the Bulk Assignment section below.

At the top of the Migration Treatment tab, you’ll find the Bulk Assignment section that allows you to efficiently manage treatments across all servers associated with the selected application:

Bulk Assignment Workflow

Select Treatment

Use the “Bulk Assign Treatment to all servers” dropdown to choose a 6R treatment

Apply Treatment

Click “Assign Treatment” to apply the selected treatment to all servers in the application

Auto Assignment

Use “Auto Assign Treatment” to let the AI generate appropriate treatments based on server characteristics

Undo Changes

Use “Undo Treatment Plans” to revert any bulk changes and restore previous assignments

Pro Tip: Use bulk assignment when you want to apply the same treatment strategy across all servers in an application. This is particularly useful for applications where all servers should follow the same migration approach.

Server Level Treatment Section

Below the bulk assignment controls, the Server Level Treatment section provides detailed management of individual server treatments. This is where you’ll work with each VM individually to assign specific migration strategies and targets.

Server Information Display

ℹ️
Server Details: Each row shows the VM name and operating system. Clicking on the VM name will open the Server & VM Quick Editor for that specific VM, allowing you to view and modify detailed server information.
ℹ️
Resources: Hardware specifications including CPU cores, RAM, and storage capacity. These details help you understand the server’s current capacity and plan appropriate Azure SKU sizing for the target environment.
ℹ️
Key Technologies: Blue badges showing technologies identified on each server (e.g., “IIS”, “Kubernetes 1.26”, “.NET Framework”). These badges indicate the software stack and help determine the most appropriate migration treatment.

Migration Treatment Assignment

The Migration Treatment column contains two interactive elements for each server:

Treatment Type Dropdown
  • Purpose: Select the primary 6R migration strategy for the server
  • Options: Rehost, Replatform/Refactor, Replace, Re‑Architect, Retire, Retain
  • Usage: Click the dropdown to see all available options and select the appropriate treatment
Target Solution Field
  • Purpose: Specify the exact migration target or service
  • Examples: “Exchange Online”, “Azure App Service”, “Azure Database for PostgreSQL”
  • Usage: Type directly into the field or use the dropdown if predefined options are available
  • Clear Function: Use the ‘x’ button to remove the current solution and start fresh

Target Azure SKU:

Visual Indicator: The blue “PaaS/SaaS” badge shows the target environment type based on your treatment selection. This helps validate that your treatment and solution choices align with the intended target platform.

6R Treatment Options:

ℹ️

Treatment Categories: The 6R treatment options are organized into seven categories as shown in the Estate Overview section above. Each treatment represents a different migration strategy:

  • Rehost: Migrate as‑is to Azure VM (IaaS) – minimal changes, fastest migration
  • Replatform/Refactor: Modernize to Azure PaaS services (e.g., Azure App Service, Azure Functions)
  • Replace: Migrate to SaaS or cloud‑native alternatives (e.g., Exchange Online, Azure Database)
  • Re‑Architect: Innovate with cloud‑native architectures (e.g., microservices, containers)
  • Retire: Decommission unused or redundant servers
  • Retain: Keep on‑premises due to technical or business constraints
  • Needs Assignment: Workloads awaiting a treatment assignment – assign a treatment before planning

Practical Workflow

Review Server Information

Click on the VM name to open the Server & VM Quick Editor and examine detailed server characteristics.

Analyze Key Technologies

Review the blue technology badges to understand the software stack and modernization potential.

Select Treatment Type

Choose the appropriate 6R treatment from the dropdown based on server characteristics and business goals.

Specify Target Solution

Enter the specific migration target (e.g. “Exchange Online” for email servers, “Azure App Service” for web applications).

Validate Assignment

Review the Target Azure SKU badge to ensure your choices align with the intended platform.

⚠️
Important: The system automatically validates treatment assignments against server characteristics. For example, servers with modern technologies like Kubernetes may be recommended for Replatform/Refactor, while legacy systems might default to Rehost. Always review these recommendations against your business requirements.

Search and Filtering

ℹ️
Use the search bar in the Server Level Treatment section to quickly find specific servers or filter by characteristics such as operating system, resource specifications, or associated technologies. This is particularly useful when working with applications that have many associated servers.

Bulk Assignment

The Bulk Assign Apps tab provides efficient ways to assign treatments across multiple applications simultaneously using two distinct approaches.

Bulk Assignment Interface

ℹ️

Choosing Your Approach

  • Use Assign By App when you want to interactively review and select applications for treatment assignment.
  • Use Import from Template when you have a large number of applications or prefer to work offline with spreadsheet tools.

Assign By App Tab

The Assign By App tab provides an interactive interface for bulk treatment assignment across multiple applications:

Filtering and Search
ℹ️
  • Filter Treatment: Use the dropdown to filter applications by their current treatment status (e.g., All Treatments, Rehost, Replace, etc.)
  • Search Applications: Use the search bar to find specific applications within the filtered set.
Bulk Assignment Controls
ℹ️
  • Bulk Assign to Treatment: Select a treatment from the dropdown and apply it to multiple selected applications.
  • Apply Reassignment: Click the button to execute the bulk treatment assignment.
  • Selection Count: View how many applications are currently selected for bulk assignment.
Application Table

The table displays all applications with their current treatment status and server counts:

Column Description Purpose
Checkbox Selection control Choose applications for bulk treatment assignment
Application Application name Identify the target application
Current Treatment Currently assigned 6R treatment See existing treatment status
Server Count Number of servers associated Understand the scope of impact
Quick Tip: Use the filter dropdown to focus on specific treatment categories, then use the search bar to find particular applications within that filtered set.

Filter and Search

Use filters and search to narrow down the application list.

Select Applications

Check the applications you want to assign treatments to.

Choose Treatment

Select the desired 6R treatment from the dropdown.

Apply Assignment

Click “Apply Reassignment” to update all selected applications.

Import from Template Tab

The Import from Template tab provides a template-based approach for bulk treatment assignment:

Template Workflow

Download 6R Template

Get the standardized template containing all applications and their current status.

Populate Template

Fill in treatment assignments and optional solutions for each application.

Upload Template

Submit the completed template to update all assignments simultaneously.

Template Structure

The bulk assignment template includes the following key columns:

Column Description Purpose Required
Server VM identifier (e.g. VM_190, VM_25) Identify specific servers Informational only
Assessment Scope In Scope/Out of Scope status Focus on relevant servers Informational only
Application Name Associated application Group servers by application Informational only
Environment Deployment environment Consider environment‑specific factors Informational only
Treatment 6R treatment assignment Primary migration strategy Required
Solution (optional) Specific target solution Detailed migration target Optional
Power Status Server power state Consider operational status Informational only
Operating System OS version and type Technical compatibility Informational only
Required Fields
  • Treatment: This is the only required field. You must specify a 6R treatment (Rehost, Replatform/Refactor, Replace, Re‑Architect, Retire or Retain) for each server you want to update.
Optional Fields
  • Solution: While not required, specifying a solution provides clearer migration direction (e.g. “Exchange Online” instead of just “Replace”).
Informational Fields
  • All other fields (Server, Assessment Scope, Application Name, Environment, Power Status, Operating System) are provided for context but do not need to be modified for the bulk assignment to work.
Pro Tip: Use the template’s “Solution (optional)” column to specify detailed migration targets. For example, instead of just “Replace,” specify “Exchange Online” or “Azure Database for PostgreSQL” to provide clear migration direction.