Case study
30 Terabytes Moved Without Pausing Live Data for a US Poultry Processor
How SquareShift moved roughly 30 terabytes of historical Elasticsearch data to Elastic Cloud through snapshot-restore, without touching live ingestion, and added Azure AD single sign-on for a century-old poultry processor.
Book a session →
Client
A 100-year-old, family-owned US poultry processor that supplies cooked and raw chicken products to foodservice, retail, and industrial customers.
Industry
Food & Beverage
Services
Stack
Elasticsearch · Elastic Cloud · Google Cloud Storage · Microsoft Azure Active Directory · Index Lifecycle Management (ILM) · Elastic Fleet
How SquareShift delivered it.
The challenge
The client ran Elasticsearch on-prem and needed to move about 30 terabytes of historical data to Elastic Cloud, along with its dashboards, ILM policies, and Fleet agent configuration, without disrupting the live ingestion path already running.
What we delivered
SquareShift moved the historical data through snapshot-restore from Google Cloud Storage, leaving the live ingestion path untouched throughout. Custom dashboards, ILM policies, and Fleet agent configurations all moved over intact.
The team added single sign-on through Azure Active Directory and stood up observability on the new environment from day one. To move your own historical data to Elastic Cloud, see our Elasticsearch migration services.
The outcome
The client's data, dashboards, and agent settings all now run in Elastic Cloud, and users sign in with their existing company credentials instead of a separate login.
A historical data migration should be invisible to the people running the live system — if ingestion notices the move at all, something's wrong with how it was planned.
Platform & Software Engineering Practice Lead, SquareShift
