The business question What is our cloud migration strategy? supports the planning of a migration strategy for each application in your cloud portfolio based on the impact of migration on the business capabilities and IT ecosystem. This Kanban board enables you to decide on a migration strategy for each relevant application in the IT portfolio.

The Kanban board shows applications in any of the following lanes:

• Retain: The application supports a business capability for which the Business Relevant indicator is set to Business Enabling or Business Operating and the application cannot be migrated to the cloud immediately. Or the application is at the end of its lifecycle and is about to be retired.
• Rehost: The application is SaaS-enabled but is either outdated or would require rehosting to the cloud platform.
• Refactor: The application requires some changes in code to be eligible for migration to the cloud. The application can be modular or a self-contained application with services that can easily be refactored.
• Rearchitect: The application requires additional effort to make it cloud enabled. For example, this might be due to application health monitoring, application security, data backup and policies, scalability and replication zones, disaster recovery, network utilization, multi-channel communication, or identity management.
• Rebuild: The application could be made cloud ready but would require a change in the build process to ensure seamless delivery. The concepts of CI/CD (continuous integration/continuous delivery) could be leveraged for these applications.
• Migrated: The application has been migrated to the cloud successfully.
• Unknown: The cloud migration strategy is unknown for the application. This may be the case for applications for which the Architecture Type attribute is not set to Cloud-Based.