EN
keyboard_arrow_down
Choose a language:

Cloud Placement Organizer – Cloud migration strategy and planning for complex IT landscapes

Automated distribution planning of workloads in the cloud

Key benefits at a glance

  • Analysis & visualization of the IT landscape in a dependency network
  • Estimation of future operating costs
  • Time savings due to high degree of automation

Your challenge in planning the cloud migration strategy

Companies that want to migrate their IT landscape to the cloud are faced with complex, mostly manual planning. Especially if they have a very large IT environment and are also pursuing a multi or hybrid cloud strategy, planning for cloud migration can quickly become complex and involve vast resources.

Above all, thousands of servers and applications must be analyzed to determine which technical dependencies exist between them. In addition, a decision must be made for each system  taking into account the respective business requirements  as to whether a public cloud should be considered or whether it would be better to use a private cloud. Last but not least, the selection of the right target platform (e.g., Microsoft Azure, Amazon AWS, Google GCP) represents an additional challenge for many companies. Here, it must be ensured that this also takes into account internal and external compliance requirements.

Our solution? Cloud Placement Organizer – cloud migration strategy for complex IT landscapes

Cloud Placement Organizer is a cloud planning tool that analyzes the current IT landscape and calculates the optimal placement  in the private or public cloud  of workloads (apps & servers) in the cloud according to operating model (IaaS, PaaS), costs and compliance. Internal and external regulations and specifications are taken into account. Placement in the target system is fully automated  for companies, this means significant time savings compared to manual distribution. 

This means that especially in very large IT landscapes with several thousand servers and applications, the Cloud Placement Organizer can show its strengths to the full, making the complexity in cloud transformation projects manageable and accelerating the progress of the project.

Get to know our solution

Preparing your IT landscape for cloud migration is as simple as this

01

Upload data

The data of your IT landscape can be easily fed into the application via drag & drop using an Excel-based data entry template. The template can be downloaded in advance if required.

02

Select constraints

The planning of cloud systems is based on business and technical requirements. We work with you to select the applicable requirements from a best-practice catalog - or we customize them for you.

03

Start planning

After the data is uploaded, the automated planning is started and a possible target distribution is calculated.

Benefits of the Cloud Placement Organizer

launchEasy simulation

Simulation of different target operating models and provision of provider-independent recommendations (e.g. IaaS or PaaS) based on relevant evaluation criteria

shareDistribution planning

Automated distribution planning and optimization within seconds

view_quiltVisualization

Presentation of the IT landscape in a relational network for easily recognizing clusters and dependencies

buildIndividual rules

Provision of a standard set of rules and mapping of customer-specific use cases with individually adaptable rules

paymentsCost planning

Estimation of future operating costs based on planning (in Future Mode of Operation FMO)

swap_horizCompatibility

Compatibility with existing CMDBs or discovery tools

verified_userCompliance

Consideration of compliance and security requirements during planning

data_usageOptimization

Permanently repeatable computations for continuous optimization

Pricing

Get a preview of what your future IT landscape might look like in the cloud with the Cloud Placement Organizer.

You can switch from package 1 to package 2 at any time during the project. Costs incurred up to that point will be credited accordingly. The costs for a successfully completed Cloud Placement Organizer project can be credited to subsequently commissioned cloud transformation projects.

Package 1 (Quick Assessment)
€ 10,000(excl. VAT)
  • Feeding IT infrastructure data
  • Conducting a client workshop on constraints
  • Application of the standard ruleset for placement rules
  • Conducting a simulation
  • Providing a final report
  • Perform and schedule up to 1000 workloads
Package 2 (Deep Assessment)
€ 50,000(excl. VAT)

All services from package 1, in addition:

  • Execution of up to 5 simulations (iterative)
  • Preparation of a detailed final report
  • Interpretation of the results and submission of recommendations for further optimization
  • Programmatic adjustments to the placement rules on a small scale
  • Performing scheduling for unlimited number of workloads
Package 3 (Managed Service)
on request
  • All services from package 1 and 2
  • Price on request and depending on the size of the IT landscape
  • Long-term support over a defined period
  • Billing on a monthly basis

Develop your cloud migration strategy today

Please enter your business e-mail address if you would like to receive more information, an offer, or a demo of this product. We will get back to you as soon as possible.

check
Sent. Thank you for your interest, we will get back to you as soon as possible!

FAQ

What does a cloud migration strategy look like?

A cloud migration results in a system being moved from a source environment to a target environment. Often, during the migration, an adaptation of the architecture for the target environment is also carried out, for example, in order to eliminate technological legacies of the past. The so-called "6-R approach" is used for this purpose:

  • Rehosting (Lift & Shift): cloning the existing IT landscape
  • Replatforming/Redeploying: migration to a new technological base
  • Repurchasing: switching the product
  • Refactoring/Rearchitecting: rebuilding the application
  • Retire: shutting down legacy systems
  • Retain: maintaining in the current state (no migration)

Typically, enterprises do not focus on just one of the 6-R approaches to cloud migration, but they often choose a combination depending on the anticipated technology challenges.

Often, the vast majority of applications and systems are migrated using the "rehosting" approach, as this is usually the most cost-effective option that also involves few technological dependencies. This strategy is supplemented by replatforming or redeploying approaches in order to be able to perform the technological modernization for a portion of the application components.

The most rarely used variant is the refactoring/replatforming variant, as this involves an elaborate rebuild of the app. While this helps to take advantage of the greatest cloud benefits, it comes at a high cost in the short term.

The Cloud Placement Organizer already brings a set of mechanisms to identify and suggest the ideal migration strategy depending on the system and app.

Public Cloud vs. Private Cloud: What's the difference?

The cloud consists of a collection of servers that pool resources such as storage. The difference between the public and private clouds is primarily that in the private cloud, the resources of the underlying IT infrastructure are exclusively available to one company, and in the public cloud, several companies share the use ("Shared Infrastructure").

 

The public cloud is provided by an external service provider, a so-called cloud service provider. The service provider procures and operates the IT infrastructure so that many of its customers can consume the IT services. This is an IT environment shared by several customers. Public clouds are characterized above all by a very high level of functional diversity, which can often only be replicated in the private cloud at great expense.

 

The private cloud is often operated by companies themselves  sometimes also by external service providers  on their own. The company procures and operates the IT infrastructure and consumes the IT services exclusively itself, without third-party users such as other companies using the same IT infrastructure. This makes the private cloud particularly suitable where companies have a particularly high need for IT security, since here the cloud is not shared and used with other users.

When can a hybrid cloud be beneficial?

A hybrid cloud helps in combining the benefits of both cloud types  public and private cloud. Thus, a company can use the functionality of the public cloud, but for individual selective servers and apps the private cloud, if there are special needs regarding security. However, the prerequisite for efficient use of the hybrid cloud is precise planning of which systems and servers are to be operated and used in the private or public cloud. In this way, the advantages of both worlds can be ideally combined.

What determines whether to migrate to the public cloud or private cloud?

The most common requirements for the cloud come from the area of IT security. Companies with a high need for security for particularly critical systems prefer the private cloud because it runs on company-owned systems and no other companies also use the systems. Other aspects in the decision-making process can include the costs incurred, any technical restrictions or the use of a provider's particular technical strengths.

What are cloud migration best practices?
  1. Clear strategy for using private and public cloud
    Since both private and public cloud often offer a similar portfolio of services, it should be clearly defined for which purposes the respective cloud type will be used. This ensures that there are no discrepancies in the planning process prior to migration.
  2. Very good knowledge of the IT landscape
    The systems and apps to be migrated should be sufficiently well documented to be adequately considered in the planning process. This includes documenting the amount of servers and apps, the responsible persons in the company and the business criticality, as well as technical documentation. The better and more extensively a system is documented, the fewer technical and organizational hurdles can impede the migration.
  3. Determining the scope of the migration
    It should be determined prior to migration which systems and apps will be migrated to the cloud in each case. The selection can be made based on business units and processes as well as geography and lifecycle status of the respective systems. This approach ensures that the migration scope is clearly outlined and that the scope does not change unscheduled during the migration process (so-called "scope creep").
  4. "Start small, think big"
    A cloud migration is a complex undertaking. Since there is often little experience at the beginning of a migration, it is recommended to start the migration with few and non-critical systems and apps. On the other hand, planning should be sufficiently long-term and anticipate an increase in migration speed to be able to migrate even large landscapes. Thus, it is possible to start with low risk at the beginning and keep the migration risk limited in the further course of the project.
  5. For mass migration: use a migration factory
    A cloud migration is to a large extent an individual project. Even though each system and app functions and acts uniquely, recurring activities, such as testing the systems and apps, can still be bundled. It is advisable to set up a so-called Migration Factory, which has the task of centralizing tasks that can be standardized and at the same time granting cloud technicians flexibility to solve special issues.
What points should be considered before a cloud migration (cloud migration checklist)?

Before a cloud migration can be carried out, it is important to carry out the most accurate planning possible. This is the only way to ensure that the migration runs efficiently and is ultimately successful, even in very large IT landscapes. The following apply as prerequisites for planning:

  • The IT landscape is sufficiently well inventoried (How many servers and apps are to be migrated? Which people are responsible?)
  • Technical dependencies and interfaces between servers and apps are known and documented (Which systems exchange data with each other?)
  • Business requirements for the servers and apps, e.g. for the availability of the systems, are fully known or can be identified
  • Compliance requirements, e.g. for IT security and geographical conditions, are known or can be identified
  • An overarching IT strategy exists that describes the scope of cloud usage

You might also be interested in: