I’m truly happy with Eon because they made it easy to get everything protected and keep us in compliance while we migrated.

—Alejandro Zuniga, IT & Security Architect SK Converge

About Sigdo Koppers

Founded in 1960, Sigdo Koppers is a leading Chilean industrial group that enables mining operations through a comprehensive portfolio of equipment, services, and industrial solutions. As part of its long‑term strategy to enhance scalability, resilience, and operational efficiency across its diverse subsidiaries, the company is advancing a modernization program that includes the migration of key workloads to Google Cloud.

The Challenge

Migration speed created pressure to protect workloads immediately and consistently

Sigdo Koppers was in the middle of a major infrastructure transition. Workloads were moving into Google Cloud, and new systems were coming online quickly. The team needed backup coverage that could keep up without turning into another ongoing project to manage.

The SK team needed to maintain compliance expectations during constant change. During migration, coverage can get uneven fast, which makes compliance harder to prove.

Why Eon

The SK team needed data protection that wouldn’t slow the migration down

Sigdo Koppers needed a backup foundation they could put in place early, then rely on as migrations continued. They also wanted ransomware safeguards built in from day one.

What started as a multi-environment reality is now heading toward consolidation: the team plans to migrate more workloads to Google Cloud, using the same protection model rather than rebuilding backup workflows. Standardizing also made it easier to govern protection across multiple projects and regions as the footprint grew.

Searchable backups helped restores stop being a ticket queue

As the environment scaled across subsidiaries, restores had become an operations overload: tickets, spreadsheets, escalations, and often full restores just to retrieve a single file or dataset.

Eon’s search and role-based access model gave teams a way to find what they needed and manage restores within their scope, without routing every request through central IT.

Now it’s like a Google search on the cellphone. People can manage their restore by themselves.

The numbers had to work for a CFO-led decision

As Sigdo Koppers evaluated options, cost wasn’t a side-by-side spreadsheet exercise; it was a gate. In the middle of a company-wide migration, any vendor decision had to fit the financial reality of a moving footprint, not a static environment.

The decision also had to hold up beyond IT. The team presented Eon in monthly cross-company IT leadership meetings, and the purchase ultimately moved through a CFO-led decision process across subsidiaries.

That gave the team a path to standardize on one approach while the footprint was still changing, and get leadership comfortable saying yes.

The Solution

Protect GCE workloads during migration and keep policies consistent

Eon was deployed to protect Google Compute Engine (GCE) workloads as systems moved into Google Cloud. As virtual machines were migrated, they were added to Eon and brought under backup policy, so coverage kept pace with change. The team used Eon to manage protection across projects and regions, instead of running separate backup workflows in each environment.

We moved workloads into GCP, protected them right away, and the team feels good about where we are.

Sigdo Koppers also set up role-based access so teams could operate within the projects they own, with clearer accountability across subsidiaries and less reliance on central IT for day-to-day restore execution.

The team also prioritized protecting core “keep-the-business-running” systems, including legacy SAP workloads running on virtual machines, so recovery and compliance expectations were met even for older, mission-critical applications.

Backups were designed to be logically isolated and immutable, supporting ransomware and audit requirements without adding extra infrastructure to manage. They also wanted the option to recover more precisely when needed, including granular restores beyond full-system recovery.

The Results

More confidence that migration wouldn’t create data protection gaps

Before Eon, backup risk was an unspoken dependency of the migration: if protection lagged, teams would either slow down or accept avoidable risk.

With Eon in place, Sigdo Koppers was able to protect workloads as they moved and maintain consistent coverage during the transition. That confidence extended across projects and regions, with a consistent approach rather than one-off configurations.

A simpler path to compliance during ongoing change

The team’s priority wasn’t just “having backups,” it was being able to say that workloads were protected and compliant as the environment changed.

Eon’s policy-driven approach made it easier to keep systems “under compliance” without treating every migration wave like a bespoke backup effort. The same governance view also supported chargeback-style reporting across business units as more workloads came online.

A critical financial restore went from days to hours

Alejandro pointed to a critical financial/accounting server where restores used to take about two days. With Eon, it took a couple of hours, which changed how confident the team felt in urgent recovery situations.

Before, it was like two days to restore one server. Now it’s a couple of hours.

A cost case that helped standardize decisions

Sigdo Koppers compared projected costs across options, including native GCP snapshots. In their internal modeling, Eon came out meaningfully lower (around 38% below their assumptions), which helped justify proceeding with the migration under a cost structure leadership could support.