Hello everyone. I've been meaning to share a detailed account of our recent infrastructure-as-code platform migration for a while now. Our team, a mid-sized SaaS company, recently completed a move from Terraform Cloud to Scalr. The headline result is significant: we reduced our monthly IaC management bill by roughly 60%. However, as the thread title hints, it wasn't a simple cost-for-cost swap, and the trade-offs have been substantial and worth discussing.
Our primary driver was, undeniably, cost. As our Terraform Cloud usage grew—more workspaces, more teams, more frequent runs—the monthly invoice became a recurring point of contention. The per-user pricing model, coupled with the run-based fees, felt increasingly misaligned with our actual consumption, which was more about the volume and complexity of our infrastructure rather than the number of engineers clicking the UI. We conducted a thorough evaluation, mapping our usage to Scalr's account-based pricing, and the projection was compelling enough to greenlight the migration project.
The migration process itself had two major phases: state migration and pipeline refactoring. Importing our state files was surprisingly straightforward. Both platforms use a similar backend structure, so it was largely a matter of reconfiguring our backend blocks and running `terraform init` to migrate state. We did this workspace-by-workspace over a few weekends, ensuring we had rollback plans. The more intensive effort was refactoring our CI/CD pipelines. We had deeply integrated TFC's API and CLI-driven runs into our deployment workflows. Reworking those scripts and Jenkins jobs to work with Scalr's API and CLI tools took several weeks of dedicated engineering time. We also had to rebuild our internal documentation and runbooks around the new interface and concepts.
Now, for the trade-offs. The cost savings are real and impactful. However, we did lose some features we'd come to rely on. The most noticeable is the policy-as-code integration. While Scalr does have OPA support, the tight, native integration and pre-built policy sets we used in Terraform Cloud were more polished and required less maintenance. We've had to invest time in rebuilding and maintaining those policy definitions ourselves. Additionally, the user interface for visualizing resource relationships and exploring state files feels less intuitive in Scalr, which has occasionally slowed down debugging for our less-experienced team members.
Was it worth it? For our specific context, yes. The financial saving is directly funding other tooling improvements. The Scalr model of hierarchical account structures has also better fit our multi-team, multi-project organization, improving our governance in a way TFC's flat workspace list did not. That said, I would not recommend this move purely on cost alone. The migration effort is non-trivial, and the feature differential is real. Teams heavily invested in TFC's specific ecosystem features, especially around Sentinel or their private module registry, should weigh the loss carefully.
I'm curious if others in the community have undertaken similar migrations, whether to Scalr or another platform. How did your experience with state migration compare? For those who stayed with Terraform Cloud, have you found strategies to optimize cost that don't involve a full platform shift? Let's share some data points.
— Grace
Stay curious.