# Cloud-to-Cloud Webshop Migration with Cloud Native Redesign

> How Weltbild migrated its own webshop a second time – this time with a cloud redesign, infrastructure as code and agile methods, under a tight deadline.

Source: https://www.xalt.de/en/case/weltbild-cloud-migration/

Weltbild migrated its own webshop a second time – this time with an infrastructure redesign instead of a plain move. Our DevOps team brought AWS expertise, infrastructure as code and agile methods, and kept the tight deadline.

### Products used

AWS, including Route53, CloudFormation, NLB (Network Log Balancer), Puppet, Ansible, Gitlab, Graphana / Prometheus

### Solution and methodology

Agile sprint planning, GitFlow, infrastructure as code and configuration as code, containerization, introduction and workshops on DevSecOps

## About Weltbild

[Weltbild](https://www.weltbild.de/) is a German publishing and book retail company headquartered in Augsburg, and a major multi-channel bookseller. Weltbild serves customers through online shops, direct marketing and its own stores. To reduce costs and increase flexibility, Weltbild migrated its webshop to AWS.

## Core challenges and opportunities for improvement

Most companies take their first steps toward the cloud for several reasons: to save costs on running their own IT infrastructure department, to react faster and more flexibly to future changes, and to make hardware generation upgrades easier. In addition, the cloud removes the need for long-term infrastructure capacity planning. For these reasons, Weltbild decided to move to the AWS cloud.

The first implementation took place with the [Weltbild.de](https://www.weltbild.de/) webshop. Moving to the cloud generally offers lower maintenance costs and higher flexibility. However, it must be considered that the hoped-for changes are not automatically achieved by an infrastructure move with a "lift and shift" mindset. Quite the opposite is often true: achieving these desired results requires effort and expertise in infrastructure redesign and the available cloud services.

Based on these findings, Weltbild launched a new project. Its main tasks consisted of (1) a renewed infrastructure migration, this time in (2) combination with a cloud redesign and (3) a more flexible workflow. The biggest challenge was a very strict deadline. Missing it would have meant Weltbild being tied to the legacy cloud for two more years, ultimately paying for infrastructure it no longer needed.

This is exactly where our XALT DevOps team was brought in. The goal was to accelerate the planned project and contribute additional know-how in AWS-specific technologies as well as infrastructure and configuration as code. This allowed us to ensure the complete infrastructure migration was finished on time, in line with the new project goals.

## Finding a solution and introducing new methods

The first challenge was defining all necessary migration steps and turning them into a roadmap. Within the project, this served two purposes: it gave project management an overview and a visualization of identified risks that could affect the deadline, and it gave the project team defined goals that made completing the project within the given timeframe possible. This foundation let us give the Weltbild team the support needed to carry out the cloud migration using agile methods. Our DevOps team advised Weltbild along the way and introduced new methods and ways of working based on a DevSecOps mindset. These included, among others:

- Planning all required epics and tools
- Scrum Master / Product Owner support on technical cloud topics
- Running team workshops on the new tools and methods
- Improving collaboration and communication within the team
- Implementing a live project status for management
- Automating deployment
- Building a multi-account cloud environment

## Step-by-step implementation and added value

In the next step, the cloud-to-cloud migration of the webshop was carried out. The services were split into individual microservices, described as infrastructure as code, and then migrated incrementally. Some existing services were fully replaced by AWS services. This not only saved on infrastructure costs but also reduced the administrative effort.

> An incremental migration makes it possible to redesign services individually and then migrate them to the new infrastructure platform in working order. They are then integrated back into the overall application.

During the project, our team committed to comprehensive consulting for the customer and served as a co-pilot for Weltbild. This meant our team ran training sessions and workshops on the newly introduced working methods and technologies. It also became clear that the agile methods introduced helped complete the project within the required timeframe. Weltbild now has a new, agile foundation of methods and tools that follow-up projects can build on.

Further additional, positive side effects of the cloud redesign during the migration include:

- Fewer on-call incidents
- Improved service and infrastructure stability through self-healing mechanisms
- An overview of live cloud costs and a forecast of future costs
- Separation of management and infrastructure team cloud accounts

## Want to know more about this cloud-to-cloud migration success story? Feel free to contact us for a free consultation.

[Get in touch](https://www.xalt.de/en/contact/)

## More Success Stories

Home appliances

### [Digital Workplace and Intranet for 60,000 Employees at BSH Hausgeräte](https://www.xalt.de/en/case/bsh-digital-workplace-and-intranet/)

60,000 employees in 51 countries, 25 languages – and an intranet on SharePoint where only the editorial team could publish. The new one runs on Confluence and Linchpin: everyone can write, everyone sees tailored content, and it has won two awards.

Read case study →

Mechanical engineering

### [Business Intelligence with Confluence](https://www.xalt.de/en/case/fath-business-intelligence-confluence/)

A business intelligence system for mid-sized companies: instead of a separate BI tool, Fath shows its business data where employees already work – in Confluence, with PocketQuery and a permissions system that shows everyone only their own data.

Read case study →

Sports association

### [Building a Dynamic Knowledgebase with a Help Center Function Based on Confluence and Scroll Viewport](https://www.xalt.de/en/case/dav-confluence-knowledgebase/)

The Deutscher Alpenverein wanted to make its Confluence knowledge as easy to access as a website – without the upkeep of a website. With Confluence and Scroll Viewport, that became DAV360 Wissen: a knowledgebase, a help center and a learning portal with courses and quizzes.

Read case study →

## We help your team achieve greatness in every aspect

Want to know more about this success story or about our solution? We help you get the best out of your company. Feel free to contact us by phone, email, or visit us at our office.

[Get in touch](https://www.xalt.de/en/contact/)

---

*This version is for AI agents. Every page of this site is available as Markdown: append `index.md` to its path. Index of all pages: [llms.txt](https://www.xalt.de/llms.txt)*
