Stuttgart · Ulmerstraße 300
Cloud migration in Stuttgart – without bad surprises
We accompany companies from Stuttgart and the region into the cloud: vendor-neutral for Azure, AWS and Google Cloud, step-by-step and with cost control right from the start – or deliberately hybrid if data is to remain in-house.
Azure · AWS · Google Cloudhybrid possible
Where cloud costs really arise
The posts that surprise after the migration
Calculation powerusually oversized
Storagegrows silently
Data transfer outsidethe much overlooked post
Licencesrarely migrate automatically
Schematic representation of typical cost drivers, no measured values. The actual distribution depends heavily on architecture and use.
Three triggers with which companies come to us
Hardly anyone migrates because the cloud is modern. In practice, there is almost always a concrete occasion – and that determines the pace and the cut.
The hardware is at the end
Servers run out of maintenance, the data center becomes too small or the contract with the hoster expires. The deadline is fixed and suddenly a strategy topic becomes a project with a deadline.
Increasing safety and proof obligations
An audit, certification or new obligations such as NIS2 make it visible that the grown environment is no longer sustainable. Patch stands, logging and recoverability become the question someone needs to answer.
The bill has gone out of hand
The most common occasion with which companies come to us: It has already been migrated, but without control. Now the cloud costs more than the old data center and no one can say exactly what for.
The Three Mistakes We Fix Most Often
We are often only called when a migration has already taken place. These three points occur so regularly that we anticipate them here – even if you hire someone else in the end.
1
Move everything, adjust nothing
Lift and shift is completely legitimate as a first step – if someone readjusts afterwards. If a machine that was generously sized in its own data center is adopted one to one, you pay this generosity monthly from now on.
Better: Right-sizing belongs firmly in the weeks after the migration, not on the wish list.
2
Forget the data transfer
Computing power and memory are on offer. What comes out, often not. For applications that talk a lot with systems outside the cloud – or are spread over several regions – this quickly becomes a noticeable item.
Better: Calculate data flows beforehand, not discover them on the third invoice.
3
No exit strategy
The deeper you go into a provider’s managed services, the harder it will be to switch. This can be a conscious decision. Unconsciously hit, it becomes a problem as soon as prices, conditions or the political situation change.
Better: Determine beforehand what a move would cost – and what would make it impossible.
What an inventory answers
Before anything moves, we clarify four questions. They cost a few days and prevent the surprises that make a cloud migration expensive.
What's going on?A reliable list of systems, their dependencies and who actually uses them. Experience has shown that applications appear that nobody in the house knew about anymore.
What does the operation really cost today?Not only hardware and licenses, but also maintenance, electricity, space and the working time that is bound in the operation. Without this number, no before-and-after can be calculated.
What must not leave the house?Protection requirements per system, derived from data protection, contracts and trade secret. This results in which parts remain hybrid.
What is the most economical way per system?For some applications, the move is enough, others need a conversion, and some simply do not pay for the migration. We explain the procedure per system in detail on the page for Cloud Migration.
What is typically different in the Stuttgart area
In the Stuttgart area we encounter a certain starting point: medium-sized companies with IT that has grown over decades, often their own server room and a small team that keeps everything going. Those who are set up in this way cannot afford a Big Bang – day-to-day business continues.
In addition, there is an attitude we share: not everything has to go to the cloud. In industry, there are good reasons to keep production and measurement data in their own network – from latency to company secret. A hybrid model is often not the compromise, but the right answer.
Because we are on site, we can look at the surroundings before recommending anything. A server room says more about the state of an IT in twenty minutes than three inventory lists.
- Industry proximity shapes the requirementsManufacturing, measurement technology and control pose different questions than a pure office world.
- Hybrid is often the right answer hereWhat should stay in the house, stays in the house – the rest moves.
- On-site inventoryWe look at what is actually going on instead of building migration plans on call.
Your contact person in Stuttgart
Our office is located in Stuttgart-Wangen. We come to you for an inventory.
Discussion of projects
- Initial consultation free of charge and without obligation
- Also suitable if already migrated and it clamps
- On request with initial assessment of cost drivers
Frequent questions
No, and we often advise against it. Applications with hard latency requirements, production proximity or special protection requirements often remain better in their own network. A hybrid model usually makes sense: What benefits from scaling and managed services moves – the rest remains. We make this decision per system, not across the board.
Yes, this is even a frequent entry. At the beginning, there is an inventory: which resources run, how are they dimensioned, where data transfer takes place and which services are paid for but hardly used. The analysis usually results in effective measures quickly before talking about architecture.
Yes. We migrate gradually and set up the conversion so that there is a way back. This takes longer than a change of date, but is the only sensible way for a company with ongoing day-to-day business.
It depends on your starting position, not on our preferences. We are not partners of any of the three providers and do not earn a license. In practice, existing contracts, know-how in the team and the specialist applications used are often decisive.
By right-sizing after migration, automating shutdown times, monitoring data transfer and regular monitoring instead of one-time optimization. Above all, it is important that someone actually reads the bill – surprisingly often that does not happen.
There are several ways to do this: regions within the EU, a hybrid model with the local location of the critical data or complete operation in its own data center. Which variant carries depends on the need for protection. To classify the often cited on-premises trend, we have written our own contribution.
On request, yes, with monitoring, maintenance and clear reaction times – read under Managed Services. Also possible is the transfer to your own team; The documentation for this is created during the project anyway.
Related benefits
Cloud migration in detailRehost, Replatform or Refactor – the procedure per system.Find out more ›Data MigrationTake over stocks from old systems without losses.Find out more ›Managed ServicesOperation, monitoring and support after migration.Find out more ›Software development in StuttgartApplications that are built or converted to be cloud-ready.Find out more ›
Migration planned – or already run?
Both are a good time to talk. You get an honest assessment of what is worthwhile, what should remain and where the costs actually arise.