Migration Treatment

Migration Treatment is where you organise applications by 6R treatment and adjust the AI's recommendations. It turns your chosen strategy into a concrete 6R treatment for every workload, then lets you review and override those decisions from whichever angle suits the conversation.

Three flat sibling tabs run across the top: Treatment Preferences (the guard rails that drive the AI's suggestions), Treatment Board (the working board for assigning and overriding treatments), and Analysis Views (data cuts to review the estate from multiple planning angles).

Treatment overview¶

At the top of the Treatment Manager, summary tiles show where the plan stands. Counts here are illustrative.

A Treatment Distribution bar shows, at a glance, how the estate is spread across the 6R categories.

Treatment Board and Analysis Views¶

The Treatment Board and Analysis Views tabs let you assign and review treatments. Use the Treatment Board to assign and override treatments directly, and Analysis Views to slice the plan by different dimensions.

Treatment Preferences: the guard rails¶

Open Treatment Preferences from the left sub-nav. Preferences are the guard rails that guide consistent treatment decisions across the estate: the rules the AI follows so the same technology is treated the same way everywhere.

For every server, based on the technology it runs and the chosen strategy, Dr Migrate determines the most suitable cloud modernisation target. For example, a .NET workload may be recommended for App Service; where no suitable PaaS target exists, it recommends IaaS instead. You can:

• Filter by category (for example data services or middleware) to work through one technology family at a time.
• Set the guard rails in advance with the Microsoft account team and solution architects, so the generated plan reflects agreed targets from the outset.
• See, for each preference, whether it was human-assigned or auto-applied, so changes are always traceable.

Once the preferences look right, use Generate treatment plan to have Dr Migrate apply them across the estate and populate the Treatment Board.

6R treatments and treatment options¶

In Dr. Migrate, 6R treatment assignment is performed at the server level. This means each server can have only one active 6R treatment at any point in time, such as Rehost, Replatform, Replace, Retire, Retain, or Replatform/Refactor.

A server can, however, have multiple treatment options. Treatment options are useful when the same server supports more than one application workload. They allow you to describe different target outcomes for each application context, while still keeping the server's active 6R treatment consistent.

For example, a server cannot be both Rehosted and Replaced at the same time. If a server is first assigned Rehost and is later assigned Replace, Replace becomes the active treatment for that server. The most recently assigned treatment is the treatment that applies.

Example¶

Server01 supports two application workloads:

In this example, Server01 has multiple treatment options because it is associated with multiple applications. However, the active 6R treatment for Server01 is still only one treatment: Replace.

This is because treatment assignment is controlled at the server level, not separately for each application. The application-level treatment options help explain the intended replacement path for each workload, but they do not create multiple active treatments for the same server.

Cost allocation¶

When a server is mapped to multiple applications, its future-state cost is split evenly across those applications. The cost is not duplicated for each application.

For example, if Server01 has an estimated future-state cost of $1,200 per month and is mapped to two applications, the cost allocation would be:

The same rule applies whether the server has one treatment option or multiple treatment options. Dr. Migrate allocates the server cost evenly across all applications associated with that server.

Recommended flow¶