One platform, 70 teams: how TeamSystem built full-stack observability at scale on Grafana Cloud

As TeamSystem continued to grow through acquisitions, its Cloud Operations team faced the challenge of bringing diverse technologies and development practices under a single observability strategy. After migrating from an on-premises deployment of a previous observability platform to Grafana Cloud, the company unified observability — logs, metrics, traces, and application performance — across more than 70 teams and 600 users. freed up time equivalent to roughly 1.5 full-time roles within the existing team by reducing platform maintenance work, allowing the team to focus more on investigation and resolution while improving observability and traceability across the organization.

“We wanted a single platform where we can monitor everything, ensuring we respect our SLAs, and know that our uptime is on point,” said Luca Fumasoni, Cloud Operations Team Lead at TeamSystem. “Before, we were monitoring and checking alerts. Now we’re doing full observability with Grafana Cloud.”

Luca recently spoke with Grafana Labs about why TeamSystem moved to Grafana Cloud, how it successfully led a large-scale migration, and how the company is continuing to expand its observability practice.

Can you tell us a little about TeamSystem and what your Cloud Operations team does?

I’m Luca Fumasoni. I work on the Cloud Operations team, where I lead a team of 13 people. 

TeamSystem is an Italian tech & AI company that develops digital platforms designed to enhance the competitiveness of businesses and professionals. The Group supports its clients in the digital transformation of their entire supply chain through a comprehensive and integrated range of innovative technologies -based on AI, SaaS and cloud- to manage and evolve internal processes, strengthen collaboration across their business ecosystem and foster both growth and operational efficiency at every stage of the value chain. TeamSystem operates in Italy and abroad, closing 2025 with revenues of EUR 1.15 billion, up 14% year on year, and a team of over 6,000 employees serving around 3.1 million customers using its proprietary cloud-based digital platforms. 

Why did TeamSystem decide it was time to modernize its observability platform?

As our organization grew through both acquisitions and organic growth, we needed to increase automation and improve the quality and consistency of our observability. We wanted a single platform where we could monitor everything, meet our SLAs, and maintain high uptime as we continued to scale.

I joined TeamSystem in 2018, and around 2019 we started building what eventually became our observability strategy. Before Grafana, we were really just monitoring systems and responding to alerts. We wanted something more complete that would allow us to practice full observability.

What limitations of your previous observability platform environment led you to Grafana Cloud?

There were several challenges.

Because of the acquisitions, every team generated logs differently. Some used JSON, some plain text, and everyone had different schemas. The previous observability platform was powerful, but it worked best when everything followed the same standards. As our environment became more diverse, it became increasingly difficult to manage.

We also wanted to move beyond basic monitoring to full observability, and that became one of the main goals during our software evaluation.

Finally, maintaining our self-managed, on-premises community edition required significant effort, taking up time equivalent to roughly 1.5 full-time roles within our team. During the last six months before migration, we also experienced slower performance in that environment. Delays in data availability made it difficult to rely on the platform during software releases, because issues only became visible well after they had occurred.

Those were the biggest reasons we started looking for another solution.

When evaluating alternatives, what made Grafana Cloud stand out?

It was really a combination of factors.

We were following the Gartner Magic Quadrant, and while we already knew Grafana through the open source dashboards, Grafana Cloud was still relatively new for us. We like trying new technologies, so that was exciting.

Cost was another major factor. Grafana Cloud fit our budget and was less expensive than the other solutions we evaluated. In some cases the difference was up to 50% less.

We also liked the user interface. It felt simpler and more approachable than other products. On top of that, the agentic AI capabilities and automations really caught our attention: they had the potential to reduce manual troubleshooting and speed up incident response, which was a big plus for us.

Finally, from the proof of concept onward, we had a great experience working with the Grafana team. Everyone was proactive, knowledgeable, and easy to work with, and that gave us confidence throughout the evaluation process.

What helped your team successfully navigate the migration?

Timing was definitely the biggest challenge.

We kicked things off during a period of real change: our previous observability solution contract was coming up for renewal, we had just welcomed a new CTO who championed this move, and -given the size of both companies- procurement and legal needed to be extremely thorough to get everything right. All of that meant the timeline was tighter than ideal, but it also meant that once we moved, we moved with real alignment behind us.

At the time, we had around 70 to 80 terabytes of data in the previous solution, about 70 teams using the platform, more than 600 users, countless dashboards, and many saved queries.

The migration wasn’t simply about redirecting logs. We had to migrate dashboards, update queries, train users, and help every team onboard successfully.

Our role was both technical and organizational. We personally migrated some workloads, but we also acted as the governance team across TeamSystem. We worked directly with every team, together with Grafana Professional Services, helping people onboard and solve problems as they came up.

It required a lot of work, but by the time our previous observability platform  license expired, all of the critical workloads had successfully moved to Grafana Cloud.

Since then, we’ve been focused on building true observability on top of that foundation.

Now that the migration is complete, how has your experience with Grafana Cloud evolved? What has been most valuable so far?

The migration is complete, but we’re still building on it. We’re continuing to implement Application Observability, define SLOs, and adopt new capabilities as they become available. Every team is moving at its own pace, but the foundation is now in place and we’re continuing to expand what we can do with Grafana Cloud.

One capability that’s already had a real impact is Grafana Assistant.

Recently, a critical issue occurred when only one engineer was available over a weekend. Using Grafana Assistant, the engineer identified the root cause, generated the necessary code change, committed it, and restored the service in about an hour and a half.

Previously, we probably would have spent most of a day just figuring out where the problem was.

We shared that success with our CTO because it clearly demonstrated that moving to Grafana Cloud was the right decision. The benefits have also extended to making observability insights more accessible. “Thanks to Grafana’s agent, I can easily interpret our observability reports,” said Alessio Botta, CTO at TeamSystem. “Sometimes I simply ask, ‘Is everything running as it should?’”

What’s next for TeamSystem’s observability journey?

We’re excited to keep building on the platform. There are still more observability capabilities we want to roll out, more applications where we want to define SLOs, and we’re looking forward to adopting new Grafana features as they become available.

One thing I’ve really appreciated throughout this journey is the relationship with the Grafana team. From the proof of concept through implementation, our Professional Services team and dedicated account team were always available when we needed help.

They also regularly introduced us to new capabilities that proved valuable as we continued expanding our observability practice, so we’re excited to see what’s next.

Ready to unify your observability stack? Start free at grafana.com/get — connect your first data source in minutes.