Case study
Seven Terabytes Moved Inside a Six-Hour Window for a US IT Provider
How SquareShift migrated a U.S. IT services provider's 1,000-plus indices and 7 terabytes of live data to Elastic Cloud inside a 4-to-6-hour cutover window.
Book a session →
Client
A U.S.-based IT services and systems integration provider that specializes in Cisco networking, VMware, and Veeam infrastructure, running a dealer-based distribution model.
Industry
Technology
Services
Stack
Elasticsearch · Elastic Cloud · Cross-Cluster Replication (CCR) · Index Lifecycle Management (ILM) · Elastic Fleet
How did SquareShift migrate 7 terabytes of live data to Elastic Cloud?
The challenge
The client is a U.S.-based IT services and systems integration provider specializing in Cisco networking, VMware, and Veeam infrastructure. It had to move over 1,000 indices and 7 terabytes of live data, under active ingestion, to Elastic Cloud inside a cutover window capped at 4 to 6 hours.
What we delivered
SquareShift moved the system indices first, validating each stage before moving forward, then moved the live and historical data. Custom scripts replicated security configurations and ILM policies precisely rather than recreating them by hand, closing off the risk of misconfiguration that cross-cluster replication, ILM, and Fleet settings carried if migrated the wrong way.
The team also turned on frozen-tier storage for data that is rarely accessed, to cut the client's ongoing storage cost.
The outcome
The environment now runs on Elastic Cloud with all 1,000-plus indices and every setting intact, migrated inside its 4-to-6-hour window with no disruption to daily operations. See how we plan moves like this in our Elasticsearch migration services.
A tight cutover window doesn't leave room to recreate configuration by hand. Scripting the replication of security and lifecycle settings is what makes a multi-hour deadline survivable.
Platform & Software Engineering Practice Lead, SquareShift


