Artera×
A recap of what we heard about Artera's move to Google Cloud, and how RiverMeadow takes you from discovery through cutover with near-zero disruption to the field operations and systems your crews depend on every day.
What We Heard
Before we talk about how, we wanted to reflect back what we heard in the room, so we're solving for the right problem together.
A full environment move, mainly Windows Server workloads with a meaningful number of Linux systems mixed in, not a partial lift.
Everything lands in Google Cloud by the end of the year. That deadline shapes how we sequence discovery, waves, and cutover from day one.
Crews, dispatch, and field operations can't go dark. Migration downtime isn't a line item you're willing to absorb, it's risk on a jobsite.
Windows and Linux side by side means the platform doing the work has to handle both natively, not treat one as an afterthought.
DDS, Feeney Brothers, Hydro-X, Miller Pipeline, Otis Minnesota, and Southeast Connections all lean on this environment. One migration standard beats six different playbooks.
This is also a chance to shed technical debt, close security gaps on older OS versions, and land in Google Cloud right-sized, not just relocated.
Why RiverMeadow
RiverMeadow is a single, unified platform for migration, optimization, and modernization, used across hybrid and multi-cloud environments including AWS, Azure, Google Cloud, Red Hat OpenShift, and HPE Morpheus. We built it to remove the complexity, cost, and risk that usually come with a move like yours.
Continuous replication into Google Cloud means the final cutover is a short, controlled event, not a weekend of holding your breath.
Automated OS and app replication removes the manual re-platforming work that slows most migrations down.
This isn't a new tool learning your environment. It's a mature platform with over 100,000 hours of manual migration effort saved for customers like you.
OS hardening to CIS benchmarks as part of the move, so you land in Google Cloud more secure than you left, which matters when the systems in scope support gas, electric, and water infrastructure.
Windows and Linux are first-class citizens on the platform, including Linux OS conversion where it helps you standardize post-migration.
Automated OS and SQL Server upgrades retire extended security update costs and end-of-life exposure instead of carrying them into the new environment.
The Migration Journey
Six phases, one continuous plan. Scroll through it the way your migration will actually unfold.
We start with a full, automated inventory of all 116 VMs: OS versions, dependencies, performance baselines, and Windows/Linux split, so nothing surprises us mid-migration.
We group your VMs into migration waves by dependency, risk, and business priority, then build a sequence that lands everything by December 31 without rushing the workloads that matter most.
RiverMeadow replicates each wave into Google Cloud in the background while source systems keep running. No forklift, no downtime, just continuous sync toward a ready-to-cut copy.
Not every workload needs the same treatment. As each wave lands, RiverMeadow can apply OS upgrades, CIS security hardening, and Linux conversion wherever it makes sense, you decide which systems get modernized and which are simply relocated as-is.
Your team runs the testing and gives final acceptance on every wave. RiverMeadow provides oversight throughout, comparing each system against its source, flagging issues early, and guiding you to a confident go/no-go.
A short, controlled cutover per wave, with a rollback path standing by. RiverMeadow is there live through the entire cutover event for every wave, start to finish, so Google Cloud is performing the way it should the moment you go live.
Path to December 31
This is an illustrative pace based on 116 VMs, a September 21 start, and the holidays ahead. We'll finalize exact wave sizes and dates together once Discovery is complete.
Starting September 21, Discovery kicks off immediately so Wave 1 can prove the pattern by mid-October, well ahead of the holiday season.
All 116 VMs inventoried, waves defined and sized, plan signed off.
Process proven end-to-end before scaling to the full estate.
Bulk of the migration completes ahead of the Thanksgiving pause.
Final wave (~36 VMs) closes out the estate, three weeks ahead of Dec 31.
Why This Partnership Works
RiverMeadow works with organizations running mission-critical systems, where downtime has real operational consequences on the ground, not just an IT inconvenience.
Google brought this conversation to the table because RiverMeadow has a track record of getting workloads into Google Cloud correctly and quickly.
Native tooling and manual rebuilds ask your team to absorb the downtime risk and the hours. RiverMeadow absorbs that instead, with a platform built for exactly this.
Wave-based execution across all six operating companies means progress is visible from week one, so December 31 is a managed outcome, not a last-minute scramble.
We'll walk through the RiverMeadow platform in detail and show you exactly how it handles your 116 VMs, wave by wave, from discovery through cutover.