NEW IN VERSION 6.2
The Migration Dashboard helps you plan a move to a new platform. K looks at every asset in scope and recommends a migration strategy, then scores how much effort the move will take and how risky it is.
This page covers how to set up the dashboard, run the analysis, and adjust the rules K uses.
Before you start, make sure that:
-
the sources you want to migrate are loaded into K
-
the K Platform daily and weekly batches have run
Run business lineage first if you can. It isn't required, but it gives better recommendations.
Preparing for migration analysis
To help K improve the migration analysis, you can tag assets with the following two attributes:
-
Migration Exclusion: Assets tagged with this attribute are excluded from the Migration Dashboard. This is a great way to remove any out of scope assets that could create noise in your Dashboard
-
Performance Issue: These are the assets that you already know have issues and require a redesign prior to migration e.g. not a simple Retire or Refactor migration approach
You can use the Bulk Action function to tag multiple assets quickly.
Create a migration pair
A migration pair tells K what you're moving (Source) and where it's going (Target). The dashboard shows one pair at a time, so you need at least one pair before it has anything to show.
-
Go to Migration Settings and click CREATE PAIR
-
Choose what's being migrated:
-
Database: database sources move to your database target
-
Tool: tool sources move to one target tool
-
-
Select the target
-
Select the sources to include
-
Click CREATE PAIR
K supports only one database target at a time,Your first database pair sets the target for every database pair after it.
A source can only belong to one pair. Sources already in a pair can't be selected.
Run the migration analysis
Click RUN NOW to analyse every pair. You can choose either a:
-
Full run: Recalculate every asset, or
-
Run for not categorised assets: Only process assets that don't have a strategy yet. These are typically new assets or assets previous marked as excluded for migration
Anything a user has changed by hand is never overwritten.
When the run finishes, click OPEN DASHBOARD to see the results.
Change or delete a pair
You can't edit a pair. To change its sources or target, delete it and create a new one. Strategies and scores already on your assets will stay.
How K assigns a migration strategy
K checks each asset against these rules in order. The first rule that matches sets the strategy.
|
Strategy |
When K assigns it |
|---|---|
|
Retire |
The asset is unused or used infrequently |
|
Reinvent |
More than 10 consumption users, and the asset is part of a shared consumption or shared raw source cluster |
|
Redesign |
The asset has a performance flag, and has non-portable attributes or code |
|
Refactor |
No performance flag, and the asset has non-portable attributes or code |
|
Rehost |
No non-portable attributes or code |
Retire recommendations also carry a confidence score: 100 if the asset is unused, 20 if it's used infrequently.
You can change an asset's strategy manually. Where you have manually changed the migration strategy, K retains your choice on future runs.
How K scores migration effort and migration risk
Effort and risk starts at Low and increases based on certain triggers and thresholds.
You can change the default thresholds via Platform Settings
Factors that increase effort
-
Number of downstream queries
-
Migration strategy
-
Reinvent and Redesign is automatically classified as High effort
-
-
Number of non-portable code items
-
Number of non-portable attributes
-
Number of downstream consumption/presentation assets and users
Factors that increase risk
-
Migration effort
-
Number of governance indicators
-
Number of downstream consumption/presentation assets and users