Cowork Arcetec

Industria de pinturas — Critical infrastructure migration to Azure

Client: Industria de pinturas — Manufacturing

The challenge

SAP, SQL Server, and web services ran on on-premises servers, with third-party integrations that could not break during the move.

The solution

Wave-based migration in eight weeks, with integrations intact and addressing planned in advance. The three-year reservation brought a 62% discount on compute.

Why does a wave-based migration reduce risk for operations?

Moving critical systems all at once can expose operations to failures at any point in the move. A wave-based migration makes it possible to advance in stages, validating each set of services before moving on to the next. In this case, that strategy is what made it possible to complete the move in eight weeks without affecting third-party integrations.

Planned addressing is another key piece. When applications change location, routes and connections must be defined in advance so that systems can find each other without depending on improvised adjustments. That planning makes the change predictable and lets the team know at all times what is being moved and what must keep working.

Finally, the three-year reservation shows that the decision to migrate is also a financial one. By committing compute usage over a longer term, the company significantly reduced its cost, which turns the migration into an investment with measurable returns and not just a technical change.

Technologies used

Results

Frequently asked questions

How was the migration done without disrupting third-party integrations?
The migration was carried out in waves over eight weeks. Addressing was planned from the start, and care was taken to keep third-party integrations from breaking during the move, so operations could keep running while the infrastructure moved to the cloud. Each wave was designed to protect the processes that depend on those connections.
Which systems were moved to Azure in this project?
The systems that ran on the company's own servers were moved: SAP, Microsoft SQL Server and the web services. These are critical components for the company's operations, so the project was designed with special care to ensure the move did not affect how they run or the integrations that connect them with other parties.
What financial benefit did the client get from the three-year reservation?
By committing to a three-year reservation for compute, the client obtained a 62% discount on that line item compared with the no-commitment option. It is a cost lever that comes into play when a company has clarity about its medium-term infrastructure demand and decides to commit to it.
What should a similar company consider before migrating its critical infrastructure?
It is best to first identify the third-party integrations that cannot be interrupted, plan the addressing and define a phased move. A prior assessment helps decide which systems to move first and how to validate each wave. At Arcetec, we support that process with an approach tailored to each operation, always on the Microsoft platform.

Keep reading

Want similar results?

Let's talk. We design solutions tailored to your industry.

Book a consultation