Executive Summary:
Qualtrics, a global experience management company whose platform answers more than 100 million search queries a day, needed to move off rigid IBM bare-metal infrastructure that was slow to scale, offered limited disaster recovery and depended on manual operations.
Rapyder migrated 1.5+ petabytes of data across 13 production Elasticsearch clusters, the full Kafka estate and all PostgreSQL databases to AWS, rebuilt the infrastructure as code with Terraform and Ansible, and put automated monitoring and alerting in place.
The result: zero data loss, 99.99% availability through cutover, deployments cut from 3–5 days to under 2 hours, 70% faster incident resolution and headroom to grow to 5+ petabytes without redesign.
About Customer:
Qualtrics runs a global experience management platform that helps organisations capture, analyse and act on customer and employee feedback. Its search and analytics layer processes more than 100 million queries a day. Behind it sits a petabyte-scale data estate: Elasticsearch clusters across North America and Europe, high-throughput Kafka event streaming handling millions of events per second, and PostgreSQL databases for customer accounts, subscription billing and operational data, running at more than 10,000 transactions per second at peak.
Industry:
Industries, IT- ITeS
Offering:
Offerings, Migration
Business Challenges:
- Capacity that couldn’t keep up – New capacity took 72+ hours on IBM bare metal. With 100M+ daily queries, every demand spike put performance and customer experience at risk.
- Single-datacentre risk – One datacentre, no multi-AZ resilience and limited DR stood behind a 99.99% uptime commitment. A single site failure could take search, streaming and billing down together.
- Slow environment delivery – Each new environment took 3–5 days to deploy, delaying testing and slowing releases to customers.
- A hard growth ceiling – Scaling from 1.1 PB to 5+ PB would have forced an architectural redesign, with backup storage growing alongside the data.
- Manual incident response – Issues across 500+ servers were investigated by hand, stretching resolution times and tying engineers up in routine work.
- A zero-tolerance migration – 1.5+ PB across 13 production clusters, plus Kafka and PostgreSQL, had to move live with zero data loss and no breach of latency SLAs.
Solution Implemented:
- Infrastructure as code – Terraform provisions all AWS infrastructure from versioned state, and Ansible rolls out changes across 500+ servers. Capacity is now added in hours, not days.
- Built-in resilience and DR – Synchronous PostgreSQL replication delivers zero RPO, backed by pgBackRest backups on Amazon S3 and quarterly recovery tests. DR targets: RPO under 5 minutes, RTO under 30 minutes.
- Standardised environments – Every service ships as a versioned Docker image with resource limits and health checks, while Hiera and Vault manage configuration and secrets.
- Built for multi-petabyte scale – The AWS architecture scales to 5+ PB and 300% transaction growth without redesign, and S3 Intelligent-Tiering and lifecycle policies keep backups lean.
- Automated monitoring and alerting – Grafana (50+ panels), Cerebro, Elasticvue and Kafdrop give live visibility, while Slack alerts, escalation policies and runbooks speed up response.
- Workload-specific, zero-loss migration – Elasticsearch moved live through shard rebalancing (snapshot and restore for clusters over 80 TB), Kafka through broker expansion and PostgreSQL through pgBackRest replication, all over encrypted VPN with tested rollback.
Technology Stack:
- Amazon EC2
- Amazon EBS
- Amazon S3
- Amazon VPC
- AWS IAM
- AWS KMS
- AWS CloudTrail
- Amazon VPC Flow Logs
- Terraform
- Ansible
- Docker
- Jenkins
- Grafana
- Apache Kafka
- Elasticsearch
- PostgreSQL
- pgBackRest
Business Benefits:
- New capacity in under 2 hours, down from 7 -+ – – Qualtrics now scales to meet demand as it happens instead of waiting days for hardware.
- 99.99% availability. RPO of zero – – Qualtrics protects its uptime commitments and billing data, with disaster recovery designed and tested rather than assumed.
- 95% faster deployments – – Environments that took 3–5 days now deploy in under 2 hours, so engineering teams test and release sooner.
- Headroom to 5+ PB. 75% smaller backup footprint – – Qualtrics can grow data volumes and transactions by 300% without redesign, while cutting backup storage and keeping 7-year retention.
- 70% faster incident resolution. 85% fewer manual tasks – – Qualtrics spots and fixes issues sooner and frees engineers from hand-run procedures across 500+ servers.
- Zero data loss across 1.5+ PB – – Every Elasticsearch cluster, the full Kafka estate and all PostgreSQL databases moved with 100% data integrity, with p95 query latency under one second, Kafka acknowledgements under 100 ms and PostgreSQL commits under 50 ms.
Facing a migration measured in petabytes? Whether you are leaving bare-metal infrastructure, consolidating datacentres or moving large Elasticsearch, Kafka or PostgreSQL estates, Rapyder’s AWS experts
Key Takeaways:
- Migrate live where you can – expanding running Elasticsearch and Kafka clusters into AWS let data move while customers kept using the platform.
- Match the method to the workload – live rebalancing, snapshot-and-restore and physical replication each suited a different part of the estate.
- Codify first, then migrate – the Terraform and Ansible foundation that made the migration repeatable also cut provisioning from days to hours.
- Always keep a way back – tested per-service rollback and a 30-day warm standby gave the business confidence to proceed.
Frequently Asked Questions
- Smaller clusters were migrated continuously by making AWS nodes members of the live cluster and shifting shards across, while clusters over 80TB used snapshot and restore with a short, coordinated cutover window.
- No. AWS brokers joined the existing cluster, replication factors were temporarily raised to spread replicas across both environments, and ISR status was confirmed before leadership moved, preserving consumer offsets throughout.
- Rollback procedures were documented and tested per service, and the IBM infrastructure was kept in warm standby for a 30-day stabilisation period after cutover.
- PostgreSQL runs synchronous replication for RPO of zero, and the wider disaster recovery design targets RPO under five minutes and RTO under 30 minutes.
Qualtrics needed to move a live, petabyte-scale search, streaming and database estate off IBM bare metal without losing data or slowing queries for its customers. It needed a partner with hands-on expertise in AWS, large data platforms and DevOps who could plan the move workload by workload and automate the new environment. Rapyder brought that combination.
Rather than one big cutover, Rapyder chose a migration method for each workload based on its size and behaviour, ran IBM and AWS side by side over encrypted links, and validated data integrity before every switch. Tested rollback plans and a 30-day warm standby on IBM kept the move reversible at every stage.